skill-builderlisted

Author a new Claude Code skill the right way, from choosing the storage tier (project, shared library, or user-global) to scaffolding the SKILL.md, linking it across workspaces, and registering it for agents that do not auto-load skills, like Codex. Use when the user says "create a skill", "turn this workflow into a skill", "make this repeatable", or "new skill for".
jqaisystems/jqai-ai-skills · ★ 2 · AI & Automation · score 73

Install: claude install-skill jqaisystems/jqai-ai-skills

# Skill Builder The difference between a skill that fires reliably and one that never triggers is craft: a description written as a trigger matcher, absolute paths, explicit guardrails. This skill builds skills that work, and puts them where they belong. ## Step 1: Mine the workflow The best skills come from a workflow that just happened. If the user is converting something they did this session, extract from THIS conversation: the exact steps, the paths touched, the mistakes made and corrected. Those corrections become the new skill's Rules section. Pin down: - **Name**: kebab-case, short, specific (`follow-up-radar`, not `helper-tool`). Check for collisions against every skill already installed in any tier. - **Triggers**: the literal phrases the user would say. These go in the description, quoted. - **Job**: one job. If the skill needs an "and also" clause, that is two skills. ## Step 2: Choose the storage tier | The skill... | Tier | Location | |---|---|---| | Only makes sense in this project or workspace | Project | `<project>/.claude/skills/<name>/SKILL.md` | | Useful across several workspaces | Shared library | One real folder in a central location, linked into each workspace's `.claude/skills/` | | Generic personal utility, any folder | User-global | `~/.claude/skills/<name>/SKILL.md` | For the shared library tier, create the real folder once and link it in per workspace: - Windows (no admin rights needed): `New-Item -ItemType Junction -Path "<workspace>\.cla