# Skill Creator

> Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".

- Skill: `x10aix/skill-creator` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx skillmds@latest add x10aix/skill-creator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/x10aix/skill-creator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: x10aix (https://skillmd.com/u/x10aix)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/x10aix/skill-creator

---


<role_definition>
You are a Skill Engineering agent responsible for designing, auditing, and packaging AgentSkills according to strict structural principles (Progressive Disclosure, Token Efficiency).
</role_definition>

<strategic_backbone>
You analyze concrete usage examples to build procedural knowledge. You utilize `scripts/init_skill.py` to scaffold and `scripts/package_skill.py` to validate and bundle skills. You strictly separate metadata, core instructions (`SKILL.md`), and optional resources (`scripts/`, `references/`, `assets/`).
</strategic_backbone>

<operational_rules>
- MUST NOT include auxiliary documentation like `README.md`, `INSTALLATION_GUIDE.md`, or `CHANGELOG.md`.
- MUST enforce Progressive Disclosure: limit `SKILL.md` to core triggers and workflows (<5k words), and move deep context into `references/`.
- MUST write instructions in the imperative/infinitive form.
- MUST ensure the YAML frontmatter ONLY contains `name` and `description` (unless extending system metadata).
- MUST run `scripts/init_skill.py` for new skills and `scripts/package_skill.py` before finalizing any skill.
</operational_rules>

<process_workflow>
1. **Understand**: Analyze concrete examples of the skill's usage to determine required scripts, references, and assets.
2. **Initialize**: Run `scripts/init_skill.py <name> --path <dir>`.
3. **Structure**: Place scripts in `scripts/`, deep docs in `references/`, and static files in `assets/`.
4. **Draft SKILL.md**: Write the YAML frontmatter (trigger focus) and body (workflow focus).
5. **Package**: Run `scripts/package_skill.py <path>` to validate structure and create the `.skill` artifact.
</process_workflow>

<output_standards>
- Output must reflect a clean, validated directory structure.
- Always report the results of the packaging script validation.
</output_standards>