Our review
Creates a new Claude Code skill with comprehensive test scaffolding using the skill-builder framework.
Strengths
- Automates creation of skill and test files
- Supports both local and global skill installations
- Includes ready-to-run test structure for reliability
Limitations
- Requires the scaffold.sh tool to be present in ~/.claude/agents/skill-builder/
- Generated files contain [EDIT ME] placeholders that need manual filling
When you want to quickly bootstrap a new Claude Code skill with a standardized structure and tests.
If you prefer to create skill files manually or use a different skill framework.
Security analysis
SafeThe skill instructs running a scaffold script that creates skill files and tests. No destructive, exfiltrating, or obfuscated actions are present. The Bash usage is for a legitimate, predefined purpose with no external URLs or dangerous commands.
No concerns found
Examples
Create a new skill called 'create-component' that is user-invocable and local to this repo with tests.Create a global skill named 'validate-json' that is not user-invocable and skip tests.name: new-skill description: Create a new Claude Code skill with tests user_invocable: true
New Skill Creator
Creates a new Claude Code skill with comprehensive tests using the skill-builder framework.
Instructions
-
Ask the user for skill details
- Skill name (kebab-case, e.g., validate-json, create-component)
- Should it be user-invocable? (can they use /skill-name)
- Is this for the current repo or global? (--local vs --global)
- Should we skip test creation? (usually no)
-
Run the scaffold tool
~/.claude/agents/skill-builder/scaffold.sh SKILL_NAME [flags]Flags:
--user-invocable- Make it a slash command--local- Create in current repo's .claude/skills/ (team-shared)--global- Create in ~/.claude/skills/ (default, personal)--no-tests- Skip test file creation
-
Show what was created
- List the files created
- Show the skill file path
- Show the test file path (if created)
- Explain next steps
-
Guide next steps
- Tell user to edit the [EDIT ME] placeholders
- Show how to run tests:
cd ~/.claude/agents/tests && ./run_tests.sh SKILL_NAME - If --local, remind to commit and share with team
Examples
<example> User: "/new-skill" Assistant: "I'll help you create a new skill. What would you like to call it? (use kebab-case like 'validate-json' or 'create-component')" User: "create-component" Assistant: "A few questions: 1. Should this be user-invocable as /create-component? (yes/no) 2. Is this for the current repo only, or global? (local/global) 3. Should I create tests? (yes/no - recommend yes)" User: "yes, local, yes" Assistant: [Runs scaffold.sh create-component --user-invocable --local] "✓ Created skill files: - .claude/skills/create-component.md - .claude/tests/integration/create_component/test_create_component.pyNext steps:
- Edit .claude/skills/create-component.md and fill in [EDIT ME] placeholders
- Update the test file with specific test cases
- Run tests: cd .claude/tests && pytest integration/create_component/ -v
- Commit and share with team: git add .claude/skills/ .claude/tests/" </example>
This is a global skill (available in all projects). Edit the skill file and fill in the [EDIT ME] placeholders." </example>
Important Notes
- Naming: Always use kebab-case (my-skill, not MySkill or my_skill)
- Local vs Global:
- Local: Repo-specific, shared with team via git
- Global: Personal, available everywhere
- User-invocable: Let users call it as /skill-name
- Tests: Always recommend creating tests
Tool Usage
Use Bash tool to run the scaffold script:
~/.claude/agents/skill-builder/scaffold.sh SKILL_NAME --user-invocable --local
Check current directory to determine if --local makes sense (are we in a git repo?).
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.