| name | recovery |
| description | Use Recovery when the system, team, or process has lost capacity — degraded performance, accumulated errors, technical debt fatigue — and needs direct restorative attention before it can operate effectively. |
| version | 0.1.0 |
| author | mmbnchips |
| license | CC0-1.0 |
| compatibility | Hermes Agent skills system |
| metadata | {"hermes":{"tags":["shipping-now","literal","defense-and-recovery","defense","recovery","stabilization","survivability"],"homepage":"https://github.com/Hmbown/mmbnchips"}} |
Recovery
Restore operating capacity so the system can fight again.
What This Skill Does
Use Recovery when the system, team, or process has lost capacity — degraded performance, accumulated errors, technical debt fatigue — and needs direct restorative attention before it can operate effectively.
In this chip pack, Recovery is treated as a literal battle-chip procedure with a shipping-now delivery profile.
Canonical reference input: Recovery.
Hermes shelf: Defense and Recovery.
When To Use
- A system or team is running at reduced capacity and needs to regain working strength.
- Accumulated damage (technical debt, error backlog, degraded metrics) is the bottleneck, not broken infrastructure.
- The next move requires full operating capacity that you currently do not have.
Prerequisites
- Confirm the active Hermes session has the real tools, permissions, and target access needed for a live chip effect.
- These procedures rely on the normal tools already present in the active Hermes runtime; this repo does not ship a separate integration layer.
Procedure
- Restate the target, success condition, and no-touch boundaries before you spend the chip.
- Assess what capacity has been lost and what restoration would look like.
- Apply the lightest effective restorative action — pay down debt, clear the backlog, restore the baseline.
- Confirm capacity has returned to a usable level before resuming normal tempo.
- Stop for explicit confirmation before taking a live action that changes real state outside the current conversation.
- Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.
Deliverables
- A restorative action that returns a system, process, or team to functional operating capacity.
- A short note on what was recovered and what the new baseline looks like.
Pitfalls / Guardrails
- Treat the live action surface as real operational work, not just battle-chip flavor text.
- Recovery restores capacity; it does not fix what broke it. If the damage source is still active, triage that separately.
- Do not mistake repeated Recovery for a sustainable strategy. If you are healing constantly, something upstream still needs Repair.
- Recovery is not free — every heal costs a turn. Use it when the restoration is worth the tempo loss.
- Keep the chip metaphor anchored to a real operating move; do not let flavor substitute for procedure.
Verification
- Check that the response includes every promised deliverable and leaves an inspectable audit trail.
- Check that confirmed facts, assumptions, and proposed follow-up are visibly separated.
- Check that the exact live target, confirmation gate, and rollback or recovery path are explicit.
Example Invocation
/recovery restore lost operating capacity — pay down the debt, clear the backlog, or rebuild the baseline — so the system can operate at full strength again
