[IMPORTANT] Use TaskCreate to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ask user whether to skip.
Quick Summary
Goal: Add new reference files or scripts to an existing skill directory.
Workflow:
- Identify — Determine target skill and required additions
- Create — Add reference/script files following skill-creator patterns
- Validate — Ensure files follow progressive disclosure (<100 lines each)
Key Rules:
- Delegates to
skill-creator and claude-code skills for guidance
- Reference files must be under 100 lines (progressive disclosure)
- Scripts must have tests and respect
.env loading order
Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).
Think harder.
Use skill-creator and claude-code skills.
Use docs-seeker skills to search for documentation if needed.
Arguments
$1: skill name (required, default: "")
$2: reference or script prompt (required, default: "")
If $1 or $2 is not provided, ask the user to provide it.
Your mission
Add new reference files or scripts to a skill at .claude/skills/$1 directory.
Requirements
Rules of Skill Creation:
Base on the requirements:
- Always keep in mind that
SKILL.md and reference files should be token consumption efficient, so that progressive disclosure can be leveraged at best.
SKILL.md is always short and concise, straight to the point, treat it as a quick reference guide.
- If you're given nothing, use
AskUserQuestion tool for clarifications and researcher subagent to research about the topic.
- If you're given an URL, it's documentation page, use
Explore subagent to explore every internal link and report back to main agent, don't skip any link.
- If you receive a lot of URLs, use multiple
Explore subagents to explore them in parallel, then report back to main agent.
- If you receive a lot of files, use multiple
Explore subagents to explore them in parallel, then report back to main agent.
- If you're given a Github URL, use
repomix command to summarize (install it if needed) and spawn multiple Explore subagents to explore it in parallel, then report back to main agent.
IMPORTANT:
- Skills are not documentation, they are practical instructions for Claude Code to use the tools, packages, plugins or APIs to achieve the tasks.
- Each skill teaches Claude how to perform a specific development task, not what a tool does.
- Claude Code can activate multiple skills automatically to achieve the user's request.
IMPORTANT Task Planning Notes (MUST FOLLOW)
- Always plan and break work into many small todo tasks
- Always add a final review todo task to verify work quality and identify fixes/enhancements
1---2name: skill-add-23description: [Skill Management] Add new reference files or scripts to a skill4---56> **[IMPORTANT]** Use `TaskCreate` to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ask user whether to skip.78## Quick Summary910**Goal:** Add new reference files or scripts to an existing skill directory.1112**Workflow:**13141. **Identify** — Determine target skill and required additions152. **Create** — Add reference/script files following skill-creator patterns163. **Validate** — Ensure files follow progressive disclosure (<100 lines each)1718**Key Rules:**1920- Delegates to `skill-creator` and `claude-code` skills for guidance21- Reference files must be under 100 lines (progressive disclosure)22- Scripts must have tests and respect `.env` loading order2324**Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).**2526Think harder.27Use `skill-creator` and `claude-code` skills.28Use `docs-seeker` skills to search for documentation if needed.2930## Arguments3132$1: skill name (required, default: "")33$2: reference or script prompt (required, default: "")34If $1 or $2 is not provided, ask the user to provide it.3536## Your mission3738Add new reference files or scripts to a skill at `.claude/skills/$1` directory.3940## Requirements4142<reference-or-script-prompt>43$244</reference-or-script-prompt>4546## Rules of Skill Creation:4748Base on the requirements:4950- Always keep in mind that `SKILL.md` and reference files should be token consumption efficient, so that **progressive disclosure** can be leveraged at best.51- `SKILL.md` is always short and concise, straight to the point, treat it as a quick reference guide.52- If you're given nothing, use `AskUserQuestion` tool for clarifications and `researcher` subagent to research about the topic.53- If you're given an URL, it's documentation page, use `Explore` subagent to explore every internal link and report back to main agent, don't skip any link.54- If you receive a lot of URLs, use multiple `Explore` subagents to explore them in parallel, then report back to main agent.55- If you receive a lot of files, use multiple `Explore` subagents to explore them in parallel, then report back to main agent.56- If you're given a Github URL, use [`repomix`](https://repomix.com/guide/usage) command to summarize ([install it](https://repomix.com/guide/installation) if needed) and spawn multiple `Explore` subagents to explore it in parallel, then report back to main agent.5758**IMPORTANT:**5960- Skills are not documentation, they are practical instructions for Claude Code to use the tools, packages, plugins or APIs to achieve the tasks.61- Each skill teaches Claude how to perform a specific development task, not what a tool does.62- Claude Code can activate multiple skills automatically to achieve the user's request.6364---6566**IMPORTANT Task Planning Notes (MUST FOLLOW)**6768- Always plan and break work into many small todo tasks69- Always add a final review todo task to verify work quality and identify fixes/enhancements