Skill Builder

Skill Builder

Create, repair, audit or export one canonical skill package, or turn supported expertise into a small authoring proposal.

Decide whether to create anything

Apply these before any creation step, including when the request already names the new skill or file it wants:

1. Find the existing owner. Search skills, references, checklists and instruction files for one that already handles the behavior. Extend that owner rather than adding a root.
2. Count independent occurrences. A new skill, gate, library or workflow needs three independently evidenced real occurrences and a successful reapplication to a source case without missing context. Fewer occurrences support only a narrow note in an existing owner; one incident is an observation, not a skill. An authoritative source supports only a faithful statement of that source.
3. Name the consumer of every new artifact. A proposed process artifact (a report, ledger, counter, dashboard or tracker) needs a concrete consumer, the decision it informs, the observed defect it answers and a retirement condition. If any is missing, leave it out; code written only to consume it is no consumer.
4. No action is a valid result, and so is a short addition to an existing owner. Say what the evidence supports before drafting, build only what the caller then authorizes, and return a proposal inline unless a durable one was requested.
5. A built package proves no benefit. Route behavioral benefit to Skill Eval and acceptance judgment to Validate.

Choose the requested operation