| name | skill-creator |
| description | Guide for creating and updating effective skills. Use when the user wants to add a new skill or improve an existing skill for tool workflows or reusable domain knowledge. |
Skill Creator
Use this skill when the task is to create, refine, or maintain a skill.
Skills live inside the workspace at skills/<skill-id>/ and are discovered by the agent through the SKILL.md frontmatter plus any bundled scripts/, references/, or assets/.
Core Rules
- Keep the frontmatter precise.
- Keep the body short and procedural.
- Put detailed reference material into
references/ instead of bloating SKILL.md.
- Prefer reusable scripts or templates when the same steps will be repeated.
- Design for the real runtime: root shell, workspace files, built-in tools, and Android automation.
Skill Shape
Every skill needs a SKILL.md file.
Recommended layout:
skill-id/
├── SKILL.md
├── scripts/
├── references/
└── assets/
Use only the folders that are actually needed.
Frontmatter
Use YAML frontmatter with only these fields:
---
name: my-skill
description: What the skill does and when the agent should use it.
---
Write the description as the trigger contract:
- State the task type clearly.
- State the signals that should trigger the skill.
- Mention important environments or tools when they matter.
Bad description:
Helpful utility for many tasks.
Good description:
Create or update deployment runbooks for workspaces. Use when the user asks to document setup, workspace paths, scheduled runs, or recovery steps for on-device agents.
Body Guidance
Write the body as instructions for another agent.
Prefer:
- imperative steps
- short heuristics
- references to concrete files or directories
- explicit failure handling
Avoid:
- long product overviews
- repeated basics the model already knows
- user-facing marketing text
- duplicate content that belongs in
references/
Resource Choices
Use scripts/ when:
- a flow is fragile
- the same code would otherwise be rewritten often
- deterministic output matters
Use references/ when:
- the skill needs schemas, API notes, policy text, or domain documentation
- only part of the material is needed per task
Use assets/ when:
- the skill needs templates, starter projects, icons, or example files that should be copied or edited
Creation Workflow
- Understand the repeated task the skill should help with.
- Collect a few realistic user requests that should trigger it.
- Decide which knowledge belongs in
SKILL.md and which belongs in bundled resources.
- Create the skill directory under
skills/<skill-id>/.
- Write
SKILL.md with a strong description and compact body.
- Add any needed
scripts/, references/, or assets/.
- Re-read the result and cut anything that is obvious, duplicated, or too generic.
Naming Rules
- Use lowercase letters, digits, and hyphens only.
- Keep the id short and descriptive.
- Prefer action-oriented names such as
skill-creator, calendar-helper, or workspace-audit.
Review Checklist
Before finishing, verify:
- the skill id matches the folder name
SKILL.md exists- the description explains when to use the skill
- the body tells the agent what to do next
- bundled resources are referenced only when needed
- no extra documentation files were added without a clear reason
Editing Existing Skills
When updating a skill:
- Preserve the trigger intent unless the user explicitly wants to change it.
- Tighten the description if the skill is triggering too broadly or too narrowly.
- Move bulky details out of
SKILL.md when the file starts becoming hard to scan.
- Keep examples realistic and aligned with the runtime.
Output Expectation
When asked to create or revise a skill, produce the actual skill files in the workspace rather than only describing them.
