safe-self-mod

Validate core file changes in an isolated Clone-01 before applying them.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/zkksdk/skills --skill safe-self-mod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: safe-self-mod
Source: https://github.com/zkksdk/skills/tree/main/skills/safe-self-mod
Command: npx skills add https://github.com/zkksdk/skills --skill safe-self-mod

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow ensures that changes affecting the main instance (core files under /workspace, including SOUL.md, IDENTITY.md, AGENTS.md, TOOLS.md, MEMORY.md, and configuration or skill files such as openclaw.json and skills/*) are validated in an isolated Clone-01 environment before applying to the main workspace.

Core Features & Use Cases

  • Recognizes write operations that touch core identity/behavior files, configuration, or skill updates.
  • Performs isolated verification using a prepared Clone-01 session to validate changes without impacting the live workspace.
  • Analyzes verification outcomes and reports PASS with risk assessment or FAIL with issues, enabling user consent prior to modification.
  • Requires explicit user confirmation before applying any changes to the main instance.

Quick Start

Initiate a safe-mod workflow by validating a proposed change in Clone-01 and report the verification result.

Frequently Asked Questions about safe-self-mod

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

FAQPage Schema
How do I safely validate self-modifications to core identity files before applying changes?

To safely validate self-modifications, changes to core identity files are first tested in an isolated Clone-01 environment. This workflow automates risk checks and requires explicit user consent before applying any validated modifications to the main workspace.

What is an isolated verification workflow for self-modification?

An isolated verification workflow for self-modification is a three-stage process: detecting relevant file changes, validating them in a Clone-01 session, and applying them only after user confirmation. It prevents unverified changes from impacting the live workspace.

How do I automate change management for core configuration and skill files?

You can automate change management for configuration and skill files by triggering a safe-mod workflow that recognizes write operations. It performs isolated verification and reports PASS or FAIL outcomes, ensuring user consent prior to modification.

Does the self-modification safety workflow require user confirmation before applying changes?

Yes, the self-modification safety workflow requires explicit user confirmation before applying changes. It analyzes verification outcomes from the Clone-01 session and reports a PASS with risk assessment or FAIL with issues, enabling informed consent.

Can I use this isolated verification process for updates to openclaw.json and skills directories?

Yes, you can use this isolated verification process for updates to openclaw.json and skills directories. The workflow recognizes write operations that touch configuration or skill files and validates them in Clone-01 before applying changes.

What happens if a verification task fails during the self-modification workflow?

If a verification task fails during the self-modification workflow, the system reports a FAIL outcome with specific issues. Changes are blocked from applying to the main workspace until the issues are resolved and a subsequent verification passes.