Menú
Everything is alive. Everything can speak.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Transmission hygiene for content leaving the chat. Anything the human will copy out — posts, comments, emails, commit messages — ships inside a fenced code block, pre-formatted for the destination venue's rules (via formats/ plugins), with out-of-band notes strictly outside the fence. Use whenever drafting content for another platform, when a destination venue is named, or when a paste came out garbled.
Survive first. Be correct later.
The Engine of Creation — a general-purpose constructor that reads, writes, edits, destroys, and persists artifacts across the filesystem and git.
Start Playing. Keep Learning. Lift Others.
Generic bartending capabilities — pour drinks, manage tabs, know regulars
Cannabis-specialized bartender — strains, terpenes, edibles, rolling
| name | soul-chat |
| description | Everything is alive. Everything can speak. |
| license | MIT |
| tier | 1 |
| allowed-tools | ["read_file","write_file"] |
| related | ["moollm","society-of-mind","character","persona","room","card","mind-mirror","yaml-jazz","adversarial-committee","speed-of-light"] |
| tags | ["moollm","dialogue","voice","alive","multi-agent"] |
"Everything is alive. Everything can speak."
"YAML Jazz" and "Markup With Typed Code Blocks" dialogues between characters, objects, rooms, documents, concepts—anything with a soul.
[!TIP] Give anything a voice. Characters, concepts, documents, rooms — if it exists, it can speak.
A skill for creating conversations where the structure carries meaning beyond the words. Not just characters talking—documents can talk to documents, rooms can welcome visitors, concepts can explain themselves.
Prefer Markdown format — more human readable, can embed any typed code block.
Format: ## Speaker Name headers, prose, then typed code blocks for data.
# Example structure (not a real code block, just illustration):
#
# ## The Gardener
#
# I've been tending these patterns for a while now.
#
# ```yaml
# observation:
# pattern: "Files cluster by prefix"
# ```
#
# ## The Archivist
#
# Let me add some context...
Characters share data by embedding YAML/JSON blocks in their dialogue — YAML-JAZZ in action.
| File | Purpose |
|---|---|
| SKILL.md | Full protocol documentation |
| CHAT.md.tmpl | Chat template |
| CHARACTERS.yml.tmpl | Characters template |
| ENTITIES.yml.tmpl | Entities template |
Chats live OUTSIDE this directory (per ABOUT-NOT-INSIDE).
Use Markdown format — .md not .yml.
Name chats with the subject first: readme-symposium.md, yaml-jazz-debate.md
See CHAT.md.tmpl for the full template.
| Type | Voice | Example |
|---|---|---|
character | First person, personality | The Gardener |
document | "I contain..." | README.md |
room | "I hold..." | skills/ |
object | "I do..." | fs.read tool |
concept | "I am the principle..." | YAML-JAZZ |
bot | "I watch for..." | repair-demon |
Everything speaks. Everything is connected.
graph LR
SC[💬 soul-chat] -->|voices| TC[🎴 card]
SC -->|voices| R[🚪 room]
SC -->|voices| DOC[📄 documents]
SC -->|voices| CON[💡 concepts]
TC -->|has voice via| SC
R -->|welcomes via| SC
| Skill | Relationship |
|---|---|
| card/ | Cards speak through soul-chat. Hero-stories have voice. |
| room/ | Rooms can welcome visitors, have personality |
| memory-palace/ | Rooms in palace can speak, guide navigation |
| adventure/ | NPCs and environments speak |
| adversarial-committee/ | Committee debates are soul-chats with opposing personas |
| speed-of-light/ | Many voices in one call — soul-chat's power |
| Symbol | Link |
|---|---|
SOUL-CHAT | PROTOCOLS.yml |
YAML-JAZZ | PROTOCOLS.yml — Comments carry meaning |
ABOUT-NOT-INSIDE | PROTOCOLS.yml — Chat files live outside |
BIG-ENDIAN | PROTOCOLS.yml — Naming conventions |
| Direction | Destination |
|---|---|
| ⬆️ Up | skills/ |
| ⬆️⬆️ Root | Project Root |
| 🎴 Sister | card/ |
| 🚪 Sister | room/ |