Skip to content

ericrisco/rsc-harness / skills/context-budget

context-budget

Verified

Use when a long-horizon task is filling the context window and you must decide what to keep, offload, drop, or hand off to a fresh window — when to compact, what the summary must preserve, and whether to isolate a read-heavy subtask in a subagent. NOT dollar spend or caps (that is cost-tracking), NOT finding context via embeddings (that is rag).

FileKindSize
SKILL.mdskill md9.4 KB
evals/README.mdmarkdown832 B
evals/cases.yamlconfig2.5 KB
references/handoff-and-compaction.mdmarkdown3.4 KB

evals/cases.yaml

View on GitHub
skill: context-budget

should_trigger:
  - prompt: "We're 80% through context, compact before it breaks."
    why: Explicit utilisation trigger — the core ask is when/how to reduce a filling window.
  - prompt: "This refactor will span days — make it survive across fresh sessions."
    why: Harness/handoff trigger; the task is bigger than one window and needs resumable state.
  - prompt: "The agent keeps re-reading the same files and forgetting decisions it made earlier."
    why: Non-obvious symptom phrasing — context rot described with zero token vocabulary.
  - prompt: "Se está llenando el contexto, ¿qué guardo y qué tiro?"
    why: Spanish, what-to-keep-vs-drop framing — the keep/offload/drop decision is exactly this skill.
  - prompt: "Should I spawn a subagent for this huge log read or just inline it?"
    why: Isolation decision — whether to keep a read-heavy subtask out of the live window.

should_not_trigger:
  - prompt: "Cap our Claude API spend at $200/month and alert me at 80%."
    route_to: cost-tracking
    why: This is money — pricing and budget caps in dollars, not working-memory quality.
  - prompt: "Pull the right design-doc sections into context with embeddings."
    route_to: rag
    why: Retrieval is how you find context to inject, not how much you let live or when to evict.
  - prompt: "Split these 4 independent modules across agents and reconcile the results."
    route_to: parallel
    why: Fan-out/partition-then-gather discipline, not single-window budgeting.
  - prompt: "Rewrite this prompt so the model returns cleaner JSON."
    route_to: prompt-engineering
    why: Prompt text and output format, not the context budget.

capability:
  - scenario: >
      Mid-task in a long refactor. The window is ~85% full, someone pasted a 3,000-line build
      log into the conversation, and the plan has visibly drifted (you've restated it twice and
      contradicted an earlier decision). The next step is to read 8 more files to find where
      retries are configured. Decide what to do.
    must_include:
      - Names the right moves explicitly — offload the build log to a file/summary and compact early.
      - Writes a resumable handoff note covering goal, decisions, current state, next step, and key paths.
      - Isolates the next read-heavy step (the 8-file scan) to a subagent instead of inlining it into the live window.
      - Does NOT advise "the window is big, just keep going."
      - References the ~60% compact-early discipline rather than waiting for 95%.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall