# Skill Creator

> Meta-skill for creating and validating new skills following the agentskills.io open standard.

- Skill: `majiayu000/skill-creator-42` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/skill-creator-42`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/skill-creator-42/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/skill-creator-42

---


# 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 `name` field
- Names should be 2-3 words, descriptive and action-oriented
- Avoid generic names like `helper` or `utility`
- Good: `code-review`, `test-writer`, `data-analyst`
- Bad: `stuff`, `misc-helper`, `do-things`

## Writing the Skill Body

### Structure your skill with these sections:

1. **Role Statement** - One sentence defining who the agent becomes
2. **Core Capabilities** - Bulleted list of what the skill enables
3. **Process / Workflow** - Step-by-step instructions for how to execute
4. **Output Format** - What the deliverable looks like
5. **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
- [ ] `name` matches the directory name
- [ ] `description` is 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_tools` in frontmatter
- [ ] Skill does not duplicate an existing catalog entry

## Testing a Skill

1. Load the skill into an agent session
2. Give it a representative task matching the skill's purpose
3. Verify the agent follows the documented workflow
4. Check that output matches the specified format
5. Iterate on unclear or ambiguous instructions