[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E69714H5Q1ZGQDACP1TZH9":3,"skill-same:01M7E69714H5Q1ZGQDACP1TZH9":57},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7E69714H5Q1ZGQDACP1TZH9","neosis-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.","sainibhaowal\u002FNeoSIS_Hanness","sainibhaowal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F251900306?v=4","01M7E67EMQ2WCJPNWWNV1GREBN","Ravinder Singh","01M7E67EN9BVA8YDGRQRHA9WYZ",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsainibhaowal\u002FNeoSIS_Hanness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fneosis-trim-cot-leakage\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: neosis-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:** [neosis-prose-standard](..\u002Fneosis-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 evidence 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 [neosis-prose-standard](..\u002Fneosis-prose-standard\u002FSKILL.md): require an explicit scope; never touch `vendor\u002F` or `.agents\u002Fnotes\u002Farchived\u002F`. Recorded fixtures and snapshots are derivatives, not prose targets: change the owning source or scenario and regenerate them only when an authorized behavior change requires new evidence.\n2. Audit read-only first: run the [recall batteries](references\u002Frecall-batteries.md) (with `--hidden` so `.agents\u002F` is searched), calibrating each probe against a known positive and a near-miss negative before trusting its output, 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 → trace every consumer, fix the source JSDoc or generator template, then regenerate all derivatives; type-equivalence fences → fix the source JSDoc, then re-paste both bilingual pages (`verify-type-equiv` pins them); bilingual prose → update the counterpart minimally and re-record it through the [lightweight routine](..\u002F..\u002F..\u002Fdocs\u002FAGENTS.md#writing-rules); bilingual fences → copy the corrected verbatim block byte-for-byte into both sides per [neosis-doc](..\u002Fneosis-doc\u002FSKILL.md), then re-record the pair; model- or user-visible strings → route through [neosis-prose-standard](..\u002Fneosis-prose-standard\u002FSKILL.md) and change only with owning behavior evidence, otherwise leave unchanged and report the deferral.\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 the evidence source.\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:** [neosis-prose-standard](..\u002Fneosis-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 evidence 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 [neosis-prose-standard](..\u002Fneosis-prose-standard\u002FSKILL.md): require an explicit scope; never touch `vendor\u002F` or `.agents\u002Fnotes\u002Farchived\u002F`. Recorded fixtures and snapshots are derivatives, not prose targets: change the owning source or scenario and regenerate them only when an authorized behavior change requires new evidence.\n2. Audit read-only first: run the [recall batteries](references\u002Frecall-batteries.md) (with `--hidden` so `.agents\u002F` is searched), calibrating each probe against a known positive and a near-miss negative before trusting its output, 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 → trace every consumer, fix the source JSDoc or generator template, then regenerate all derivatives; type-equivalence fences → fix the source JSDoc, then re-paste both bilingual pages (`verify-type-equiv` pins them); bilingual prose → update the counterpart minimally and re-record it through the [lightweight routine](..\u002F..\u002F..\u002Fdocs\u002FAGENTS.md#writing-rules); bilingual fences → copy the corrected verbatim block byte-for-byte into both sides per [neosis-doc](..\u002Fneosis-doc\u002FSKILL.md), then re-record the pair; model- or user-visible strings → route through [neosis-prose-standard](..\u002Fneosis-prose-standard\u002FSKILL.md) and change only with owning behavior evidence, otherwise leave unchanged and report the deferral.\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 the evidence source.\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},"main","3a15a39c058d519cfc6e0a1064e3db7645020951",".agents\u002Fskills\u002Fneosis-trim-cot-leakage",0,"https:\u002F\u002Fgithub.com\u002Fsainibhaowal\u002FNeoSIS_Hanness","https:\u002F\u002Fgithub.com\u002Fsainibhaowal","https:\u002F\u002Fportfolio.faimatrix.com\u002F","I am independent developer full stack end to end, system and design Architect,  with IT Security profession and AI\u002FML Researcher and All Rounder.","2026-10-08 05:56:04",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add sainibhaowal\u002FNeoSIS_Hanness --skill neosis-trim-cot-leakage",{"tool":39,"command":40},"bunx","bunx skills add sainibhaowal\u002FNeoSIS_Hanness --skill neosis-trim-cot-leakage",{"tool":42,"command":43},"pnpm","pnpm dlx skills add sainibhaowal\u002FNeoSIS_Hanness --skill neosis-trim-cot-leakage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsainibhaowal\u002FNeoSIS_Hanness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fneosis-trim-cot-leakage\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fexamples.md","REFERENCE","参考文档",12566,"https:\u002F\u002Fgithub.com\u002Fsainibhaowal\u002FNeoSIS_Hanness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fneosis-trim-cot-leakage\u002Freferences\u002Fexamples.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Frecall-batteries.md",5044,"https:\u002F\u002Fgithub.com\u002Fsainibhaowal\u002FNeoSIS_Hanness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fneosis-trim-cot-leakage\u002Freferences\u002Frecall-batteries.md",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7E6AAVHNHMQZRNX0H0BQ2Q6","user-only-skill","Prove model-disabled skills stay outside the model catalog.","https:\u002F\u002Fgithub.com\u002Fsainibhaowal\u002FNeoSIS_Hanness\u002Fblob\u002Fmain\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.neosis\u002Fskills\u002Fuser-only-skill\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7E6A9M5CDC5QF5V4BBDKQX2","snapshot-skill","Exercise project skill discovery and loading in snapshot tests.","https:\u002F\u002Fgithub.com\u002Fsainibhaowal\u002FNeoSIS_Hanness\u002Fblob\u002Fmain\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.neosis\u002Fskills\u002Fsnapshot-skill\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7E6A717Z08V63NQWH8625B8","model-only-skill","Prove user-disabled skills remain available to the model.","https:\u002F\u002Fgithub.com\u002Fsainibhaowal\u002FNeoSIS_Hanness\u002Fblob\u002Fmain\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.neosis\u002Fskills\u002Fmodel-only-skill\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7E6A49THR42Q3908RGRJD52","office-xlsx","Read, create, and modify Excel workbooks (.xlsx), including cell values, formulas, formatting, and pandas analysis. Use when an Excel workbook is an input or deliverable.","https:\u002F\u002Fgithub.com\u002Fsainibhaowal\u002FNeoSIS_Hanness\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-xlsx\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7E6A27V0BQCQ9JDZ8CSMP75","office-pptx","Create, read, edit, and check PowerPoint presentations (.pptx), including slide text, tables, images, and charts. Use when a PPTX file is an input or requested deliverable.","https:\u002F\u002Fgithub.com\u002Fsainibhaowal\u002FNeoSIS_Hanness\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-pptx\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7E69YX6DNJE6BSJKADKDJFC","office-docx","Create, read, edit, and check Word documents (.docx), including reports, letters, and formatted tables. Use when a DOCX file is an input or requested deliverable.","https:\u002F\u002Fgithub.com\u002Fsainibhaowal\u002FNeoSIS_Hanness\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-docx\u002FSKILL.md",[],[]]