skill-creator

Skill creator

Turn a repeatable workflow into a compact specialist package, or improve an existing package without erasing its effective domain knowledge. Optimize for correct behavior on real requests rather than conformity to one Markdown template.

Choose the mode

• Create — build a new package from concrete usage examples.
• Improve — diagnose and revise an existing package while preserving working behavior.
• Merge — combine overlapping packages, reconcile triggers and resources, and define migration boundaries.
• Validate — inspect structure, resource routing, triggers, and behavior without changing the package unless asked.

Read the current package, repository conventions, validators, and catalog metadata before asking questions. Ask only for intent that cannot be recovered and would materially alter trigger scope, side effects, or output.

Model real usage

Collect or derive representative prompts:

• direct requests that should trigger;
• common paraphrases and incomplete requests;
• near-miss requests that belong to another skill;
• multi-turn requests where the skill becomes relevant later;
• risky, unavailable, or ambiguous cases that require a branch;
• examples of successful output and known failure modes.

For each positive example, outline the execution path from inputs to verified outcome. Identify decisions that depend on context and operations that should remain deterministic.

Audit an existing package

When improving or merging, inventory:

• frontmatter trigger coverage and collisions;
• user inputs, inferred context, and unnecessary questions;
• decision branches and missing failure paths;
• domain rules versus generic advice;
• output and side-effect contract;
• verification that exercises behavior rather than checking ingredients;
• every reference, script, and asset, including reachability and duplication;
• runtime-specific assumptions and portability constraints.

Preserve concise, evidence-backed instructions and tested resources. Remove false precision, unsupported claims, authorial house style, and formatting rules that do not affect behavior.