New Skill Creator

VerifiedCaution

Creates a new Claude Code skill with a test file using the skill-builder scaffold tool. It walks through choosing a kebab-case name, setting user-invocable flag, and selecting local (repo-specific) or global installation. Ideal when you need to quickly bootstrap a new skill with proper structure and tests.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#skill-creation#scaffolding#testing#claude-code

Recommended for

Automated summary

Creates a new Claude Code skill with comprehensive tests using the skill-builder framework.

Strengths

  • Automates scaffolding of skill and test files
  • Supports both local (repo-specific) and global skills
  • Option to make the skill user-invocable as a slash command

Limitations

  • Requires the skill-builder tool to be installed
  • Only works within the Claude Code ecosystem
  • Names must be in kebab-case
When to use it

Use this skill when you need to quickly create a new, well-structured Claude Code skill with tests.

When not to use it

Avoid using it for simple one-off tasks that are not intended to become reusable skills.

Security analysis

Caution
Quality score90/100

The skill runs a Bash script to create new skills. While the script is presumably trusted and the skill is legitimate, execution of any script introduces risk if the script is compromised or contains unintended side-effects.

Findings
  • •Uses Bash to run a scaffold script, which could execute arbitrary commands if the script is tampered with.
How this analysis is made

Examples

Create a local user-invocable skill
/new-skill
Skill name: create-component
User-invocable? yes
Local or global? local
Create tests? yes
Create a global skill without tests
/new-skill validate-json --global --no-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

  1. 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)
  2. 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
  3. Show what was created

    • List the files created
    • Show the skill file path
    • Show the test file path (if created)
    • Explain next steps
  4. 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.py

Next steps:

  1. Edit .claude/skills/create-component.md and fill in [EDIT ME] placeholders
  2. Update the test file with specific test cases
  3. Run tests: cd .claude/tests && pytest integration/create_component/ -v
  4. Commit and share with team: git add .claude/skills/ .claude/tests/" </example>
<example> User: "/new-skill validate-json --global" Assistant: [Detects inline arguments, runs scaffold] "✓ Created global skill: - ~/.claude/skills/validate-json.md - ~/.claude/agents/tests/integration/validate_json/test_validate_json.py

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?).

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/new-skill-creator-mm5t8bik/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/new-skill-creator-mm5t8bik' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/new-skill-creator-mm5t8bik/download' --output '.skill-downloads/new-skill-creator-mm5t8bik/SKILL.md.part' && mv '.skill-downloads/new-skill-creator-mm5t8bik/SKILL.md.part' '.skill-downloads/new-skill-creator-mm5t8bik/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/new-skill-creator-mm5t8bik/SKILL.md' && test -s '.skill-downloads/new-skill-creator-mm5t8bik/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/new-skill' && cp -R '.skill-downloads/new-skill-creator-mm5t8bik' '.claude/skills/new-skill'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/new-skill-creator-mm5t8bik'

openskills read 'new-skill-creator-mm5t8bik'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/new-skill-creator-mm5t8bik/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills