← ClaudeAtlas

judge-a-skilllisted

Put one skill on trial before adopting it — a prosecutor argues why it is not needed, a defence argues why it is, and a judge decides from a fixed set of verdicts, including the one that matters most - reject the skill, take these parts. Charges must cite something checkable in the artefact, a clean verdict is a first-class outcome, and the two cases are rated so a close call is visible as a close call. Ships a runnable recorder that refuses a charge with no evidence. Use when deciding whether to adopt, keep, fork or drop a skill; after reading an external or marketplace skill; when asked to review, audit, judge or score a skill; when a skill "seems useful" but nobody can say why; when several skills overlap and one has to go.
ubik-dsh/deepseek-harness-skills · ★ 0 · AI & Automation · score 63
Install: claude install-skill ubik-dsh/deepseek-harness-skills
# Judging a skill A score says how good a skill is at being a skill. It does not say **whether it should exist**, and that is the question that decides adoption. Three rival skills were put through this and all three were rejected — while each contained one idea worth keeping. A rubric would have scored all three respectably and told nobody what to do. So the shape is a hearing, not a table: > **Prosecutor** — why this is not needed. **Defence** — why it is. **Judge** — a > verdict from a fixed list, and a rating of the two arguments, because a close call is > information. --- ## Step 0 — Is a hearing worth it? Do not convene one for everything. A hearing costs three readings and pays only when the question is **consequential** and either **contested** or **checkable**. If the skill is obviously thin, say so and stop. If you already know it should be kept and why, say that and stop. **But beware the triage trap**, and this one is not optional: > The gate is run by **the same judgement whose blind spots the hearing exists to catch**. > The skills you are most confidently wrong about are exactly the ones that will not > trip it. So: if the user asked for a hearing, run it regardless of your certainty. And for a skill that will be adopted, let **stakes** decide, not your felt confidence. ## Step 1 — The structural check, before any argument A hearing about the content of a malformed file is a waste. Check the mechanical things first, and **do not proceed to argument w