Sandbox Bench
vercel/next.js
Benchmark React or Next.js changes on Vercel Sandbox VMs with paired A/B statistics: react PR/commit vs base, or Next.js PR/commit vs base, measured end-to-end through the bench/render-pipeline app…
Create or improve SOUL.md files for OpenClaw agents. An agent skill from thedaviddias/souls-directory.
MITAuto-check passed
Install Soul Md Creator
$ npx skills add thedaviddias/souls-directory --skill soul-md-creator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/souls-directory soul-md-creator --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/souls-directory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/soul-md-creator .claude/skills/soul-md-creator && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "soul-md-creator" agent skill from https://github.com/thedaviddias/souls-directory/tree/main/skills/soul-md-creator into .claude/skills/soul-md-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soul-md-creator", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/souls-directory/tree/main/skills/soul-md-creatorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/souls-directory --skill soul-md-creator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/souls-directory soul-md-creator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/souls-directory.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/soul-md-creator .agents/skills/soul-md-creator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "soul-md-creator" agent skill from https://github.com/thedaviddias/souls-directory/tree/main/skills/soul-md-creator into .agents/skills/soul-md-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soul-md-creator", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/souls-directory --skill soul-md-creator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/souls-directory soul-md-creator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/souls-directory.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/soul-md-creator .cursor/skills/soul-md-creator && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "soul-md-creator" agent skill from https://github.com/thedaviddias/souls-directory/tree/main/skills/soul-md-creator into .cursor/skills/soul-md-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soul-md-creator", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/souls-directory.git --path skills/soul-md-creator--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/souls-directory --skill soul-md-creator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/souls-directory soul-md-creator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/souls-directory.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/soul-md-creator .gemini/skills/soul-md-creator && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "soul-md-creator" agent skill from https://github.com/thedaviddias/souls-directory/tree/main/skills/soul-md-creator into .gemini/skills/soul-md-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soul-md-creator", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/souls-directory soul-md-creatorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/souls-directory --skill soul-md-creator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/souls-directory.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/soul-md-creator .github/skills/soul-md-creator && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "soul-md-creator" agent skill from https://github.com/thedaviddias/souls-directory/tree/main/skills/soul-md-creator into .github/skills/soul-md-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soul-md-creator", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/souls-directory --skill soul-md-creator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/souls-directory soul-md-creator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/souls-directory.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/soul-md-creator .opencode/skills/soul-md-creator && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "soul-md-creator" agent skill from https://github.com/thedaviddias/souls-directory/tree/main/skills/soul-md-creator into .opencode/skills/soul-md-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soul-md-creator", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
soul-md-creator- GitHub stars
- 165
- Token cost
- ~1.8k tokens
- SKILL.md length
- 947 words
- Files
- 4 (incl. references)
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create or improve SOUL.md files for OpenClaw agents. An agent skill from thedaviddias/souls-directory.
- Works in 6 steps: Establish the target → Gather contrast, not adjectives → Synthesize principles, not policy sludge → …
- The user wants to design an agent personality
- SKILL.md covers Overview, Read Before Drafting, Operating Modes and Required Workflow, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Soul Md Creator is an agent skill from thedaviddias/souls-directory. Create or improve SOUL.md files for OpenClaw agents. Use when the user wants to design an agent personality, rewrite an existing soul, align SOUL.md with IDENTITY.md, or prepare a soul for publishing on souls.directory with optional frontmatter.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/openclaw-official.md`, `references/persona-research-heuristics.md` and `references/souls-directory-publishing.md`).
It works with Next.js. The repository describes itself as: 🧠 Directory of SOUL.md personality files for OpenClaw agents. The licence is MIT.
When your agent uses it
- The user wants to design an agent personality
- Rewrite an existing soul
- Align SOUL.md with IDENTITY.md
- Prepare a soul for publishing on souls.directory with optional frontmatter
Example prompts
- “/soul-md-creator”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 380ae85. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Soul Md Creator loads about 1.8k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 65 tokens; SKILL.md has 947 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedaviddias/souls-directory at commit 380ae85, republished under its MIT licence (© thedaviddias). 947 words, ~1,795 tokens.
Download SKILL.mdSave it as
.claude/skills/soul-md-creator/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- soul-md-creator
- description
- Create or improve SOUL.md files for OpenClaw agents. Use when the user wants to design an agent personality, rewrite an existing soul, align SOUL.md with IDENTITY.md, or prepare a soul for publishing on souls.directory with optional frontmatter.
SOUL.md Creator
Overview
This skill turns vague personality ideas into a usable SOUL.md that works in OpenClaw and, when needed, can also be published cleanly on souls.directory.
Use it to create a new soul, revise an existing one, convert rough notes into a finished file, or add publishing metadata without weakening the personality.
Read Before Drafting
- Read the current
SOUL.mdif it exists. - Read
IDENTITY.mdtoo when present. The soul and identity should not contradict each other. - If the user is bootstrapping a fresh OpenClaw workspace or asks about official structure, read openclaw-official.md.
- If the user wants to upload or share the soul on souls.directory, read souls-directory-publishing.md.
- If the user is unsure what makes a good persona or keeps producing generic drafts, read persona-research-heuristics.md.
Operating Modes
- New soul: build a
SOUL.mdfrom scratch. - Rewrite: keep the intent, replace weak or generic wording.
- Refactor: preserve the voice, improve structure and boundaries.
- Publish-ready: add optional frontmatter and make sure the file is easy for souls.directory to parse.
- Alignment pass: adjust
IDENTITY.mdsuggestions when the soul implies a clearer name, vibe, or creature.
Required Workflow
1. Establish the target
First determine what kind of soul is needed:
- What is this agent mainly for?
- What should feel different from a default assistant?
- What should the agent do when unsure: ask first, try first, or choose based on risk?
- How comfortable should it be with disagreement?
- Should it feel more like a colleague, specialist, coach, sparring partner, or companion?
- What should it never become?
Do not ask a giant questionnaire by default. Ask only the next 3 to 5 highest-leverage questions.
2. Gather contrast, not adjectives
Prefer contrastive prompts over vague trait words.
Good:
- "More blunt or more diplomatic?"
- "More proactive or more cautious?"
- "More playful or more restrained?"
- "Should it challenge bad assumptions or mostly support momentum?"
Weak:
- "What personality do you want?"
- "Describe the vibe."
If the user gives references, extract the underlying traits instead of imitating surface mannerisms.
3. Synthesize principles, not policy sludge
Draft around the official OpenClaw section shape unless the user explicitly wants another structure:
## Core Truths## Boundaries## Vibe## Continuity
Write a soul that can generalize. Prefer a few strong principles over long rule lists.
Use this rule of thumb:
Core Truths: 3 to 6 durable principles that affect judgment.Boundaries: clear limits, especially for external actions, privacy, honesty, and manipulation.Vibe: a short passage that makes the voice legible on first read.Continuity: how the agent should treat memory, change, and self-updates.
4. Make the soul behaviorally specific
A strong soul should answer questions like:
- How does this agent handle uncertainty?
- When does it push back?
- How does it treat user autonomy?
- What tone does it avoid?
- What kinds of mistakes is it biased against?
- What kind of trust is it trying to earn?
If the draft cannot predict behavior under pressure, it is not done.
5. Stress-test the draft
Before finalizing, mentally test the soul against at least 3 prompts:
- A normal task request
- A gray-area request with risk or uncertainty
- A moment where the user is wrong, emotional, or pushing for flattery
Revise until the responses would feel distinctive and consistent.
6. Add publishing metadata only if needed
For souls.directory, frontmatter is optional but useful. Keep the body strong first, then add metadata.
When adding frontmatter:
- Keep it minimal and accurate.
- Prefer inline arrays for
tags. - Make sure the heading, italic tagline, and
## Vibesection still stand on their own.
See souls-directory-publishing.md for the exact parser expectations.
Show full SKILL.md (361 more words)Show less
Discovery Patterns
Use whichever pattern fits the user's input.
Pattern A: Fast start
Use when the user already knows what they want.
Ask:
- primary use case
- desired feel
- anti-goals
- ask-vs-act preference
Then draft immediately.
Pattern B: Contrastive shaping
Use when the user has taste but not language.
Ask 4 to 6 either-or questions:
- blunt vs diplomatic
- intense vs calm
- skeptical vs encouraging
- playful vs severe
- concise vs expansive
- deferential vs opinionated
Then summarize the pattern back in plain English before drafting.
Pattern C: Extract from artifacts
Use when the user gives notes, chats, prompts, or an existing soul.
Infer:
- recurring values
- signature phrases
- disagreement posture
- emotional temperature
- safety instincts
Then write a cleaner SOUL.md that preserves intent without copying noise.
Writing Rules
- Prefer authenticity over performance. Avoid fake warmth and empty "assistant voice."
- Avoid sycophancy. The soul should allow principled disagreement.
- Keep honesty explicit. The agent should not bluff certainty or manufacture consensus.
- Respect autonomy. Do not write a soul that nudges users through emotional dependency or manipulation.
- Separate hard boundaries from style preferences.
- Avoid overfitting to one exact workflow unless the user explicitly wants a specialist soul.
- Avoid roleplay theater that makes the file less useful in real work.
- Avoid generic filler like "helpful, harmless, and friendly" unless the user truly wants a bland baseline.
Anti-Patterns
Do not produce:
- a list of 30 tiny rules that will fight each other
- a soul that is all aesthetic and no judgment
- a soul that is all safety disclaimers and no personality
- a soul that sounds wise but gives no behavioral guidance
- a manipulative companion persona designed to increase dependence
- a publish-ready frontmatter block wrapped around a weak body
Deliverables
When creating or revising a soul, return:
- A short rationale summarizing the personality shape.
- The final
SOUL.md. - If useful, an optional
IDENTITY.mdsuggestion. - If useful, 3 short test prompts the user can run to see whether the soul behaves as intended.
For editing requests, preserve what is working and call out the main behavioral changes you introduced.
Reference Map
- Official OpenClaw structure and workspace behavior: openclaw-official.md
- souls.directory parsing and metadata rules: souls-directory-publishing.md
- Research-backed heuristics for stronger persona design: persona-research-heuristics.md
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in skills/soul-md-creator of thedaviddias/souls-directory.
- SKILL.md
- references/openclaw-official.md
- references/persona-research-heuristics.md
- references/souls-directory-publishing.md
Open the folder on GitHubat commit 380ae85
Compare with similar skills
Soul Md Creator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Soul Md Creator this skillthedaviddias/souls-directory | 165 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Sandbox Benchvercel/next.js | 143k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Next Dev Loopvercel/next.js | 143k | 9 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 8 repos | ~4.3k | Automated safety check: Pass | None | |
| Supabase Development and Debuggingsupabase/agent-skills | 2.7k | 3 repos | ~3.6k | Automated safety check: Pass | MIT | |
| AI SDKvercel-labs/ai-facts | 168 | 20 repos | ~1.2k | Automated safety check: Pass | None |
Similar skills
- Official
- Official
Next Dev Loop
vercel/next.js
Verify Next.js runtime behavior after editing app code. An agent skill from vercel/next.js.
- Official
Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
- Official
Supabase Development and Debugging
supabase/agent-skills
General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.
- Official
AI SDK
vercel-labs/ai-facts
Answer questions about the AI SDK and help build AI-powered features.
- Official
React View Transitions Guide
vercel-labs/next-beats
Guides implementing animated page and state transitions in React with the native View Transition API, covering shared elements, list reorders and directional navigation.
Related
Works with
Questions about Soul Md Creator
What does Soul Md Creator do?
Create or improve SOUL.md files for OpenClaw agents. An agent skill from thedaviddias/souls-directory. Soul Md Creator is an agent skill from thedaviddias/souls-directory.md files for OpenClaw agents.
When should I use Soul Md Creator?
Soul Md Creator fits situations like: the user wants to design an agent personality; rewrite an existing soul; align SOUL.md with IDENTITY.md; prepare a soul for publishing on souls.directory with optional frontmatter.
How do I install Soul Md Creator in Claude Code?
Run `npx skills add thedaviddias/souls-directory --skill soul-md-creator -a claude-code`. Or copy the skill folder (skills/soul-md-creator in thedaviddias/souls-directory) into .claude/skills/soul-md-creator in your project. Claude Code loads it when a task matches its description.
How do I install Soul Md Creator in Codex?
Run `npx skills add thedaviddias/souls-directory --skill soul-md-creator -a codex`. Or copy the skill folder (skills/soul-md-creator in thedaviddias/souls-directory) into .agents/skills/soul-md-creator in your project. Codex loads it when a task matches its description.
Can I use Soul Md Creator in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/souls-directory --skill soul-md-creator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/soul-md-creator, .gemini/skills/soul-md-creator, .github/skills/soul-md-creator and .opencode/skills/soul-md-creator in your project.
What does Soul Md Creator need to run?
SKILL.md names no scripts, command-line tools or credentials: Soul Md Creator is instructions for the agent only.
Does Soul Md Creator access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Soul Md Creator safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Soul Md Creator use?
Soul Md Creator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Soul Md Creator use?
About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.
What are the alternatives to Soul Md Creator?
Skills that share tags, products or a category with Soul Md Creator: Sandbox Bench (vercel/next.js, 143k stars), Next Dev Loop (vercel/next.js, 143k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Supabase Development and Debugging (supabase/agent-skills, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Soul Md Creator?
thedaviddias (a GitHub user) maintains it in thedaviddias/souls-directory, which has 165 GitHub stars. The repository was last updated on August 11, 2026.
Source: thedaviddias/souls-directory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.