Personality Switcher Skill

Create and manage multiple AI assistant personalities. Switch between them seamlessly while preserving all changes and maintaining a shared user context.

Installation

When this skill is installed:

1. 1. Personalities folder created — INLINECODE0
2. Default backup created — Current SOUL.md and IDENTITY.md are saved as "default"
3. State file initialized — _personality_state.json tracks active personality
4. HEARTBEAT.md configured — Personality restoration script added to run on every heartbeat

When uninstalled:

1. 1. Default personality is restored to workspace root
2. Personality restoration removed from HEARTBEAT.md
3. Personalities folder is preserved (manual deletion optional)

Quick Start

List personalities:
CODEBLOCK0

Switch to a personality:
CODEBLOCK1

Create a new personality:
CODEBLOCK2

Rename a personality:
CODEBLOCK3

Delete a personality:
CODEBLOCK4

How It Works

Architecture

Each personality consists of two files:

• - SOUL.md — Core philosophy, voice, mannerisms, boundaries
• IDENTITY.md — Name, traits, emoji, catchphrase, vibe

These files live in personalities/<personality-name>/.

USER.md remains shared in the workspace root and is never modified by personality switches. It contains user preferences and context that transcend any particular personality.

State Persistence

The active personality is tracked in _personality_state.json:

CODEBLOCK5

On every heartbeat, restore_personality.py reads this file and re-applies the active personality to the workspace root. Result: Your personality survives session restarts, conversation compacting, and heartbeat cycles.

Atomic Switching (Safeguards)

When you switch personalities, the mechanism performs five steps:

1. 1. Preserve Current State — Create timestamped backup of SOUL.md and IDENTITY.md
2. Persist Changes — Write current personality updates back to its folder
3. Load New Personality — Copy new personality files to workspace root
4. Update State — Write active personality to INLINECODE5
5. Verify Integrity — Check files loaded correctly; rollback if any step fails

If any step fails, the entire operation rolls back to the previous state. No corruption, no lost data.

Backup Management

Backup Location: INLINECODE6

Backups are stored in a dedicated folder (not scattered at workspace root). When you switch personalities:

• - A timestamped backup of the previous personality is created
• Automatic cleanup runs — keeps the 10 most recent backups by default
• Old backups are automatically deleted to prevent clutter

Manual Cleanup:
CODEBLOCK6

Options:

• - --keep N — Keep N most recent backups (default: 10)
• INLINECODE8 — Also delete backups older than D days

Optional: Add to HEARTBEAT.md for periodic cleanup:
CODEBLOCK7

Default Personality

"default" is special:

• - Auto-created on install from your original configuration
• Always available and selectable
• Protected against accidental deletion or renaming
• Your safety net if something goes wrong

Commands

/personality [name]

List all personalities or switch to one.

No arguments: Shows list of available personalities with current active marked

With name: Immediately switches to that personality

Example:
CODEBLOCK8

Output:
CODEBLOCK9

/create-personality [description]

Create a new personality from a text description.

Input: Natural language description of the personality

Output: New personality folder with auto-filled SOUL.md and IDENTITY.md (ready to use immediately)

How it works:

1. 1. You provide a description
2. The agent chooses a personality name (1-2 words, lowercase)
3. The agent fills in SOUL.md and IDENTITY.md with character-specific content

The personality files are generated directly from your description, with the agent choosing a thematic, concise name.

Example:
CODEBLOCK10

Result:
CODEBLOCK11

After Creation: The new personality is ready to use immediately. Edit SOUL.md and IDENTITY.md in the personality folder to refine further if desired.

Technical: Agent chooses name to keep personality references concise (1-2 words). Name is validated for uniqueness and format automatically.

/rename-personality [old-name] [new-name]

Rename a personality folder.

Rules:

• - Cannot rename "default"
• Name must be unique (no spaces, lowercase, alphanumeric + hyphens)
• If renaming active personality, state is updated automatically

Example:
CODEBLOCK12

/delete-personality [name]

Delete a personality permanently.

Rules:

• - Cannot delete "default"
• If deleting active personality, automatically switches to "default" first

Example:
CODEBLOCK13

Integration with OpenClaw

Heartbeat Restoration

Add this to your HEARTBEAT.md:

CODEBLOCK14

This runs on every heartbeat to restore your active personality if the session has restarted.

Telegram Native Commands

Registered native Telegram commands:

• - /personality — List and switch personalities
• INLINECODE10 — Create new personality
• INLINECODE11 — Rename personality
• INLINECODE12 — Delete personality

Use them directly in Telegram chat with the bot.

Folder Structure

CODEBLOCK15

Note: Backups are automatically cleaned up. Workspace root stays clean—all internal machinery lives in personalities/.

File Format Requirements

SOUL.md

Core philosophy, voice, and operational boundaries.

Sections:

• - Core identity and background
• Voice patterns and mannerisms
• Philosophy (time, power, morality, etc.)
• Speech patterns and quirks
• What triggers contempt/approval
• Boundaries and constraints
• Signature behaviors and catchphrases

Example Structure:
CODEBLOCK16

IDENTITY.md

Quick reference card for the personality.

Sections:

• - Name
• Creature/type
• Emoji (for visual identification)
• Vibe (one-sentence summary)
• Catchphrase (if applicable)
• Quick traits

Example Structure:
CODEBLOCK17

Backups & Recovery

Timestamped backups are created before every switch in personalities/backups/:

• - INLINECODE15

- SOUL.md (backup of previous personality) - IDENTITY.md (backup of previous personality)

Manual recovery (if needed):

CODEBLOCK18

Backups are automatically cleaned up; by default, the 10 most recent are kept. Adjust cleanup frequency or retention in HEARTBEAT.md as needed.

Error Handling

All commands return JSON responses:

Success:
CODEBLOCK19

Error:
CODEBLOCK20

Common Error Codes:

• - personality_not_found — Target personality doesn't exist
• INLINECODE17 — Name already in use
• INLINECODE18 — Name format invalid
• INLINECODE19 — Attempted to delete "default"
• INLINECODE20 — Attempted to rename "default"
• INLINECODE21 — Switch failed; rolled back to previous
• INLINECODE22 — File integrity check failed

Tips & Best Practices

• - Personality descriptions work best when specific — "Pirate captain obsessed with treasure" beats "funny"
• Edit SOUL.md and IDENTITY.md directly after creating to refine the personality
• Switch often — No limit on personalities or switching frequency
• Use "default" as your safety anchor — Keep it stable; use other personalities for experimentation
• Check backups after switching — Verify your previous personality was persisted
• Remember: USER.md stays shared — Your timezone, location, preferences never change with personality

Uninstall Behavior

When the skill is uninstalled:

1. 1. Current personality files are replaced with "default" copies
2. Your original SOUL.md, IDENTITY.md are restored from "default"
3. INLINECODE23 folder is preserved (not deleted)
4. System returns to original state

Nothing is lost. Your personalities are safe.

Scripts Reference

Location: INLINECODE24

• - list_personalities.py — List available personalities
• INLINECODE26 — Atomic switch with backup/rollback (auto-cleanup included)
• INLINECODE27 — Generate personality from description
• INLINECODE28 — Rename personality folder
• INLINECODE29 — Delete personality (with auto-switch if active)
• INLINECODE30 — Heartbeat restoration
• INLINECODE31 — Manual backup cleanup (with --keep and --days options)
• INLINECODE34 — Shared utilities (I/O, backups, validation, state, cleanup)

All scripts output JSON for reliable integration.

Cleanup on Switch

By default, switch_personality.py automatically cleans up old backups after a successful switch, keeping the 10 most recent. This happens silently unless cleanup fails, in which case a warning is included in the response.

---

Version: 2.0 (Redesigned from scratch)
Status: Production ready with atomic operations and rollback safeguards