plastic-skill-creating

# Creating Skills Author skills, agents, and hooks as thin routers over deep references. This body carries the rules that must stay correct without opening anything, then routes each authoring task to the reference that holds the depth. ## Rules (must be right even if no reference is opened) - Three load levels, hard budgets: metadata around 100 tokens (always loaded), body under 5000 tokens and under 500 lines (loaded on trigger), references on demand. Keep the body well under budget, not at the ceiling. - Progressive disclosure first: the body routes, the references hold the depth. Any deep how-to in the body belongs in a reference instead. - Description states WHEN to use, not the workflow. Write it in third person, front-load concrete trigger keywords, and include at least one indirect trigger (a request that never names the domain). Never summarize the steps. - Bind every reference link to an observable trigger condition. Never leave a bare pointer to a reference. - References stay one level deep. Any reference over 100 lines opens with a table of contents. - Build at least three evals before writing extensive docs. - Match determinism to fragility: a deterministic script for fragile or repeated mechanical steps, prose for judgment calls. - Imperative voice, no second person. No em-dashes or en-dashes in any shipped skill or doc (use commas, periods, parentheses, colons). ## Route the authoring task to its reference | Authoring task | Open | |---|-...