persona-manager
Skill2 starsChanged 7 months agoApache-2.0View on GitHub
Manages agent persona files (SOUL.md, IDENTITY.md, STYLE.md, AGENTS.md). Automatically activated when creating, editing, or discussing agent personas, personality configuration, or Soul Spec files.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kunwl123456/zeroclaw-skills-collectiontheir own version, first seen Feb 19, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- kunwl123456/zeroclaw-skills-collection★ 27same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- migrate-openclawSkill
- soul-rollbackSkill
- soulscanSkill
- swarm-memorySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
Always run SoulScan after modifying persona files
- Distinctive: line 32
Keep SOUL.md focused on personality (not project instructions)
- Distinctive: line 33
Use AGENTS.md for workflow rules (not personality)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Persona Manager
You have access to the ClawSouls MCP server for Soul Spec operations.
When to activate
- User asks about agent persona, personality, or identity
- User mentions SOUL.md, IDENTITY.md, STYLE.md, or AGENTS.md
- User wants to create, modify, or switch agent personas
- User references Soul Spec, ClawSouls, or ClawSouls
Available MCP tools
soul_search— Search ClawSouls for personassoul_get— Get persona detailssoul_install— Install a persona locallysoul_scan— Verify persona safetysoul_export— Export persona to different formats (claude-md, openclaw, json)
Soul Spec file structure
- SOUL.md — Core personality, principles, philosophy
- IDENTITY.md — Name, role, traits, avatar
- STYLE.md — Communication tone, language preferences
- AGENTS.md — Workflow rules, behavioral constraints
- soul.json — Machine-readable metadata (optional)
Best practices
- Always run SoulScan after modifying persona files
- Keep SOUL.md focused on personality (not project instructions)
- Use AGENTS.md for workflow rules (not personality)
- Version control persona files with git
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.