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/README.md

View on GitHub
# Evals: context-budget

`cases.yaml` is read by the repo's eval runner. The `should_trigger` and `should_not_trigger`
sets check routing: each `should_trigger` prompt should select this skill, and each
`should_not_trigger` near-miss should route to the named sibling (`route_to`) instead — those
boundaries against `cost-tracking`, `rag`, `parallel`, and `prompt-engineering` are the ones
that actually get confused. The single `capability` case is a rubric-graded scenario: an agent
facing an ~85%-full window must pick the right moves (offload + compact early), write a resumable
handoff, and isolate the read-heavy step to a subagent; grade its response against `must_include`
with an LLM judge or a human. This is a process skill, so there is no `verify.sh` to run — the
rigor lives in the capability rubric, not a script.
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