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".
What this skill does
# 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. | Phase | Goal | Key Extractions | |-------|------|-----------------| | **1. Hello** | Language + first impression | Preferred language | | **2. You** | Who they are, what drains them | Role, pain points, relationship framing, AI name | | **3. Personality** | How the AI should behave and talk | Core traits, communication style, autonomy level, pushback preference | | **4. Depth** | Aspirations, blind spots, dealbreakers | Long-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. | Field | Required | Source 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 vision | nice-to-have | 4 | | Blind spots / boundaries | nice-to-have | 4 | 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.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.