[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AV44YGJS3DBNJ3CKZ710TX":3,"skill-same:01M7AV44YGJS3DBNJ3CKZ710TX":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7AV44YGJS3DBNJ3CKZ710TX","dsh-trim-cot-leakage",null,"Use when auditing or fixing prose that reads like a leaked reasoning transcript — dead design-session citations such as (decision N), audit item codes, or §N of uncommitted drafts; change narration such as \"used to\", \"no longer\", \"this cut\"; stack or review vantage (\"a later PR in this stack\", \"rejected in review\"); reviewer-addressed justifications; control-flow narration; or hedged planning residue in comments, JSDoc, docs, or Agent Notes.","vignesh050694\u002Fdeepseek_harness","vignesh050694","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28592443?v=4","01M7AV2QCAEBS9GXAGZZ4JRTV3","Vignesh V","01M7AV2QDMQ7J8CVBHKHWQPC9R",0,"MIT","https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002F.agents\u002Fskills\u002Fdsh-trim-cot-leakage\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dsh-trim-cot-leakage\ndescription: Use when auditing or fixing prose that reads like a leaked reasoning transcript — dead design-session citations such as (decision N), audit item codes, or §N of uncommitted drafts; change narration such as \"used to\", \"no longer\", \"this cut\"; stack or review vantage (\"a later PR in this stack\", \"rejected in review\"); reviewer-addressed justifications; control-flow narration; or hedged planning residue in comments, JSDoc, docs, or Agent Notes.\n---\n\n# Trimming Chain-of-Thought Leakage\n\nChain-of-thought leakage is prose whose vantage is the authoring session rather than the repository: it cites artifacts only that session could see, narrates the change instead of the state, or argues with a reviewer who has left. The fix is never deletion alone when a passage carries factual clauses — restate each so it stands at HEAD, then delete the transcript around it; a passage carrying none (an audit code, control-flow narration) is deleted outright. **REQUIRED BACKGROUND:** [dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md) owns the complete-proposition rule this skill applies; the [committed-artifact-citations note](..\u002F..\u002Fnotes\u002Fimplemented\u002Fprocess\u002F2026-08-09-committed-artifact-citations.md) owns the citation rule's rationale. It is guidance, not a script.\n\n## The one test\n\nFor every suspect passage ask: **could a reader at HEAD, with no access to any session transcript, PR thread, or uncommitted draft, resolve every reference and verify every claim?** If no, restate the surviving facts from the repository's vantage and delete the rest. If yes, it is not leakage, however historical it sounds — but resolvability only clears this skill's bar: on current-state surfaces (READMEs, docs, JSDoc) a resolvable change story is still change narration, and class 3 routes it to its sanctioned home.\n\n## Taxonomy\n\n1. **Dead design-session citations** — `(decision 7)`, `(audit C2)`, `design §4.7`, `plan §1.4`, phase labels (`T4`, `W3`, `P-I`), \"the design ledger\", \"(B ruling)\". If the decision has a committed owner, cite it by name and path; otherwise delete the citation and restate its factual clause to stand alone.\n2. **Stack and PR vantage** — \"a later PR in this stack\", \"this PR adds\", \"the previous commit\". State the shipped mechanism or the extension point; deferred work moves to a `TODO` marker or an issue reference.\n3. **Change narration and version stamps** — \"used to\", \"no longer\", \"the old X\", and indexical stamps (\"v1\", \"this cut\", \"today\", \"now\" contrasting with a past state). State the present behavior; a fixed regression becomes a present-tense counterfactual (\"without X, Y happens\"), never repo history (\"used to Y\").\n4. **Review choreography** — \"Rejected in review:\", \"the reviewer confirmed\", draft ordinals (\"v5 of this note\"), round attributions. Keep the surviving decision and rationale as plain fact; delete who said it when.\n5. **Reviewer-addressed justification** — \"the cast is safe — it simply…\", \"this is correct because…\". A comment arguing its own correctness addresses a reviewer, not a maintainer. State the invariant that makes the code safe, or delete the comment if the code shows it.\n6. **Restatement and derivation transcripts** — control-flow narration (\"first we X, then we Y\"), test walkthroughs, proofs of obvious branches. Delete; keep only a non-obvious contract or invariant.\n7. **Hedges and planning residue** — \"probably fine for now\", \"should be enough\", deferrals with no marker. Promote to `TODO`\u002F`FIXME` or restate as the actual bound; delete the hedge.\n8. **Authoring-language slips** — untranslated working-language fragments (端, 设计稿, `---- 私有 ----` separators) in prose whose language is otherwise English, or the reverse in a zh counterpart. Translate or delete.\n\n## What is not leakage\n\nUnaided citation passes fail in both directions by deleting durable references and keeping dead ones. Apply these keep rules as written; [examples](references\u002Fexamples.md) calibrates each:\n\n- **Issue references** — `#1470`, `TODO(name):`, \"issue #N owns the follow-up\" resolve at HEAD; keep them on any surface, including READMEs. Do not relocate them to Agent Notes.\n- **Merged-PR and issue citations inside Agent Notes and postmortems** — sanctioned evidence per the [documentation standard](..\u002F..\u002F..\u002Fdocs\u002FAGENTS.md)'s change-story routing.\n- **Suppression justifications** — `oxlint-disable … -- reason`, coverage-ignore reasons, empty-catch explanations are required prose; fix a false reason, never delete it.\n- **Counterfactual-present regression pins** — \"without X, Y happens\", \"a naive X would…\".\n- **Measured bounds** — \"(measured: 512 nests ≈ 0.15s)\" calibrating a constant; the provenance word \"measured\" is load-bearing.\n- **Runtime old\u002Fnew states** — \"the old connection drains before the new one accepts\" is runtime lifecycle, not change history.\n- **Historical stage names inside a note's change-story sections** — \"the first cut shipped X\" is current-state-safe there; indexical stamps (\"this cut\") stay banned everywhere.\n- **External references that resolve outside the repo by design** — standards sections (RFC 9110 §10.1.5), Figma frame names; the §-ban covers uncommitted internal drafts, not external standards or committed docs that own their §-numbering.\n- **Project voice and genre forms** — \"we\" as project voice; a note's Alternatives-considered section.\n\n## Workflow\n\n1. Scope and exclusions per [dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md): require an explicit scope; never touch `vendor\u002F`, `.agents\u002Fnotes\u002Farchived\u002F`, or recorded fixtures and snapshots — recorded model output and sealed history keep their original voice.\n2. Audit read-only first: run the [recall batteries](references\u002Frecall-batteries.md) (with `--hidden` so `.agents\u002F` is searched), then judge every hit semantically. The batteries are probes, not the definition — each review round of the original purge found cases the batteries missed, so also read the densest prose in scope (module JSDoc, READMEs, Agent Notes) without a pattern in hand.\n3. Fix owner-first per surface: generated catalogs → fix the source JSDoc or generator template, then regenerate; type-equivalence fences → fix the source JSDoc, then re-paste the page (`verify-type-equiv` pins them); model-visible strings → wording is behavior, so flag for a snapshot-backed change instead of silently rewording.\n4. Before deleting anything, enumerate the passage's propositions (prose-standard) and check the [overcorrection traps](references\u002Fexamples.md#overcorrection-traps): trims that flip an obligation into an endorsement, promote a hypothetical to a shipped feature, delete a true fact, or drop provenance.\n5. Verify: re-run the batteries expecting only sanctioned keeps, this skill's own directory, and the owning note's quoted evidence; confirm every remaining citation resolves at HEAD; run the gates for touched surfaces (`doc-sync` for docs, `verify-type-equiv`, `verify-translation-pairing`).\n","# Trimming Chain-of-Thought Leakage\n\nChain-of-thought leakage is prose whose vantage is the authoring session rather than the repository: it cites artifacts only that session could see, narrates the change instead of the state, or argues with a reviewer who has left. The fix is never deletion alone when a passage carries factual clauses — restate each so it stands at HEAD, then delete the transcript around it; a passage carrying none (an audit code, control-flow narration) is deleted outright. **REQUIRED BACKGROUND:** [dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md) owns the complete-proposition rule this skill applies; the [committed-artifact-citations note](..\u002F..\u002Fnotes\u002Fimplemented\u002Fprocess\u002F2026-08-09-committed-artifact-citations.md) owns the citation rule's rationale. It is guidance, not a script.\n\n## The one test\n\nFor every suspect passage ask: **could a reader at HEAD, with no access to any session transcript, PR thread, or uncommitted draft, resolve every reference and verify every claim?** If no, restate the surviving facts from the repository's vantage and delete the rest. If yes, it is not leakage, however historical it sounds — but resolvability only clears this skill's bar: on current-state surfaces (READMEs, docs, JSDoc) a resolvable change story is still change narration, and class 3 routes it to its sanctioned home.\n\n## Taxonomy\n\n1. **Dead design-session citations** — `(decision 7)`, `(audit C2)`, `design §4.7`, `plan §1.4`, phase labels (`T4`, `W3`, `P-I`), \"the design ledger\", \"(B ruling)\". If the decision has a committed owner, cite it by name and path; otherwise delete the citation and restate its factual clause to stand alone.\n2. **Stack and PR vantage** — \"a later PR in this stack\", \"this PR adds\", \"the previous commit\". State the shipped mechanism or the extension point; deferred work moves to a `TODO` marker or an issue reference.\n3. **Change narration and version stamps** — \"used to\", \"no longer\", \"the old X\", and indexical stamps (\"v1\", \"this cut\", \"today\", \"now\" contrasting with a past state). State the present behavior; a fixed regression becomes a present-tense counterfactual (\"without X, Y happens\"), never repo history (\"used to Y\").\n4. **Review choreography** — \"Rejected in review:\", \"the reviewer confirmed\", draft ordinals (\"v5 of this note\"), round attributions. Keep the surviving decision and rationale as plain fact; delete who said it when.\n5. **Reviewer-addressed justification** — \"the cast is safe — it simply…\", \"this is correct because…\". A comment arguing its own correctness addresses a reviewer, not a maintainer. State the invariant that makes the code safe, or delete the comment if the code shows it.\n6. **Restatement and derivation transcripts** — control-flow narration (\"first we X, then we Y\"), test walkthroughs, proofs of obvious branches. Delete; keep only a non-obvious contract or invariant.\n7. **Hedges and planning residue** — \"probably fine for now\", \"should be enough\", deferrals with no marker. Promote to `TODO`\u002F`FIXME` or restate as the actual bound; delete the hedge.\n8. **Authoring-language slips** — untranslated working-language fragments (端, 设计稿, `---- 私有 ----` separators) in prose whose language is otherwise English, or the reverse in a zh counterpart. Translate or delete.\n\n## What is not leakage\n\nUnaided citation passes fail in both directions by deleting durable references and keeping dead ones. Apply these keep rules as written; [examples](references\u002Fexamples.md) calibrates each:\n\n- **Issue references** — `#1470`, `TODO(name):`, \"issue #N owns the follow-up\" resolve at HEAD; keep them on any surface, including READMEs. Do not relocate them to Agent Notes.\n- **Merged-PR and issue citations inside Agent Notes and postmortems** — sanctioned evidence per the [documentation standard](..\u002F..\u002F..\u002Fdocs\u002FAGENTS.md)'s change-story routing.\n- **Suppression justifications** — `oxlint-disable … -- reason`, coverage-ignore reasons, empty-catch explanations are required prose; fix a false reason, never delete it.\n- **Counterfactual-present regression pins** — \"without X, Y happens\", \"a naive X would…\".\n- **Measured bounds** — \"(measured: 512 nests ≈ 0.15s)\" calibrating a constant; the provenance word \"measured\" is load-bearing.\n- **Runtime old\u002Fnew states** — \"the old connection drains before the new one accepts\" is runtime lifecycle, not change history.\n- **Historical stage names inside a note's change-story sections** — \"the first cut shipped X\" is current-state-safe there; indexical stamps (\"this cut\") stay banned everywhere.\n- **External references that resolve outside the repo by design** — standards sections (RFC 9110 §10.1.5), Figma frame names; the §-ban covers uncommitted internal drafts, not external standards or committed docs that own their §-numbering.\n- **Project voice and genre forms** — \"we\" as project voice; a note's Alternatives-considered section.\n\n## Workflow\n\n1. Scope and exclusions per [dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md): require an explicit scope; never touch `vendor\u002F`, `.agents\u002Fnotes\u002Farchived\u002F`, or recorded fixtures and snapshots — recorded model output and sealed history keep their original voice.\n2. Audit read-only first: run the [recall batteries](references\u002Frecall-batteries.md) (with `--hidden` so `.agents\u002F` is searched), then judge every hit semantically. The batteries are probes, not the definition — each review round of the original purge found cases the batteries missed, so also read the densest prose in scope (module JSDoc, READMEs, Agent Notes) without a pattern in hand.\n3. Fix owner-first per surface: generated catalogs → fix the source JSDoc or generator template, then regenerate; type-equivalence fences → fix the source JSDoc, then re-paste the page (`verify-type-equiv` pins them); model-visible strings → wording is behavior, so flag for a snapshot-backed change instead of silently rewording.\n4. Before deleting anything, enumerate the passage's propositions (prose-standard) and check the [overcorrection traps](references\u002Fexamples.md#overcorrection-traps): trims that flip an obligation into an endorsement, promote a hypothetical to a shipped feature, delete a true fact, or drop provenance.\n5. Verify: re-run the batteries expecting only sanctioned keeps, this skill's own directory, and the owning note's quoted evidence; confirm every remaining citation resolves at HEAD; run the gates for touched surfaces (`doc-sync` for docs, `verify-type-equiv`, `verify-translation-pairing`).\n",{"name":5,"description":7},"chore\u002Fremove-chinese-i18n","06fa4a35d98953badf69a1df45b1d70e250282ca",".agents\u002Fskills\u002Fdsh-trim-cot-leakage","https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness","https:\u002F\u002Fgithub.com\u002Fvignesh050694","calpyte.com","2026-09-21 12:05:15",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add vignesh050694\u002Fdeepseek_harness --skill dsh-trim-cot-leakage",{"tool":37,"command":38},"bunx","bunx skills add vignesh050694\u002Fdeepseek_harness --skill dsh-trim-cot-leakage",{"tool":40,"command":41},"pnpm","pnpm dlx skills add vignesh050694\u002Fdeepseek_harness --skill dsh-trim-cot-leakage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002F.agents\u002Fskills\u002Fdsh-trim-cot-leakage\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fexamples.md","REFERENCE","参考文档",11298,"https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002F.agents\u002Fskills\u002Fdsh-trim-cot-leakage\u002Freferences\u002Fexamples.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Frecall-batteries.md",3661,"https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002F.agents\u002Fskills\u002Fdsh-trim-cot-leakage\u002Freferences\u002Frecall-batteries.md",[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AV4XEMT19VE71MGJA7Z70R","user-only-skill","Prove model-disabled skills stay outside the model catalog.","https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002Fexamples\u002Facp-agent\u002Ftests\u002Fsnapshots\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fuser-only-skill\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AV4W4MFDZH6X15H1PN2QA8","snapshot-skill","Exercise project skill discovery and loading in snapshot tests.","https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002Fexamples\u002Facp-agent\u002Ftests\u002Fsnapshots\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fsnapshot-skill\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AV4TPBT8H7JH9QEKSJB00R","model-only-skill","Prove user-disabled skills remain available to the model.","https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002Fexamples\u002Facp-agent\u002Ftests\u002Fsnapshots\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fmodel-only-skill\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AV4PKKWSTASVS6X2DSG4X9","editing-cordis-compositions","Use when creating, changing, or validating a Cordis composition for this harness — writing or editing an agent preset, adding or removing a plugin row, deciding whether something belongs to the host composition or to one session, checking whether a preset you authored actually mounts, or diagnosing a row that mounted but contributed nothing.","https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002Fapps\u002Fcli\u002Fconfig\u002Fagent-presets\u002Fcordis\u002Fskills\u002Fediting-cordis-compositions\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AV4G69RJK29FFHRADKVNYW","cordis-plugin-development","Create, modify, debug, or extend dynamic Cordis Plugins, including Host Services and Events, Client Slot and theme UI, Package-private Client-to-Host calls, dynamic Tools, version updates, approval failures, and runtime diagnostics. Use this Skill to route a user request to the correct platform and Inspect Provider, then define, run, repair, or roll back the Plugin.","https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002Fapps\u002Fcli\u002Fconfig\u002Fagent-presets\u002Fcordis\u002Fskills\u002Fcordis-plugin-development\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7AV4AHM7FRMHKHQJCBKKE1R","record-browser-gif","Record browser or Web UI interaction demos as optimized GIFs using the available built-in browser, state-based frame capture, and deterministic encoding, then publish to a dedicated assets branch when the task includes attaching the GIF to a pull request. Use when asked to make, record, or generate a GIF that demonstrates a browser workflow, and for every pull request that changes product-user-visible GUI behavior, which MUST include a GIF recorded from the pull request's real server and model flow.","https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002F.agents\u002Fskills\u002Frecord-browser-gif\u002FSKILL.md",[],[]]