Skill Creator
Scaffold a new SKILL.md for your global Claude catalog or a single repo when you need a reusable agent capability instead of one-off chat instructions.
Overview
skill-creator is a journey-wide agent skill that authors new SKILL.md capabilities for global or project scope—usable whenever a solo builder needs to capture repeatable agent workflows before relying on ad-hoc chat.
Install
npx skills add https://github.com/fearovex/claude-config --skill skill-creatorWhat is this skill?
- Two modes: /skill-create <name> for new skills and /skill-add <name> to pull from the global catalog
- Placement prompt chooses generic (~/.claude/skills/) versus project-specific (.claude/skills/)
- Special agent-config repo rules: generic skills live under <repo>/skills/ and install.sh deploys them
- Procedural format with explicit triggers: skill:create, create skill, new skill, generate skill
- Step 1 gathers requirements before writing SKILL.md to avoid incomplete procedural skills
- Two operational modes: /skill-create and /skill-add
- Two placement targets: global catalog versus project-specific .claude/skills
Adoption & trust: 1 installs on skills.sh; 1 GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You keep re-explaining the same multi-step ritual in chat instead of a versioned skill your agents can load on trigger phrases.
Who is it for?
Solo builders standardizing Claude Code or Cursor workflows who maintain a personal skills repo or per-project .claude/skills tree.
Skip if: Invoking an already-written skill for a task (use the target skill directly), or teams that forbid custom agent procedures without a separate review process.
When should I use this skill?
/skill-create <name>, create skill, new skill, generate skill, or add skill to project.
What do I get? / Deliverables
You get a correctly placed SKILL.md with triggers and procedural steps, ready for install.sh or local .claude/skills consumption on the next task.
- New or referenced SKILL.md under the chosen catalog path
- Documented triggers and procedural steps for the skill
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Capture a competitor-research ritual as a skill before you commit to a product direction.
Run /skill-create deploy-checklist and choose project-specific placement for your SaaS repo.
Encode your PR review gates into a skill after the third time you pasted the same instructions.
Author a content-refresh skill with triggers your marketing agent can load each sprint.
Split a monolithic ops chat prompt into a focused on-call skill with clear invokeWhen lines.
How it compares
Authoring scaffold for SKILL.md packages—not a runtime MCP integration and not a one-shot code generator.
Common Questions / FAQ
Who is skill-creator for?
Indie developers and small teams who package agent behaviors as skills and need consistent placement between global ~/.claude/skills and project-local .claude/skills.
When should I use skill-creator?
Use it in Build when adding agent-tooling; in Idea when capturing research rituals as skills; in Ship when encoding review or test checklists; and anytime triggers like /skill-create or create skill appear before work starts.
Is skill-creator safe to install?
It primarily writes markdown skill files under paths you choose; review the Security Audits panel on this page and avoid letting the agent place secrets inside SKILL.md.
SKILL.md
READMESKILL.md - Skill Creator
# skill-creator > Creates new skills, either generic for the global catalog or specific to the current project. **Triggers**: skill:create, create skill, new skill, generate skill --- ## Two modes of operation ### Mode `/skill-create <name>` Creates a **new** skill that does not exist anywhere. Asks whether it is: - **Generic** → goes to `~/.claude/skills/<name>/SKILL.md` (available in all projects) - **Project-specific** → goes to `.claude/skills/<name>/SKILL.md` (only in this project) > **EXCEPTION — `agent-config` repo**: this repo IS the source of `~/.claude/`. When working inside it: > > - "Generic" placement → write to `<repo>/skills/<name>/SKILL.md` (NOT `~/.claude/skills/`). `install.sh` deploys it. > - "Project-specific" does NOT apply — the repo has no `.claude/` of its own; everything it owns is global. > - NEVER write directly to `~/.claude/skills/` from this repo; the next `install.sh` overwrites it. ### Mode `/skill-add <name>` Adds an **existing skill from the global catalog** to the current project. Copies or creates a reference. --- ## Process: /skill-create ### Step 1 — Gather information **Context detection (run before presenting the placement prompt):** ``` is_claude_config = ( file_exists("install.sh") AND ( project root contains install.sh AND skills/_shared/ OR basename(cwd) == "agent-config" ) ) has_project_context = ( dir_exists(".claude") ) is_tech_skill = name matches any of: react*, vue*, angular*, svelte*, next*, nuxt*, remix*, prisma*, drizzle*, sequelize*, typeorm*, mongoose*, zod*, yup*, valibot*, tailwind*, bootstrap*, chakra*, typescript*, javascript*, node*, python*, django*, fastapi*, flask*, rails*, laravel*, spring*, go-*, rust-*, kotlin*, swift*, zustand*, redux*, jotai*, mobx*, recoil*, react-native*, expo*, playwright*, vitest*, jest*, cypress*, storybook* if is_tech_skill AND NOT is_claude_config: default_placement = "project-local" → option 1 rationale = "Tech-specific skills belong in the consuming project's .claude/skills/, not the global catalog. See CLAUDE.md rule." elif is_tech_skill AND is_claude_config: default_placement = "_templates/tech/" → option 3 (template-only) rationale = "In agent-config repo, tech skills go to skills/_templates/tech/ so skill-creator can scaffold them into consumer projects." elif has_project_context AND NOT is_claude_config: default_placement = "project-local" → option 1 else: default_placement = "global" → option 2 ``` Ask the necessary questions to create a useful skill. The placement prompt MUST reflect the detected default using the `[DEFAULT]` marker: **When `default_placement = "project-local"`:** ``` Is this skill for this specific project or for all your projects? 1. This project only → .claude/skills/ [DEFAULT] 2. Global catalog → ~/.claude/skills/ What does this skill do? (one-sentence description) When should it activate? (what situations trigger its use?) Are there specific code patterns, commands, or processes it should know about? ``` **When `default_placement = "global"`:** ``` Is this skill for this specific project or for all your projects? 1. This project only → .claude/skills/ 2. Global catalog → ~/.claude/skills/ [DEFAULT] What does this skill do? (one-sentence description) When should it activate? (what situations trigger its use?) Are there specific code patterns, commands, or processes it should know about? ``` **When `default_placement = "_templates/tech/"` (tech skill inside agent-config repo):** ``` This is a tech-specific skill. It will NOT be deployed globally. Save as a template at `skills/_templates/tech/<name>/` so `skill