Debt ledger

Skill yuri-semenenko/ai-engineering-workspace/claude-code/.claude/skills/debt-ledger

Collect the deliberate-simplicity tradeoff annotations left in the code (`// TRADEOFF(ceiling: ...; upgrade: ...): ...`) across the repo into a single ledger — location, ceiling, upgrade path, note. Use for "debt ledger", "list tradeoffs", "what shortcuts did we take", "debt-ledger". Pairs with the TRADEOFF convention in CLAUDE.md / persona and the annotations written by /lazy.From its SKILL.md

Install

npx -y skills add yuri-semenenko/ai-engineering-workspace --skill debt-ledger

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 326 tokens by cl100k_base, as published. Nobody here has run it

Debt Ledger

Surface every deliberate, named tradeoff in the codebase so accepted debt stays visible instead of rotting as an anonymous // TODO.

Convention being collected

The persona's tradeoff annotation (see CLAUDE.md):

// TRADEOFF(ceiling: <what this solution maxes out at>; upgrade: <path when the ceiling is hit>): <short note>

The comment marker varies by language (//, #, --, ). Match the TRADEOFF( token, not the comment syntax.

Steps

Grep the repo for the TRADEOFF( token across source files (respect .gitignore; skip vendored/node_modules).
Parse each hit into: file, line, ceiling, upgrade path, note.
Flag malformed annotations — a TRADEOFF that omits ceiling: or upgrade: is incomplete; list it under a separate "needs detail" group rather than silently dropping it.
Report as a single ledger.

Output

TRADEOFF ledger — <N> entries (<M> need detail)

Location (`file:line`)	Ceiling	Upgrade path	Note

Then a "needs detail" list for malformed entries. Do not editorialize or auto-fix — this is a read-only inventory. If zero annotations exist, say so plainly (it may mean the convention is not being used, not that there's no debt).

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most finance skills give in 326 tokens

Counted across 469 of the 469 authors here whose files we hold, read 2026-08-07

Extract date vendor amount and descriptionin 15 of 469, across 3 files
Scan folder for invoice filesin 14 of 469, across 2 files
Rename files to standard formatin 14 of 469, across 2 files
Show organization plan before movingin 14 of 469, across 2 files
Generate summary CSVin 14 of 469, across 2 files
Organize files by categoryin 13 of 469, across 1 file
Preserve original filesin 13 of 469, across 1 file
Flag files missing critical infoin 13 of 469, across 1 file
Produce the requested output filein 9 of 469, across 4 files
Build best, base, and worst case scenariosin 9 of 469, across 5 files
Implement backoff if rate limit errors occurin 8 of 469, across 3 files
Determine the weighted average cost of capitalin 8 of 469, across 4 files

Said here and by no other author read

Search the repository for the TRADEOFF token
Skip vendored and node_modules directories
Parse each match into file, line, ceiling, upgrade, and note
Flag annotations missing ceiling or upgrade details
List malformed annotations in a separate group
Report the collected annotations as a ledger

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.