Agent Skill Design
Use this skill to create practical, portable agent skills from repeated workflows or domain reference material.
Workflow
- Define one job for the skill. If the description needs multiple unrelated "and" clauses, split it.
- Write trigger metadata as the routing interface: clear name and description with positive use cases.
- Keep
SKILL.mdprocedural and short. Move detailed docs intoreferences/, deterministic helpers intoscripts/, and reusable output material intoassets/. - Read
references/day3_agent_skills.txtwhen deciding packaging, progressive disclosure, evaluation, or anti-patterns. - Validate with at least three prompts:
- should trigger
- should trigger with a realistic edge case
- should not trigger
- Iterate on the description before adding more body text.
Review Criteria
- One clear job
- Good trigger description
- Minimal body
- References loaded only when needed
- No bulky background prose in
SKILL.md - Concrete validation prompts
- No duplicate information between
SKILL.mdand references
Evaluation Prompts
- Positive: "Turn this recurring workflow into a Codex skill." Expected: scoped skill design with trigger, workflow, references/scripts/assets choice, and eval prompts.
- Positive edge: "This whitepaper has useful agent ideas; extract practical skills." Expected: avoid source dump, create operating references and validation prompts.
- Negative: "Use an existing skill to edit this file." Expected: no skill-design work unless the skill itself is being created or changed.