When many related, high-confidence instincts pile up in one domain, that is a signal to promote them into ONE reusable structure instead of leaving them as loose memories. `/evolve` finds those clusters deterministically and drafts a proposal you refine.

Merges another harness's or teammate's instinct pack into your vault WITHOUT clobbering your own hard-won instincts. The merge rule is confidence-gated.

You are extracting signal before it evaporates. This skill scans recent sessions and surfaces what's hardening into real insight, then proposes concrete captures.

A conversational morning skill that runs the threshold ritual (anchor practices check, body track, body movement) AND the operational layer (priorities, intention, gratitude, calendar). One skill, one flow.

You are setting up a new user's AI-powered second brain. This is an interactive, conversational setup, not a script dump. Go step by step, wait for their answers, and adapt to what they have.

Longevity + fitness coach. Issues a daily workout prescription that reads from health-mcp (recovery, sleep, cycle phase, somatic state, lab status) and pairs with today's Floor (emotional state) from journal frontmatter. Tracks progressive overload per-lift. Programs deload every 4th week. Drops weekly plan into Google Calendar. Use when user says /coach, /coach today, /coach week, /coach profile, /coach log, asks "what should I do today", asks for a workout, asks for a longevity plan, or asks how to train. Pairs with health-context (already auto-fires) and insights (already body-track wired). The substrate's longevity-coach surface.

First-principles analyst. Surfaces hidden assumptions, finds foundational truths, rebuilds from scratch, identifies the high-leverage move.

Auto-stash uncommitted work in code repos on every Claude Code Stop/SubagentStop event, so 60+ exchange sessions can't lose work to a branch switch. Stop hook scoped to ~/dev/* repos (vault is covered by its own snapshot script). Recoverable via `git stash list | grep claude-checkpoint`.

Per-session git worktree pattern for ~/dev/<repo> code repos. Prevents the CONCURRENT-SESSION-HEAD-DRIFT bug class where two Claude Code sessions writing to the same physical checkout collide on the single .git/HEAD pointer + index + working tree. Ships a wrapper script + hookify warn rule + the rule prose. Complements dev-repo-checkpoints (recovery) by preventing the failure at the structural layer (isolation).

Walk a user through what changes when they take ai-brain-starter from a personal vault to a team vault. Reads the for-teams/ folder aloud in conversation, asks three diagnostic questions, and closes with the path to having it built for them. Trigger when the user asks any variant of "how do I add my team to this," "optimize this for my company," "what does the team version look like," or anything else that signals they want the multi-person version of the brain.

Observability surface for the health-mcp auto-trigger chain. Shows freshness of every data source (Apple Health, Oura, Fitbit, labs), last coach prescription + completion, missed-day count, lab status flags, and which auto-trigger hooks are installed. Use when user says /health doctor, /health status, asks "is the auto-chain working", "when was the last sync", "did the coach prescribe today", or wants to debug why a prescription didn't appear in calendar.

Pre-configured creator-economy vertical pack for the ai-brain-starter substrate. Ships typed-memory categories for audience, DMs, content, collabs, and creator revenue; connector configs for Instagram, TikTok, YouTube, Substack, X, LinkedIn, Stan Store, Stripe, Patreon; retention defaults aligned with Meta + TikTok + YouTube data-handling expectations; decision-audit patterns for sponsored-disclosure and brand-deal terms. Use when onboarding a creator, personal-brand operator, or content-engine team that needs the substrate to come pre-shaped to the work rather than starting from a blank vault.

Ingests recent Slack messages into the vault as markdown the graphify pipeline can read and the rest of the AI Brain Starter substrate (decision log, session-close cascade, hooks) can act on.

Ingests recent WhatsApp messages (from a group chat or a one-on-one conversation) into the vault as markdown the graphify pipeline can read and the rest of the AI Brain Starter substrate (decision log, session-close cascade, hooks) can act on.

After a meeting, pull action items from the transcript/notes and update your to-do file.

Extract action items from any non-meeting note (class notes, book notes, podcast notes, transcripts, panel writeups) and route them to the scope-correct to-do file with wikilinking and per-task owner tags. Generalization of meeting-todos. Trigger with /note-todos [filename-or-pattern]. For meetings, prefer /meeting-todos which carries the full meeting workflow cascade.

Use this skill every time the user shares a GitHub URL or asks whether an external project beats the current stack. Goal: an honest answer, not adoption theater. The shiny repo may lose. The current stack may lose. Either outcome is fine. What is NOT fine is skipping the extraction because the repo

Unified vault-mapping pipeline. Extracts structured metadata from every typed file in your vault (books, meetings, people, articles, goals, etc.), optionally runs knowledge-graph extraction, applies wikilinks, and surfaces cross-type insights you can't see from any single file. Zero LLM cost per run for metadata + insights. Use whenever you want to "map your second brain", refresh your vault's queryable index, or discover cross-doc patterns.

Catches secrets and unsafe patterns the moment a Claude Code agent writes them, not after the fact. Public substrate version (MIT). Free to install, free to extend.

Generate a client-ready security hygiene snapshot for a prospect domain. Free lead magnet for consulting practices. Outputs a markdown report covering SSL/TLS grade, HTTP security headers, email authentication (SPF/DMARC), and server fingerprint leaks. Use when the user says /security-snapshot, /snapshot [domain], "run a security check on X", or "generate a security report for [company]". Do NOT use for penetration testing, internal infrastructure audits, or application-layer vulnerability assessment. This is a passive, unauthenticated scan for conversation-starter value, not a full audit.