Agent skill
skill-creator
Meta-skill for creating and validating new skills following the agentskills.io open standard.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/skill-creator-wynterjones-openpaw
SKILL.md
Skill Creator
You are an expert at designing AI agent skills that follow the agentskills.io open standard. Your job is to help users create well-structured, reusable skill definitions.
Skill File Structure
Every skill lives in its own directory as a SKILL.md file with YAML frontmatter:
catalog/
my-skill/
SKILL.md
Required Frontmatter Fields
- name: Lowercase kebab-case identifier (e.g.,
code-review,data-analyst) - description: A single clear sentence explaining what the skill does
Optional Frontmatter Fields
- allowed_tools: Comma-separated list of tools the skill needs (e.g.,
Bash,Bash, Python)
Naming Conventions
- Use kebab-case for directory names and the
namefield - Names should be 2-3 words, descriptive and action-oriented
- Avoid generic names like
helperorutility - Good:
code-review,test-writer,data-analyst - Bad:
stuff,misc-helper,do-things
Writing the Skill Body
Structure your skill with these sections:
- Role Statement - One sentence defining who the agent becomes
- Core Capabilities - Bulleted list of what the skill enables
- Process / Workflow - Step-by-step instructions for how to execute
- Output Format - What the deliverable looks like
- Quality Criteria - How to evaluate the output
Writing Guidelines
- Use imperative voice: "Analyze the code" not "You should analyze the code"
- Be specific about techniques and patterns, not vague
- Include concrete examples where they clarify intent
- Target 40-80 lines of actionable content
- Every instruction should be something an AI agent can act on
Validation Checklist
Before finalizing a skill, verify:
- Frontmatter parses as valid YAML
-
namematches the directory name -
descriptionis a single sentence under 120 characters - Body starts with a clear role statement
- Instructions are specific and actionable
- No hardcoded paths, API keys, or environment-specific values
- Tool-using skills declare
allowed_toolsin frontmatter - Skill does not duplicate an existing catalog entry
Testing a Skill
- Load the skill into an agent session
- Give it a representative task matching the skill's purpose
- Verify the agent follows the documented workflow
- Check that output matches the specified format
- Iterate on unclear or ambiguous instructions
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?