mvschwarz/openrig / packages/daemon/assets/plugins/openrig-core/skills/refocusing
refocusing
VerifiedUse when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.8 KB |
| references/refocus.md | markdown | 1.1 KB |
| scripts/trace-to-root.pyexecutable | script | 30.0 KB |
references/refocus.md
View on GitHub# Refocus
1. What is the person actually trying to get? Not your current task — the outcome.
2. Does what you are doing RIGHT NOW move that? If you cannot say what a user gets, stop and say so.
3. What have you concluded without opening the file or running the thing?
Discomfort on any of these is the signal: drift feels like work.
The `refocusing` skill carries the source-appropriate path-only trace. Its
`scripts/trace-to-root.py` walks both current trees by default: topology `LEARNED.md`, then work
`SPEC.md` intent plus `NOTES.md`. Change breadth with `OPENRIG_REFOCUS_TREES=topology|work|both`
and read depth with `OPENRIG_REFOCUS_DEPTH=light|full`.
Replace this default without editing the plugin. The content ladder, highest precedence first, is:
1. `OPENRIG_REFOCUS_CONTENT_REF`, resolved by `rig context get`.
2. `OPENRIG_REFOCUS_CONTENT_FILE`, an operator-authored file.
3. `$OPENRIG_HOME/refocus/REFOCUS.md`, instance content.
4. This shipped default.
Fresh seats receive the separate onboarding assets `openrig-onboarding-01.md` and
`openrig-onboarding-02.md`. This file only cites those assets; it does not copy their world install.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 463k | Updated | Claude CodeCodex | Verified | Install |
| 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: 463k | Updated | Claude CodeCodex | Verified | Install |
| discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.). | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |