skill-creator

name	skill-creator
description	Guide for creating effective skills. Use when the user wants to create a new skill or improve an existing one — a reusable instruction package that extends Wuu with specialized knowledge, workflows, or tool integrations.
user-invocable	true
trigger-condition	When the user asks to create, write, package, or improve a skill, or asks how to teach Wuu a repeatable workflow.
allowed-tools	["read_file","write_file","edit_file","bash"]
examples	["create a skill for our release checklist","turn this PDF-rotation workflow into a skill","improve the description of my deploy skill so it triggers reliably"]
verification-checklist	["SKILL.md exists at the agreed location","wuu skills lint reports no errors","description states both what the skill does and when to use it","bundled scripts were executed at least once"]
progressive-disclosure	Read references/frontmatter.md only when the user needs fields beyond name and description, or asks for Wuu-specific behavior.

Skill Creator

Guidance for creating effective skills.

About Skills

Skills are modular, self-contained folders that extend Wuu with specialized knowledge, workflows, and tools. Think of them as onboarding guides for a specific domain or task: they turn a general-purpose agent into one equipped with procedural knowledge no model fully possesses.

A skill provides one or more of:

1. Specialized workflows — multi-step procedures for a specific domain
2. Tool integrations — instructions for specific file formats or APIs
3. Domain expertise — company-specific knowledge, schemas, business logic
4. Bundled resources — scripts, references, and assets for repetitive tasks

Core Principles

Concise is key

The context window is a public good. A skill shares it with the system prompt, the conversation, every other skill's metadata, and the actual user request.

Default assumption: the model is already very smart. Only add context it does not already have. Challenge every paragraph: "does this justify its token cost?" Prefer concise examples over verbose explanations.

Set appropriate degrees of freedom

Match specificity to how fragile the task is:

• High freedom (prose instructions) — multiple approaches are valid and context determines the best one.
• Medium freedom (pseudocode or parameterized scripts) — a preferred pattern exists; some variation is acceptable.
• Low freedom (exact scripts, few parameters) — the operation is fragile, consistency is critical, or one exact sequence must be followed.

A narrow bridge with cliffs needs guardrails; an open field allows many routes.

Anatomy of a skill

skill-name/
├── SKILL.md          (required: YAML frontmatter + markdown instructions)
├── scripts/          (optional: executable code for deterministic steps)
├── references/       (optional: docs loaded into context only when needed)
└── assets/           (optional: files used in output — templates, fonts, icons)

• SKILL.md frontmatter needs name and description. The description is the primary trigger: it is the only part always visible to the model, so it must state both what the skill does and when to use it. Do not add other fields by default; when the user needs invocation control, tool limits, or Wuu-specific behavior, read references/frontmatter.md first.
• SKILL.md body is loaded only after the skill triggers. Keep it under 500 lines; split details into references/ when approaching that limit.