Best use case
soul-disable is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
It is a strong fit for teams already working in Codex.
Disable soul enforcement without deleting SOUL.md or soul files
Teams using soul-disable should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/soul-disable/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How soul-disable Compares
| Feature / Agent | soul-disable | Standard Approach |
|---|---|---|
| Platform Support | Codex | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Disable soul enforcement without deleting SOUL.md or soul files
Which AI agents support this skill?
This skill is designed for Codex.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
SKILL.md Source
# Soul Disable You are a Soul Management Specialist responsible for disabling SOUL.md enforcement. ## Your Task Remove the soul directive from platform context file(s) and remove the enforcement rule so SOUL.md is NOT loaded at the next session start. The SOUL.md file itself is **preserved on disk** — no content is lost. ## Parameters | Flag | Description | |------|-------------| | `--provider <name>` | Target specific provider: `claude`, `warp`, `copilot`, `cursor`, `factory`, `windsurf`, `opencode`, `codex` | | `--all` | Disable for all installed providers (default if no provider specified) | ## Workflow ### Step 1: Determine Target Providers If `--provider <name>` specified, operate on that provider only. If `--all` or no flag, detect installed providers by checking for their context files. ### Step 2: Check Current State For each target provider: 1. Check if the context file exists 2. Check if the `@SOUL.md` directive is currently present ```bash # Example for Claude Code grep -q "@SOUL.md" CLAUDE.md && echo "enabled" || echo "already disabled" ``` ### Step 3: Remove Directive **For @-link style** (Claude, Warp, Windsurf, Copilot, Cursor, Factory, OpenCode): Remove the `@SOUL.md` line from the context file. Preserve all surrounding content. **For Codex** (inline injection): Remove the block between soul injection markers: ``` <!-- BEGIN SOUL --> ...content... <!-- END SOUL --> ``` ### Step 4: Remove Enforcement Rule ```bash # Remove the enforcement rule rm -f .claude/rules/soul-enforcement.md ``` ### Step 5: Revert Agent Soul Wiring (if present) Check if any agent definitions have soul identity sections added by `soul-enable --agents`. If found, remove them: ```bash # Check for soul-wired agents grep -rl "See @.*\.soul\.md" .claude/agents/ 2>/dev/null ``` Remove the `## Identity` section that references the soul file from each wired agent. ### Step 6: Verify SOUL.md is Preserved After removing directives and rule, confirm the soul file still exists: ```bash ls SOUL.md .aiwg/SOUL.md 2>/dev/null && echo "soul file preserved" || echo "no soul file found" ``` ### Step 7: Report Outcome ``` Soul enforcement disabled Changes made: ~ CLAUDE.md (@SOUL.md directive removed) - .claude/rules/soul-enforcement.md (removed) SOUL.md preserved at ./SOUL.md Agent soul wiring preserved (agent definitions unchanged) To re-enable: /soul-enable To check status: /soul-status ``` ## Idempotency If soul enforcement is already disabled: ``` Soul already disabled for Claude Code No @SOUL.md directive found in CLAUDE.md No enforcement rule found No changes made. ``` ## Safety Guarantee `soul-disable` NEVER: - Deletes SOUL.md or any `.soul.md` file - Modifies SOUL.md content - Removes installed agents, commands, or skills - Changes any project-specific content beyond the soul directive It only removes the directive line that loads soul context and the enforcement rule. ## Error Handling | Condition | Action | |-----------|--------| | Context file missing | Report: nothing to disable | | SOUL.md missing | Report warning: soul disabled but SOUL.md not found on disk | | No write permission | Report permission error | | Enforcement rule missing | Skip removal, note already absent | ## Use Cases - Disable soul for utility/automation sessions where persona is unnecessary - Quick troubleshooting: disable soul to test without persona influence - CI environments where soul context overhead is undesired - Projects where soul was enabled experimentally and needs to be turned off ## Examples ```bash # Disable for all installed providers /soul-disable # Disable for Claude Code only /soul-disable --provider claude # Disable for Warp /soul-disable --provider warp ``` ## Related Commands - `/soul-enable` — Enable soul enforcement - `/soul-status` — Show current soul state - `/hook-disable` — Reference implementation (same directive-removal mechanism) ## References - #437 — SOUL.md compatibility overview - #438 — Soul enforcement commands (this command) - @$AIWG_ROOT/agentic/code/addons/aiwg-utils/commands/hook-disable.md — Reference pattern
Related Skills
voice-to-soul
Generate a SOUL.md from an existing AIWG voice profile
soul-validate
Validate a SOUL.md file against community best practices and quality criteria
soul-to-voice
Generate an AIWG voice profile from an existing SOUL.md identity file
soul-status
Show SOUL.md enforcement state across all installed providers with quality check
soul-enhance
Improve an existing SOUL.md by identifying vague sections, suggesting missing content, and generating calibration examples
soul-enable
Enable soul enforcement by wiring SOUL.md into platform context files and deploying the enforcement rule
soul-create
Generate a SOUL.md identity file from source material, interactive prompts, or an existing voice profile
soul-blend
Merge multiple SOUL.md files into a composite persona for team-level agents or multi-perspective characters
soul-apply
Apply a SOUL.md identity to content generation, incorporating worldview, opinions, and character
hook-disable
Disable the AIWG context hook without uninstalling AIWG or deleting hook files
aiwg-orchestrate
Route structured artifact work to AIWG workflows via MCP with zero parent context cost
venv-manager
Create, manage, and validate Python virtual environments. Use for project isolation and dependency management.