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.
Refocusing
Invoke the skill as refocusing, its frontmatter name. OpenRig seeds it in the
Claude and Codex global skill roots and includes selected plugin skills in managed
loadouts. Existing externally managed copies remain authoritative. If the harness
has not discovered it yet, read this installed skill file and run its script directly;
hook registration alone does not prove native skill discovery.
Refocus preserves a long session's earned expertise while re-grounding it in current intent and lived context. It is not a restart, wake, or phase checkpoint.
During an actionable managed restore, consume the current topology and work trace that actually arrived with the request. Do not rerun Python merely to duplicate it. If no current trace arrived, name that delivery gap. A packet pointer, compact summary or truncated extract is not a full source read. Use the native file-read tool for required notes and full sources, and complete the existing restore audit; partial file reads do not establish completed refocus or restoration.
For a new trace outside that delivered context, follow the command guidance below.
Resolve the bundled script's absolute path from the directory of this loaded skill.
Stay in your current working directory; do not cd into the skill directory, which
can change the inferred work node. Run the trace as one plain command, replacing
the example path with the actual absolute path written out in the tool call:
python3 "/absolute/path/to/refocusing/scripts/trace-to-root.py" --trees both --depth light
Do not combine this command with shell variables, environment assignments, command substitution, exit-status printing or file-reading loops. Read the named source files separately with the native read tool. Combined shell loops or variables can require native approval even when the intended operations are read-only; a plain command is not a guarantee that approval will never be needed.
For managed compaction, refocus during the restore request or its read-depth audit. The earlier acknowledgement-only boundary is not permission to restore.
Use --trees topology|work|both to select context domains and --depth light|full to control how
much each node contributes. Light work traces compose intent: and name notes; full traces include
the complete node and notes bodies. The script resolves topology.root and workspace.root with
rig config get. When a known current node must be supplied, pass --work-start or
--topology-start with its literal absolute path in the same plain command. Do not
substitute the project root for a mission or slice node and claim that mission was traced.
A catalogued project's root can sit outside workspace.root. The refocus hook passes the daemon's
catalogued project roots as --work-root, and the work trace ascends to the deepest known root that
contains the node. Run by hand, pass the project root with --work-root (repeatable) or
OPENRIG_REFOCUS_WORK_ROOT. Don't point OPENRIG_WORKSPACE_ROOT at the project instead: the CLI reads
that variable as workspace.root too.
The trace walks the topology and work trees. For the project's own declared context (intent, context files,
skills), rig context work-install lists it; read what the next action needs.
Read references/refocus.md when changing the automatic hook or its content ladder. A missing chain file is evidence: report the gap and continue; never follow pointers to invent a second parent.
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 |