Turns your confidence-scored instincts into a portable, evidence-backed YAML pack. The unit of sharing is the instinct: `id / trigger / confidence / domain / source_repo` plus an `action` and `evidence` body.

Use when a host skill that benefits from biometric context runs: daily-journal (/journal), coaching, advisory-panel (/panel), patterns, or insights (/weekly, /monthly). Also use when the user asks how HRV, sleep, recovery, resting heart rate, steps, or workouts relate to a journal entry, coaching window, decision, pattern, or weekly review. Companion layer, never standalone. Setup: health-setup. Data import: ingest-health. Sync diagnostics: health-doctor.

Use when the user says /ingest-github <owner/repo> [--days N], or asks to ingest, capture, sync, pull, mirror, or import a GitHub repo's recent activity (merged PRs, issues, commits) into the vault, second brain, or knowledge graph, or wants repo history queryable by graphify or External Inputs refreshed. Not for opening PRs, creating issues, one-off PR diff reads, or non-GitHub sources (Slack, Notion, email have their own ingest-* connectors).

Use when bringing a teammate's, another machine's, or another harness's instincts into this vault: the user runs /instinct-import, shares a portable YAML instinct pack (PACK.yaml), or asks to merge, adopt, sync, or inherit shared instincts. Confidence-gated so local instincts are never clobbered. Part of the Instinct Engine; pairs with instinct-export. Do NOT use to author memories by hand (just write the file).

Use when the user wants multi-year health patterns from HealthKit + journal data: "patterns in my health data," "what does my body tell me," "correlations between mood and HRV," "Floor x body fingerprint," long-term trends in sleep, HRV, VO2max, cycle, or symptoms, "how has my body changed over the years," or /longitudinal. NOT for single-day analysis (use /health-doctor), this-week patterns (use /weekly), or journal-only pattern extraction (use /patterns).

Use when the user says /meeting-todos, "the meeting is done", "I just had a meeting", "pull the action items", "what did I commit to", or otherwise wants action items from a recent meeting note captured on their to-do list. Also when a meeting note or transcript needs its tasks pulled out. NOT for general task management, journaling, non-meeting notes (use note-todos), or pulling full meeting transcripts.

Turn a single speaking engagement into maximum content leverage. Run this after any talk, panel, fireside chat, or workshop.

Use when an operator asks which rule or policy governs a question — pricing exceptions, deploys, refunds, hiring — or wants to look up the matching rule in Meta/RESOLVER.md without reading the whole index by hand. Triggers: /resolver-query <question>, "which rule applies", "what's our policy on X", "does a rule cover this". Not for writing or editing rules (read-only) and not for rebuilding RESOLVER.md (use resolver-build.py).

Use when the user says /rise, "good morning", "buenos días", "let's start the day", "morning routine", "morning check-in", wants their morning consciousness routine, or asks to set the day's priorities or intention first thing after waking. Pairs with /journal at night. NOT for evening reflection (use /journal), pattern detection (use /patterns), or workout prescription (use /coach; /rise covers only the post-wake body wake-up flow).

Use when a recurring bug, support question, client incident, or manual task surfaces 2+ times, when a codified rule keeps getting violated despite being written down, when a teammate or client hits an issue anyone could hit, or when delivery/setup friction repeats. Triggers: "skillify this", "this keeps happening", "we hit this last week too", "make a skill for X", "automate this", "every client hits this", "I keep doing X manually", "turn this into a skill".

Use when the user asks for the weekly meta-review or Sunday wrap-up of their week and vault: says /sunday, /sunday-review, 'let's do the weekly review,' 'Sunday review,' 'review my week,' 'weekly retro,' 'week in review,' 'end-of-week review,' or wants journals, patterns, vault health, and stale decisions reviewed together at week's end. Not for a journal-pattern read alone (use /weekly) or mid-week single checks.

Use when maintaining the vault ITSELF as a system, not its content: knowledge-graph build/rebuild/query (graphify), second-brain mapping, vault diagnose/audit/hygiene, drift detection, extract rules from vault, backfill journals, setup vault types, consolidate memory (index over cap), Obsidian tooling (CLI/Bases/Markdown/JSON Canvas), vault bloat or Obsidian slow. Answering questions FROM the graph, use graph-query tools; daily journal/coaching/pattern detection, use those skills.