← ClaudeAtlas

route-a-tasklisted

Decide which skill a task requires, and which are mandatory rather than optional. A regulation rather than a menu - untrusted content is scanned before it is used, a search happens before a skill is written, hardware symptoms are read before anything is changed, a result that could quietly be wrong is checked by something that did not produce it, an independent agent reads a skill before it is called done. Covers what forces a skill with no judgement allowed, what forces it under a condition, what is only worth considering, what to do when two apply, and what to do when none does. Ships a router that prints the obligations in order with the literal step for each, and a test of its own triggers. Use when starting a task whose approach is not obvious, when taking something from the internet, when writing or changing a skill, when a machine misbehaves, when a score or check is being designed, when about to report a number, a proof or a measurement, or when unsure whether a rule applies at all.
ubik-dsh/deepseek-harness-skills · ★ 0 · API & Backend · score 63
Install: claude install-skill ubik-dsh/deepseek-harness-skills
# Which tool, and whether you have a choice A catalogue says what each tool does. **A regulation says which one you are obliged to pick.** The difference is not decoration. A menu is read once and forgotten; **an obligation is checked.** The family this belongs to has seven skills and, until this one, nothing that said *in this situation, this is not optional* — so every rule in it was advice, and advice loses to the first plausible shortcut. **The master with a task reads the regulation and knows the tool. Not because the regulation is longer, but because it says which line is a requirement.** --- ## What a gate is for **A gate is not a checklist to consult.** It is a forcing function, and the difference decides whether the regulation works. An agent that has forgotten a step does not need to be pointed at a skill. **It needs the step handed to it at the moment it is standing at the gate** — or "I forgot, let us redo it" is the normal outcome, and the work is thrown away rather than corrected. So every gate below carries **the literal step**, the command where there is one, the rule that decides, and the record it owes. `route.py` prints the steps. **An agent reading only the gate can comply without going anywhere else.** And what follows from that: **a gate that was passed without a record can be found at the end.** ```bash python scripts/route.py "download a skill and publish it" --verify record.json ``` **The record is a mapping from a gate to the evidence, and