From 89f505f7f81a1cfef5ce2befe3ac1d711712711f Mon Sep 17 00:00:00 2001 From: firaen22 Date: Fri, 24 Jul 2026 23:24:52 +0800 Subject: [PATCH] =?UTF-8?q?skill-authoring=20=C2=A72:=20a=20capability=20y?= =?UTF-8?q?ou=20describe=20for=20a=20weaker=20executor=20is=20a=20claim=20?= =?UTF-8?q?to=20verify=20live=20before=20the=20doc=20ships?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A skill/runbook that tells a weaker model a capability exists ('the engine auto-searches every category', 'this flag does X') is executed verbatim by the reader least able to notice it is wrong — shipping it unverified ships a false instruction. When the behavior is new or just-patched, prove it against a real gate, THEN finalize the doc; a scarce/expiring live session argues for verifying FIRST, not for shipping on the theory it probably works. Positive twin of §3's capability-negative rule. Class-distilled from a mining pass over the owner's own sessions (no code taken). Co-Authored-By: Claude Fable 5 --- skills/skill-authoring/SKILL.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/skills/skill-authoring/SKILL.md b/skills/skill-authoring/SKILL.md index 30df5c0..5af426d 100644 --- a/skills/skill-authoring/SKILL.md +++ b/skills/skill-authoring/SKILL.md @@ -84,6 +84,19 @@ artifact-producing step. - What cannot be verified is labeled `unverified` or `user-must-provide` — never silently invented. Unproven ideas stay labeled open/candidate; no oversell. +- **Verify-before-you-write-it bites hardest on a capability you describe for a + weaker executor** (`unprobed` — private incident as shape; see Provenance). + "The engine auto-searches every category", "this flag does X" — a weak model + executes such a line verbatim, with none of your context to catch it when it + is wrong, so an unverified capability claim is a false instruction to the one + reader least able to notice. When the behavior is new or just-patched, order + it: prove it against a real gate (ground-truth-gates), THEN finalize the doc + that describes it. A scarce live session (an auth window about to expire, a + costly remote setup) argues for verifying FIRST, not for shipping the doc on + the theory it probably works. + ❌ drafting "the engine now self-heals across categories" into the skill + while the self-heal fix is still unproven, to spend the login session before + it expires. - Embed the knowledge itself; do not make private paths or one person's memory a load-bearing reference. A hard-coded machine-absolute path is worse than a broken link: a stale duplicate clone resolves *silently* to an @@ -880,3 +893,12 @@ its scope-install / invoke-by-name / prune mitigation ladder (MathWorks field-of-use license — ideas only, no text). Both ship `unprobed` per the covenant; their probes join the private round-5 queue — the catalog-collision rule's is directly runnable against this pack's own 12 skills. +The §2 verify-capability-before-shipping-the-doc rule (2026-07-24) is +class-distilled from a mining pass over the owner's own sessions (no code +taken): with a scarce authenticated remote session about to expire, doc edits +describing a just-patched self-heal behavior were held until a regression gate +proved the behavior, on the explicit reasoning that telling the weaker model +"the engine auto-searches all categories" is a capability claim that must be +verified live first or it ships a false instruction. Ships `unprobed` per the +covenant; +its probe joins the private round-5 queue.