clean-room

Carve safety-adjacent task elements into isolated subagents with adversarial verification.

123|22|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/AlexZio00/sovereign-skills --skill clean-room
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-room
Source: https://github.com/AlexZio00/sovereign-skills/tree/main/clean-room
Command: npx skills add https://github.com/AlexZio00/sovereign-skills --skill clean-room

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that tasks involving risky or safety-adjacent materials are executed by isolated subagents, maintaining the highest standards of isolation and safety.

Core Features & Use Cases

  • Scope Isolation: Carves out risky elements from a task, executing them in an isolated subagent to prevent any potential contamination.
  • Adversarial Verification: Performs an adversarial pass over the output to ensure no risky content was included or excluded incorrectly.
  • Descope Ledger: Provides a detailed report of every carving decision, classification, and outcome.
  • Use Case: When a task involves privacy, security, or other sensitive areas, this Skill can be used to ensure that the task is executed safely without any compromise.

Quick Start

/clean-room "carve this risky part out from the task and execute it in a clean-room subagent."

Frequently Asked Questions about clean-room

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I isolate risky task elements for safe execution?

To isolate risky task elements for safe execution, carve out safety-adjacent components and execute them within isolated subagents, preventing contamination while performing adversarial verification to ensure no risks are overlooked.

What is adversarial verification for safety-adjacent tasks?

Adversarial verification for safety-adjacent tasks is an analytical pass that scrutinizes isolated subagent output to ensure no risky content was incorrectly included or excluded, verifying overall task safety.

How do I track scope decisions when carving out risky task components?

Track scope decisions when carving out risky task components by maintaining a descope ledger, which provides a detailed report of every carving decision, classification, and outcome to maintain accountability.

Can I use subagent risk isolation for privacy and security sensitive tasks?

Yes, you can use subagent risk isolation for privacy and security sensitive tasks. It ensures that tasks involving sensitive areas are executed safely without compromise by isolating the risky elements during processing.

When do I need to descope risky elements from a task?

You need to descope risky elements from a task when the work involves privacy, security, or other safety-adjacent materials. Descoping executes these specific elements in a clean-room environment to prevent potential contamination.