skill-expert
Installation
SKILL.md
Skill Expert
Produce a skill with a clear trigger, a bounded job, and an acceptance contract its next consumer can use. Loaded text is a shared budget.
House style
- Every word earns its place. Keep domain knowledge, contracts, project facts, and boundaries; cut what repeats host behavior. Length alone does not make a rule wrong.
- Freedom, not procedure. Fix an order only where it protects a dependency or invariant; leave the rest to the orchestrator. State the purpose, the completion condition, and what happens when one part is blocked: finish the rest and report the gap.
- Judgment, not textbook content. Teach what the model lacks, and give a rule its reason instead of emphasis. One principle generalizes; do not list every variant.
- Scripts only where they enforce. Script only what a model cannot reliably do by hand: fragile, deterministic, security-sensitive, or repeated work.
- One owner per rule. State each rule once, where it lives; others point to it.
- Short routing. A dispatching skill runs
model_routing.py resolve, asks "Approve this plan, or specify changes.", then uses T3delegate_task, a native subagent, orcli-runner,pi-runner, ormuse-runner(pattern). Others say nothing about routing.
Select the work
An audit reports findings without edits. An improvement request authorizes its scoped edits without asking again.