New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Alego Trim Cot Leakage

by singula-ai in singula-ai/alego

A skill your agent uses 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…

MITAuto-check passedMedia & Creative

Install Alego Trim Cot Leakage

skills CLI
$ npx skills add singula-ai/alego --skill alego-trim-cot-leakage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install singula-ai/alego alego-trim-cot-leakage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/singula-ai/alego.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/alego-trim-cot-leakage .claude/skills/alego-trim-cot-leakage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
alego-trim-cot-leakage
GitHub stars
109
Used in
1 other repo
Token cost
~1.9k tokens
SKILL.md length
950 words
Files
3 (incl. references)
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses 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…

  • Works in 8 steps: Dead design-session citations —… → Stack and PR vantage — "a later PR in… → Change narration and version stamps —… → …
  • Fixing prose that reads like a leaked reasoning transcript — dead design-session citations such as (decision N)
  • SKILL.md covers The one test, Taxonomy, What is not leakage and Workflow
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Alego Trim Cot Leakage is an agent skill from singula-ai/alego. 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.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/examples.md` and `references/recall-batteries.md`).

It sits in Media & Creative, covering Text to speech and voice, Technical documentation and Citation management. The repository describes itself as: Build AI Agents like playing LEGOs. Everything is a Plugin. The licence is MIT.

When your agent uses it

  • Fixing prose that reads like a leaked reasoning transcript — dead design-session citations such as (decision N)
  • Audit item codes
  • §N of uncommitted drafts
  • Change narration such as used to

Example prompts

  • “used to”
  • “no longer”
  • “this cut”
  • “/alego-trim-cot-leakage”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Dead design-session citations — (decision 7), (audit C2), design §4.7, plan §1.4, phase labels (T4, W3, P-I), "the design ledger", "(B…
  2. Stack and PR vantage — "a later PR in this stack", "this PR adds", "the previous commit". State the shipped mechanism or the extension…
  3. Change narration and version stamps — "used to", "no longer", "the old X", and indexical stamps ("v1", "this cut", "today", "now"…
  4. Review choreography — "Rejected in review:", "the reviewer confirmed", draft ordinals ("v5 of this note"), round attributions. Keep the…
  5. Reviewer-addressed justification — "the cast is safe — it simply…", "this is correct because…". A comment arguing its own correctness…
  6. Restatement and derivation transcripts — control-flow narration ("first we X, then we Y"), test walkthroughs, proofs of obvious branches…
  7. Hedges and planning residue — "probably fine for now", "should be enough", deferrals with no marker. Promote to TODO/FIXME or restate as…
  8. Authoring-language slips — untranslated working-language fragments (端, 设计稿, ---- 私有 ---- separators) in prose whose language is otherwise…

What it can do on your machine

Read from SKILL.md and the folder at commit a79fe9a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Alego Trim Cot Leakage loads about 1.9k tokens when it runs, and up to ~6.3k if it reads all its reference files. Until then it costs about 117 tokens; SKILL.md has 950 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~117
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from singula-ai/alego at commit a79fe9a, republished under its MIT licence (© singula-ai). 950 words, ~1,904 tokens.

Download SKILL.mdSave it as .claude/skills/alego-trim-cot-leakage/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
alego-trim-cot-leakage
description
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.

Trimming Chain-of-Thought Leakage

Chain-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: alego-prose-standard owns the complete-proposition rule this skill applies; the committed-artifact-citations note owns the citation rule's rationale. It is guidance, not a script.

The one test

For 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.

Taxonomy

  1. 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.
  2. 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.
  3. 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").
  4. 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.
  5. 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.
  6. 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.
  7. Hedges and planning residue — "probably fine for now", "should be enough", deferrals with no marker. Promote to TODO/FIXME or restate as the actual bound; delete the hedge.
  8. 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.
Show full SKILL.md (477 more words)Show less

What is not leakage

Unaided citation passes fail in both directions by deleting durable references and keeping dead ones. Apply these keep rules as written; examples calibrates each:

  • 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.
  • Merged-PR and issue citations inside Agent Notes and postmortems — sanctioned evidence per the documentation standard's change-story routing.
  • Suppression justifications — oxlint-disable … -- reason, coverage-ignore reasons, empty-catch explanations are required prose; fix a false reason, never delete it.
  • Counterfactual-present regression pins — "without X, Y happens", "a naive X would…".
  • Measured bounds — "(measured: 512 nests ≈ 0.15s)" calibrating a constant; the evidence word "measured" is load-bearing.
  • Runtime old/new states — "the old connection drains before the new one accepts" is runtime lifecycle, not change history.
  • 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.
  • 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.
  • Project voice and genre forms — "we" as project voice; a note's Alternatives-considered section.

Workflow

  1. Scope and exclusions per alego-prose-standard: require an explicit scope; never touch vendor/ or .agents/notes/archived/. 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.
  2. Audit read-only first: run the recall batteries (with --hidden so .agents/ 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.
  3. 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; bilingual fences → copy the corrected verbatim block byte-for-byte into both sides per alego-doc, then re-record the pair; model- or user-visible strings → route through alego-prose-standard and change only with owning behavior evidence, otherwise leave unchanged and report the deferral.
  4. Before deleting anything, enumerate the passage's propositions (prose-standard) and check the 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.
  5. 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).

© singula-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/alego-trim-cot-leakage of singula-ai/alego.

  • SKILL.md
  • references/examples.md
  • references/recall-batteries.md

Open the folder on GitHubat commit a79fe9a

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in singula-ai/alego, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Alego Trim Cot Leakage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Alego Trim Cot Leakage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Alego Trim Cot Leakage this skillsingula-ai/alego1091 repos~1.9kAutomated safety check: PassMIT
Research Lookupdavila7/claude-code-templates33k9 repos~5kAutomated safety check: NotesMIT
Press Conference Revision Evidence Boundlensback940701/Evidence-Bound-Press-Conference-Revision-Skill259—~2.2kAutomated safety check: PassMIT
Sweep Commentsahmetb/dotfiles139—~2kAutomated safety check: PassApache-2.0
Gaik Add ExamplesGAIK-project/gaik-toolkit100—~2.4kAutomated safety check: NotesMIT
Comment Judgefmflurry/settings-opencode171—~2.5kAutomated safety check: PassMIT

Similar skills

  • Research Lookup

    davila7/claude-code-templates

    Look up current research information using Perplexity's Sonar Pro Search or Sonar Reasoning Pro models through OpenRouter.

    33k GitHub starsUsed in 9 repos~5k tokens
    Research & ScienceAuto-check: notes

  • Press Conference Revision Evidence Bound

    lensback940701/Evidence-Bound-Press-Conference-Revision-Skill

    Diagnose and revise defensive academic writing while preserving claim ceilings, evidence status, scope conditions, rival explanations, and conceptual hierarchy.

    259 GitHub stars~2.2k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed

  • Sweep Comments

    ahmetb/dotfiles

    Hold code comments and docstrings to a strict quality bar. An agent skill from ahmetb/dotfiles.

    139 GitHub stars~2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Gaik Add Examples

    GAIK-project/gaik-toolkit

    Adds or updates working code examples for GAIK toolkit components and pipelines in implementationlayer/examples/.

    100 GitHub stars~2.4k tokensUpdated 2 days ago
    AI & LLM EngineeringAuto-check: notes

  • Comment Judge

    fmflurry/settings-opencode

    LLM-as-a-judge rubric for code comments (forbidden, false, stale, narration, noise, keep).

    171 GitHub stars~2.5k tokensUpdated 4 days ago
    EducationAuto-check passed

  • Wiki Page Writer

    microsoft/skills

    Official

    Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth.

    3.1k GitHub starsUsed in 1 repo~1.5k tokens
    DevelopmentAuto-check passed

More from singula-ai/alego

All 20 skills in this repo

  • Record Browser Gif

    singula-ai/alego

    Record browser or Web UI interaction demos as optimized GIFs using the available browser-control workflow, optional Playwright Videos for higher capture frame rates, and deterministic encoding, then…

    109 GitHub starsUsed in 1 repo~4.1k tokens
    Auto-check: notes

  • Alego Archive Agent Notes

    singula-ai/alego

    A skill your agent uses when adding, auditing, pruning, archiving, restoring, or reviewing Agent Notes in alego; checks every new note for superseded active records, deletes small UI and purely…

    109 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

  • Alego Merging Stacked PRs

    singula-ai/alego

    A skill your agent uses when landing a stack of dependent GitHub PRs (A ← B ← C, where each bases on the one below) onto master, merging a PR whose base is another open PR's branch, or whenever a…

    109 GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Editing Cordis Compositions

    singula-ai/alego

    A skill your agent uses when creating, changing, or validating an agent preset or other Cordis composition for this harness, including deciding host versus preset placement and checking that an…

    109 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed

  • Office DOCX

    singula-ai/alego

    Create, read, edit, and check Word documents (.docx), including reports, letters, and formatted tables.

    109 GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed

  • Office PPTX

    singula-ai/alego

    Create, read, edit, and check PowerPoint presentations (.pptx), including slide text, tables, images, and charts.

    109 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

Categories

Questions about Alego Trim Cot Leakage

What does Alego Trim Cot Leakage do?

A skill your agent uses 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…. Alego Trim Cot Leakage is an agent skill from singula-ai/alego. 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.

When should I use Alego Trim Cot Leakage?

Alego Trim Cot Leakage fits situations like: fixing prose that reads like a leaked reasoning transcript — dead design-session citations such as (decision N); audit item codes; §N of uncommitted drafts; change narration such as used to.

How do I install Alego Trim Cot Leakage in Claude Code?

Run `npx skills add singula-ai/alego --skill alego-trim-cot-leakage -a claude-code`. Or copy the skill folder (.agents/skills/alego-trim-cot-leakage in singula-ai/alego) into .claude/skills/alego-trim-cot-leakage in your project. Claude Code loads it when a task matches its description.

How do I install Alego Trim Cot Leakage in Codex?

Run `npx skills add singula-ai/alego --skill alego-trim-cot-leakage -a codex`. Or copy the skill folder (.agents/skills/alego-trim-cot-leakage in singula-ai/alego) into .agents/skills/alego-trim-cot-leakage in your project. Codex loads it when a task matches its description.

Can I use Alego Trim Cot Leakage in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add singula-ai/alego --skill alego-trim-cot-leakage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/alego-trim-cot-leakage, .gemini/skills/alego-trim-cot-leakage, .github/skills/alego-trim-cot-leakage and .opencode/skills/alego-trim-cot-leakage in your project.

What does Alego Trim Cot Leakage need to run?

SKILL.md names no scripts, command-line tools or credentials: Alego Trim Cot Leakage is instructions for the agent only.

Does Alego Trim Cot Leakage access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Alego Trim Cot Leakage safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Alego Trim Cot Leakage use?

Alego Trim Cot Leakage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Alego Trim Cot Leakage use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.4k tokens, read only when the agent opens those files.

What are the alternatives to Alego Trim Cot Leakage?

Skills that share tags, products or a category with Alego Trim Cot Leakage: Research Lookup (davila7/claude-code-templates, 33k stars), Press Conference Revision Evidence Bound (lensback940701/Evidence-Bound-Press-Conference-Revision-Skill, 259 stars), Sweep Comments (ahmetb/dotfiles, 139 stars) and Gaik Add Examples (GAIK-project/gaik-toolkit, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Alego Trim Cot Leakage?

singula-ai (a GitHub organization) maintains it in singula-ai/alego, which has 109 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on September 28, 2026.

Source: singula-ai/alego on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.