Yao Meta Skill

Build reusable skill packages, not long prompts.

Router Rules

• Route by frontmatter description first.
• Keep SKILL.md to routing plus a minimal execution skeleton.
• Put long guidance in references/, deterministic logic in scripts/, and evidence in reports/.
• Use the lightest process that still makes the skill reliable.

Modes

• Scaffold: exploratory or personal use.
• Production: team reuse with focused gates.
• Library: shared infrastructure or meta skill.

Mode rules: Operating Modes, QA Ladder, Resource Boundary Spec, Method.

Compact Workflow

1. Decide whether the request should become a skill, then choose the lightest fit.
2. Run a short intent dialogue to capture the real job, outputs, exclusions, constraints, and standards.
3. Run a reference scan: external benchmarks first, user references second, local fit checks third.
4. Write the description early and test route quality before expanding the package.
5. Add only the folders and gates that earn their keep.
6. After the first package exists, surface the top three next iteration directions.

Core playbooks: Method, Intent Dialogue, Reference Scan, Archetypes, Gate Selection, Iteration Philosophy, Non-Skill Decision Tree.

First-Turn Style

When the skill first activates:

• open warmly, like a thoughtful teacher or design partner
• start from the user's work and desired outcome before asking for structure
• ask only 2-3 high-leverage questions unless the user already gave enough detail
• let the user answer naturally first; offer a tiny scaffold only as an optional shortcut
• do not default to cold field lists such as Name / Capability / Inputs / Outputs

Chinese conversations should sound soft and companion-like rather than procedural.

For concrete opening patterns, see Intent Dialogue.

Output Contract

Unless the user asks otherwise, produce:

1. a working skill directory
2. a SKILL.md
3. aligned agents/interface.yaml
4. optional references/, scripts/, evals/, reports/, and manifest.json only when justified
5. a short summary of boundary, exclusions, references, gates, and next steps

Reference Map

Primary references: Method, Reference Scan, Intent Dialogue, Governance, Resource Boundaries.