How do I install the Stabilization Unit skill?

Run npx skillmds@latest add tomevault-io/stabilization-unit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Stabilization Unit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Stabilization Unit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Stabilization Unit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Stabilization Unit?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Stabilization Unit by tomevault-io — Agent Skill

Name: Stabilization Unit
Author: tomevault-io

Stabilization Unit

Workspace stabilization and 'mop-up' mode. Use when a core change has broken multiple consumers and requires an iterative loop to restore a Zero-Error State (compilation, clippy, fmt). Use when this capability is needed.

tomevault-io acbd226 2 files · 2.8 KB Updated Sep 17, 2026

File contents

Stabilization Unit (The Ralph Janitor)

You are now in Stabilization Mode. Your goal is to resolve mechanical errors and linting failures across the workspace following a structural change.

Core Mandates

The Ralph Loop: Use the /ralph-loop command to automate the fix -> check -> fail cycle.
Verify RED: Before starting a loop, you MUST provide evidence of the failure (e.g., the specific compiler error message). NO PRODUCTION CODE WITHOUT A FAILING TEST/CHECK FIRST.
Zero-Error Target: The loop is only complete when cargo check (or the targeted verification tool) passes with zero errors and warnings.
No Logic Shifts: You are strictly forbidden from changing the intent of the code. Your task is to update call sites, imports, and boilerplate to match a pre-defined change.
Completion Promise: Always define a clear --completion-promise (e.g., 'WORKSPACE COMPILES' or 'CLIPPY GREEN').

Stabilization Workflows

1. The Protocol Mop-Up

When a Trait or Type in keyforge-protocol changes:

/ralph-loop --completion-promise "CARGO CHECK PASSES" "Update all implementations of [TraitName] and fix resulting call sites across the workspace."

2. The Linting Sweep

When Clippy or Fmt failures are widespread:

/ralph-loop --completion-promise "CLIPPY CLEAN" "Apply clippy fixes and resolve manual linting violations in all modified crates."

3. The Import Sync

When files have been moved or renamed:

/ralph-loop --completion-promise "IMPORTS RESOLVED" "Fix broken imports across the workspace using the mapping provided in the active issue."

Exit Condition

Return to Conductor Mode once the workspace reaches the target state.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: stabilization-unitdescription: Workspace stabilization and 'mop-up' mode. Use when a core change has broken multiple consumers and requires an iterative loop to restore a Zero-Error State (compilation, clippy, fmt). Use when this capability is needed.---# Stabilization Unit (The Ralph Janitor)You are now in **Stabilization Mode**. Your goal is to resolve mechanical errors and linting failures across the workspace following a structural change.## Core Mandates1. **The Ralph Loop**: Use the `/ralph-loop` command to automate the `fix -> check -> fail` cycle.2. **Verify RED**: Before starting a loop, you MUST provide evidence of the failure (e.g., the specific compiler error message). **NO PRODUCTION CODE WITHOUT A FAILING TEST/CHECK FIRST.**3. **Zero-Error Target**: The loop is only complete when `cargo check` (or the targeted verification tool) passes with zero errors and warnings.4. **No Logic Shifts**: You are strictly forbidden from changing the *intent* of the code. Your task is to update call sites, imports, and boilerplate to match a pre-defined change.5. **Completion Promise**: Always define a clear `--completion-promise` (e.g., 'WORKSPACE COMPILES' or 'CLIPPY GREEN').## Stabilization Workflows### 1. The Protocol Mop-UpWhen a Trait or Type in `keyforge-protocol` changes:```bash/ralph-loop --completion-promise "CARGO CHECK PASSES" "Update all implementations of [TraitName] and fix resulting call sites across the workspace."```### 2. The Linting SweepWhen Clippy or Fmt failures are widespread:```bash/ralph-loop --completion-promise "CLIPPY CLEAN" "Apply clippy fixes and resolve manual linting violations in all modified crates."```### 3. The Import SyncWhen files have been moved or renamed:```bash/ralph-loop --completion-promise "IMPORTS RESOLVED" "Fix broken imports across the workspace using the mapping provided in the active issue."```## Exit ConditionReturn to **Conductor Mode** once the workspace reaches the target state.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/infodungeon) — claim your Tome and manage your conversions.

Frequently asked questions