Skip to content

ericrisco/rsc-harness / skills/continuous-learning

continuous-learning

Verified

Use when a mistake, correction, or surprise taught the workspace something that must stick — a retro or postmortem, the same agent error corrected twice, a resolved bug's root cause, scattered notes-to-self — and route that lesson to the durable surface that fires next time. NOT a forward choice with alternatives (that is `decision-records`).

FileKindSize
SKILL.mdskill md9.6 KB
evals/README.mdmarkdown1.0 KB
evals/cases.yamlconfig3.3 KB
references/lesson-routing.mdmarkdown5.0 KB

evals/README.md

View on GitHub
# Evals — continuous-learning

These cases are eyeballed against the SKILL.md description and body, not run by a
harness. Two axes. **Triggering:** read each `should_trigger` prompt and confirm
the description's "Use when …" / "Triggers:" clauses would route it here, and
read each `should_not_trigger` prompt and confirm it routes to its `route_to`
sibling instead (the `NOT … (that is decision-records)` boundary plus the
when-NOT list should make every one of those a clean miss). **Capability:** walk
the scenario through the body and check every `must_include` rubric item is
satisfied — the blameless root cause, the 2+-recurrences structural fix, the
routing to an exact durable path, the hand-off to `author-skill` for craft, the
situation-tagged entry, and the "prove it fires next time" surface.

There is no `scripts/verify.sh`: this is a process skill whose only output is a
durable write into *another* surface, which is checked there (a rule, an eval, a
verify.sh on the owning skill). Its rigor is the capability eval above.
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: 471kUpdated 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