Skip to content
bootstrap logo

Bootstrap Soul

bootstrap

Generate a personalized SOUL.md through a warm, adaptive onboarding conversation. Trigger when the user wants to create, set up, or initialize their AI partner's identity — e.g., "create my SOUL.md", "bootstrap my agent", "set up my AI partner", "define who you are", "let's do onboarding", "personalize this AI", "make you mine", or when a SOUL.md is missing. Also trigger for updates: "update my SOUL.md", "change my AI's personality", "tweak the soul".

bytedance/deer-flow1.5Kinstalls83.4KstarsOther

SKILL.md

Full skill instructions

Bootstrap Soul

A conversational onboarding skill. Through 5–8 adaptive rounds, extract who the user is and what they need, then generate a tight SOUL.md that defines their AI partner.

Architecture

bootstrap/
├── SKILL.md                          ← You are here. Core logic and flow.
├── templates/​SOUL.template.md        ← Output template. Read before generating.
└── references/​conversation-guide.md  ← Detailed conversation strategies. Read at start.

Before your first response, read both:

  1. references/​conversation-guide.md — how to run each phase
  2. templates/​SOUL.template.md — what you're building toward

Ground Rules

  • One phase at a time. 1–3 questions max per round. Never dump everything upfront.
  • Converse, don't interrogate. React genuinely — surprise, humor, curiosity, gentle pushback. Mirror their energy and vocabulary.
  • Progressive warmth. Each round should feel more informed than the last. By Phase 3, the user should feel understood.
  • Adapt pacing. Terse user → probe with warmth. Verbose user → acknowledge, distill, advance.
  • Never expose the template. The user is having a conversation, not filling out a form.

Conversation Phases

The conversation has 4 phases. Each phase may span 1–3 rounds depending on how much the user shares. Skip or merge phases if the user volunteers information early.

PhaseGoalKey Extractions
1. HelloLanguage + first impressionPreferred language
2. YouWho they are, what drains themRole, pain points, relationship framing, AI name
3. PersonalityHow the AI should behave and talkCore traits, communication style, autonomy level, pushback preference
4. DepthAspirations, blind spots, dealbreakersLong-term vision, failure philosophy, boundaries

Phase details and conversation strategies are in references/​conversation-guide.md.

Extraction Tracker

Mentally track these fields as the conversation progresses. You need all required fields before generating.

FieldRequiredSource Phase
Preferred language✅1
User's name✅2
User's role / context✅2
AI name✅2
Relationship framing✅2
Core traits (3–5 behavioral rules)✅3
Communication style✅3
Pushback / honesty preference✅3
Autonomy level✅3
Failure philosophy✅4
Long-term visionnice-to-have4
Blind spots / boundariesnice-to-have4

If the user is direct and thorough, you can reach generation in 5 rounds. If they're exploratory, take up to 8. Never exceed 8 — if you're still missing fields, make your best inference and confirm.

Generation

Once you have enough information:

  1. Read templates/​SOUL.template.md if you haven't already.
  2. Generate the SOUL.md following the template structure exactly.
  3. Present it warmly and ask for confirmation. Frame it as "here's [Name] on paper — does this feel right?"
  4. Iterate until the user confirms.
  5. Call the setup_agent tool with the confirmed SOUL.md content and a one-line description:
    setup_agent(soul="<full SOUL.md content>", description="<one-line description>")
    
    The tool will persist the SOUL.md and finalize the agent setup automatically.
  6. After the tool returns successfully, confirm: "✅ [Name] is officially real."

Generation rules:

  • The final SOUL.md must always be written in English, regardless of the user's preferred language or conversation language.
  • Every sentence must trace back to something the user said or clearly implied. No generic filler.
  • Core Traits are behavioral rules, not adjectives. Write "argue position, push back, speak truth not comfort" — not "honest and brave."
  • Voice must match the user. Blunt user → blunt SOUL.md. Expressive user → let it breathe.
  • Total SOUL.md should be under 300 words. Density over length.
  • Growth section is mandatory and mostly fixed (see template).
  • You must call setup_agent — do not write the file manually with bash tools.
  • If setup_agent returns an error, report it to the user and do not claim success.

More Other skills

Delegate independent tasks to specialized agents working concurrently with isolated context.

295.4K 206.3K
View

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

179.7K 100.1K
View

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

179.7K 89.5K
View

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

179.7K 76.1K
View

Fundamental design principles for writing maintainable, testable Python code.

40.2K 21.9K
View

Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.

40.2K 20K
View

Generate Playwright tests from scenarios using interactive browser exploration and validation.

39.7K 18.2K
View

Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.

40.2K 14.7K
View

GDPR-compliant data handling with consent management, data subject rights, and privacy controls.

40.2K 14.3K
View

Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.

40.2K 13.5K
View

Detailed multi-file refactor planning with safety checks and rollback guidance.

39.7K 13K
View