soul-audit
6-phase interactive interview that generates the agent's identity (SOUL.md), user profile (USER.md), access control (ACCESS_POLICY.md), and operational cadence (HEARTBEAT.md). Re-runnable anytime to update any section.
What this skill does
# Soul Audit — Agent Identity Builder Generate the agent's identity and operational configuration through an interactive interview. Each phase produces a file. Any phase can be re-run independently to update. **IMPORTANT:** This skill generates content from the USER'S OWN ANSWERS. It NEVER ships pre-filled content. The templates in `templates/` are scaffolds, not defaults. ## Contract This skill guarantees: - SOUL.md generated from user's description of agent identity, vibe, mission - USER.md generated from user's self-description (role, projects, key people) - ACCESS_POLICY.md generated with configurable access tiers - HEARTBEAT.md generated with operational cadence the user chooses - Each phase is independent and re-runnable - Default mode (skip soul-audit): installs minimal templates from `templates/` ## Phases ### Phase 1: Identity Interview Ask: "What is this agent to you? Research partner? Executive assistant? Thinking partner? All of the above?" Generate: SOUL.md identity section. ### Phase 2: Vibe Calibration Show 3-4 communication style examples: - **Formal:** "I've prepared a comprehensive analysis of the situation..." - **Direct:** "Here's what's happening. Three things matter." - **Technical:** "The root cause is in the connection pooling. Here's the fix." - **Casual:** "Yeah so basically the thing is broken because X. Easy fix." Ask which feels right. Generate: SOUL.md vibe + communication style sections. ### Phase 3: Mission Mapping Ask: "What are your top 3-5 goals? What are you trying to accomplish?" Generate: SOUL.md mission + operating principles sections. ### Phase 4: User Profile Ask: "Tell me about yourself. What do you do? What are you working on? Who are the key people in your world?" Generate: USER.md with role, projects, key people, communication preferences. ### Phase 5: Boundaries Ask: "Who should have access to your brain? Are there people who should see some but not all? Anyone to keep out entirely?" Generate: ACCESS_POLICY.md with 4 tiers (Full/Work/Family/None). ### Phase 6: Operational Cadence Ask: "How often should the agent check in? Morning briefing? End of day summary? What recurring jobs do you want?" Generate: HEARTBEAT.md with operational cadence. ## Default Mode (Skip Soul-Audit) If the user skips soul-audit on first boot: - Install `templates/SOUL.md.template` as SOUL.md (minimal: "knowledge-first agent with persistent memory") - Install `templates/USER.md.template` as USER.md (auto-populate name/email from git config) - Install `templates/ACCESS_POLICY.md.template` as ACCESS_POLICY.md (owner-only access) - Install `templates/HEARTBEAT.md.template` as HEARTBEAT.md (default cadence) ## Output Format Four files generated/updated. Report: "Soul audit complete: SOUL.md, USER.md, ACCESS_POLICY.md, HEARTBEAT.md created. Re-run any phase anytime to update." ## Anti-Patterns - Shipping pre-filled SOUL.md or USER.md content (privacy violation) - Making soul-audit mandatory on first boot (high friction, optional is better) - Asking all 6 phases in one go (overwhelming, each is independent) - Not offering to re-run individual phases
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.