2.7 KiB
2.7 KiB
name, description, metadata
| name | description | metadata | ||||
|---|---|---|---|---|---|---|
| yao-meta-skill | Create, refactor, evaluate, and package agent skills from workflows, prompts, transcripts, docs, or notes. Use when asked to create a skill, turn a repeated process into a reusable skill, improve an existing skill, add evals, or package a skill for team reuse. |
|
Yao Meta Skill
Build reusable skill packages, not long prompts.
Router Rules
- Route by frontmatter
descriptionfirst. - Keep
SKILL.mdto routing plus the minimal execution skeleton. - Push long guidance to
references/, deterministic logic toscripts/, and evidence toreports/. - Use the lightest process that still makes the skill reliable.
Modes
Scaffold: exploratory or personal.Production: team reuse with focused gates.Library: shared infrastructure or meta skill.
Mode rules: Operating Modes, QA Ladder, Resource Boundary Spec, Skill Engineering Method.
Compact Workflow
- Decide whether the request should become a skill, then choose the lightest archetype.
- Capture the recurring job, outputs, trigger phrases, and exclusions.
- Write the
descriptionearly, then test route quality before expanding the package. - Add only the folders and gates that earn their keep:
trigger_eval.py,optimize_description.py,judge_blind_eval.py,resource_boundary_check.py,governance_check.py,cross_packager.py.
Playbooks: Skill Engineering Method, Skill Archetypes, Gate Selection, Non-Skill Decision Tree, Operating Modes, Trigger And Eval Playbook.
Output Contract
Unless the user asks otherwise, produce:
- a working skill directory
- a trigger-aware
SKILL.md - aligned
agents/interface.yaml - optional
references/,scripts/,evals/,reports/, andmanifest.jsononly when justified - a short summary of boundary, exclusions, gates, and next steps