context-doctor

Solid

Reduces token waste in Claude Code sessions across two axes — context footprint (auto-generates .claudeignore, guides over-read files and /clear timing) and command output (routes to a command-output proxy/hook such as rtk to trim verbose CLI stdout). In hub environments, regularly audits bloated CLAUDE.md/MEMORY.md/memory/*.md files and proposes compression. Usable standalone without a hub clone.

AI & Automation 16 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
41
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# context-doctor — Token Efficiency Diagnosis + Automatic Prescription Diagnoses the main causes of session token waste and prescribes immediate remedies: 1. No `.claudeignore` → unnecessary files loaded wholesale into context 2. Repeated full reads of large files → paying the same cost N times 3. Not using `/clear` after direction changes → continuing work with accumulated noise 4. Verbose CLI output → every `git`/`ls`/build/test call floods context with stdout (a *different* layer from 1–3 — see §Command-Output Reduction) **Two reduction axes — keep them distinct.** Causes 1–3 are the **context-footprint** axis (what gets read *into* context: files, history). Cause 4 is the **command-output** axis (tokens produced *by* the tools you run). `.claudeignore` cannot touch command output, and a command-output proxy cannot touch file reads — they are complementary, not substitutes. (Step 3.5 below adds an optional **third**, orthogonal lever — provider-side cache billing — distinct from both.) **Standalone install** — this skill works normally with plugin install only, without cloning the full meta-harness. **Built-in `/doctor` first (sister anchor, 2026-07-25)**: since the Claude 5 generation, the official `/doctor` command claims skill/CLAUDE.md rightsizing ("The new rules of context engineering for Claude 5 generation models" — https://claude.com/blog/the-new-rules-of-context-engineering-for-claude-5-generation-models). Run the built-in first when available — its scope is s...

Details

Author
chrono-meta
Repository
chrono-meta/forge-harness
Created
4 months ago
Last Updated
today
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

context-doctor

Visualize and diagnose OpenClaw context window usage. Generates a terminal-rendered breakdown showing workspace files (status, chars, tokens), installed skills inventory, and token budget allocation across bootstrap components. Use when: (1) user asks about context window health or token usage, (2) debugging agent quality degradation ("agent got dumber"), (3) after editing workspace files to verify impact, (4) auditing bootstrap overhead. NOT for: conversation history analysis, model selection, or cost tracking.

2 Updated yesterday
unhealthy-outlander317
AI & Automation Listed

doctor-plus

Runs Claude Code's built-in /doctor health check, then audits the workspace against Anthropic's 6 then-and-now context-engineering shifts (rules��judgement, examples→interfaces, progressive disclosure, one-home instructions, auto-memory, rich references). Reports first, fixes only on approval. Use on /doctor-plus or "context checkup".

3 Updated 5 days ago
bravros
Data & Documents Solid

token-doctor

Personal diagnosis of where your Claude Code + Cowork spend goes. Reads local transcripts, prints your conversation length distribution, marathon share, cache rebuild costs, and per-project diagnosis (good projects and problem projects) right in the terminal. Then offers a deeper dive that fans out parallel Haiku subagents over your most expensive (and most efficient) sessions and writes a tight Markdown report. Use when the user asks "why is my Claude spend so high", "where am I burning tokens", "diagnose my Claude habits", "audit my Claude usage", or asks for a personal token-cost diagnosis.

106 Updated 4 days ago
techwolf-ai