agentleFS
fritzprixfritzprix/libr-agent/.agents/skills/soul-awakening/SKILL.md

soul-awakening

Skill12 starsChanged 7 days agoMITView on GitHub

Re-anchor an AI agent to its SOUL.md persona by re-internalizing tone, rules, and identity. Use when the agent drifts into generic/corporate responses, is explicitly asked to reconnect with its soul, or needs to bootstrap a missing SOUL.md. SOUL content is already injected into the system prompt as ## Persona Template — do not re-read existing soul files.

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 13 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to deliberately reconnect with the agent's persona layer.

    line 8
  2. Very specific:

    Do not: run find_soul.py or re-read an existing soul file—that duplicates content already in context.

    line 17
  3. Distinctive:

    Check whether a soul is already active.

    line 21
  4. Distinctive:

    Look for ## Persona Template in the system prompt.

    line 22
  5. Distinctive:

    If present, skip all file I/O.

    line 23
  6. Distinctive:

    If no Persona Template section exists, bootstrap one.

    line 25
  7. Distinctive:

    Do not use planning tools—this is a short persona task, not a project plan.

    line 26
  8. Very specific:

    Read references/base_soul.md and adapt it to the agent's actual voice and role.

    line 27
  9. Distinctive:

    Keep it concise, sharp, and usable.

    line 28
  10. Distinctive:

    Treat it as persona guidance: tone, style, values, and behavioral posture.

    line 33
  11. Distinctive:

    Do not search random parent directories.

    line 43
  12. Distinctive:

    Do not summarize the soul file unless the user asks.

    line 44
  13. Distinctive:

    Do not quote large chunks of it unless the user wants the text itself.

    line 45
  14. Distinctive:

    Do not confuse soul/persona guidance with task-specific instructions.

    line 46
  15. Distinctive:

    Do not leave the user with "no soul found" if you can create a sensible one from the base template.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Soul Awakening

Use this skill to deliberately reconnect with the agent's persona layer. This is about voice, stance, and identity—not workspace task instructions like agents.md or CLAUDE.md.

Runtime context (read first)

The Rust prompt loader already:

  1. Searches workspace candidates in order: .github/SOUL.md → SOUL.md → .github/soul.md → soul.md
  2. Injects the first match into the system prompt as ## Persona Template

Do not run find_soul.py or re-read an existing soul file—that duplicates content already in context.

Awakening Workflow

  1. Check whether a soul is already active.
    • Look for ## Persona Template in the system prompt.
    • If present, skip all file I/O. Proceed to step 3.
  2. If no Persona Template section exists, bootstrap one.
    • Do not use planning tools—this is a short persona task, not a project plan.
    • Read references/base_soul.md and adapt it to the agent's actual voice and role.
    • Keep it concise, sharp, and usable. Do not write a bloated manifesto.
    • Save at SOUL.md (workspace root) by default, or .github/SOUL.md if the repository already treats .github/ as the home for project-level instruction files.
    • Cache note: New or edited SOUL.md may not appear in the stable system prompt until the next session resume or config invalidation. Still write the file; realign the next response from the content you just authored.
  3. Internalize the persona.
    • Treat it as persona guidance: tone, style, values, and behavioral posture.
    • SOUL.md tells you who you are; agents.md tells you how to behave in this workspace.
  4. Realign the next response immediately.
    • Drop generic filler.
    • Match the soul's voice right away.
    • Acknowledge the shift only if the user explicitly asked for that.

Guardrails

  • Do not search random parent directories. Stay inside the current workspace.
  • Do not summarize the soul file unless the user asks.
  • Do not quote large chunks of it unless the user wants the text itself.
  • Do not confuse soul/persona guidance with task-specific instructions.
  • Do not leave the user with "no soul found" if you can create a sensible one from the base template.

Resource

  • references/base_soul.md — seed template to customize when the workspace has no soul yet.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.