Set up and operate the encrypted off-site backup for the chief-of-staff live data (board, guard, config, vault). Daily AES-256-GCM snapshots are pushed to a PRIVATE GitHub repo (immutable git history); the recovery key lives in the macOS Keychain. Use when bootstrapping the app on a new machine, when you need to RESTORE after data loss/corruption, to take an on-demand backup before a risky/bulk operation on live data, to verify backups are healthy, or when rotating the recovery key. This is a first-class setup skill alongside mcp-bridge-setup and guard-setup.
Sweep Gmail — BOTH received AND sent mail — and reconcile every thread onto the Cos board: link the message onto the matching case, advance or close tasks, move the lane, set catalog labels, dedup against existing cases so one matter is one card, and — the headline guardrail — NEVER undo the user's manual board edits. Use when the user says "go through my email and update the board", "sync my inbox / sent mail to the board", "reconcile email with my cases", "update the board from my mail", or when the scheduled mail sweep hands a batch of threads to be reconciled.
The reminder janitor — a periodic sweep that reviews every OPEN reminder on the board and CLOSES the ones whose job is already done or whose moment has passed, so the reminders list stays a live to-do surface instead of a graveyard of stale nudges. For each open reminder it reads the full context via the `board` MCP (the nudge, its due date, HOW LONG it has been sitting, its checklist, its linked emails, and — when it links a case — that case's current state), then takes a CRITICAL look and sorts each into CLOSE (the thing happened / got done → complete), DISMISS (no longer relevant / the decision window lapsed / superseded → dismiss), KEEP-OPEN (still live, or pinned by a star / priority), or NEEDS-YOU (a passed deadline it can't prove is settled). It AUTO-closes ONLY what is PROVEN done (a finished checklist, a linked case now closed, a delivery whose date clearly passed); every judgment call — a lapsed job-alert, an old "decide whether to" nudge, a cold FYI, anything tied to a starred node — it PROPOSES fo
Sweep WhatsApp — BOTH inbound AND the user's own sent messages, across DMs AND group chats with recent activity — and reconcile every chat onto the Cos board: link the message onto the matching case, advance or close tasks, move the lane, set catalog labels, dedup against existing cases so one matter is one card, and — the headline guardrail — NEVER undo the user's manual board edits. Use when the user says "go through my WhatsApp and update the board", "sync my chats to the board", "reconcile WhatsApp with my cases", "update the board from my messages", or when the scheduled WhatsApp sweep hands a batch of chats to be reconciled.
Manage the BODY add-on — the single owner of your body identity, your weight + body-composition history, and your GOAL. It drives the `body` MCP: set/read your FREE-TEXT objective (describe what you're after in your own words — fat loss, muscle gain, recomposition, maintenance — plus an optional target weight) via set_body_objective / get_body_objective; set/read your identity (sex, date of birth, height, training status, whether you lift) via set_body_profile / get_body_profile; log weigh-ins + body composition (weight, body-fat %, lean mass, waist) via log_weight / list_weights; and read the deterministic physiology facts (age, BMR, maintenance TDEE, BMI, fat-free mass, trend) via get_body_status. The goal is PROSE, not a pick-list. Use when the user says "set my goal", "I want to build muscle / lose fat / recomp / maintain", "I'm 178 cm", "I was born in 1991", "log my weight", "I'm 18% body fat", "my waist is 84 cm", "what's my BMR / maintenance / body status", or otherwise asks to define their body goal,
Manage the ATHLETE PROFILE — the Fitness add-on's TRAINING-FOCUS singleton that the AI coaching skills (training plan, weekly review, pre-workout brief) read to personalise their output. It SETS / UPDATES / READS the one profile per board via the `fitness` MCP's `get_athlete_profile` / `set_athlete_profile` tools: the training-focus goal + goal date, weekly availability (days/week, max session minutes), the sports trained, and the equipment on hand. It maps free-text ("I have a bike and a pool", "5 days a week, 90 min max") onto the English `VALID_ATHLETE_*` vocabularies and validates before writing. Training STATUS, your WEIGHT, and your BODY goal (fat loss / muscle / recomp) are NOT here — those live in the body add-on (the `body-profile` skill / the `body` MCP). Use when the user says "set my athlete profile", "I'm training for a triathlon", "I can train 4 days a week", "I have a kettlebell / a treadmill / pool access", "what's my training profile", or otherwise asks to define what they're TRAINING for and
The Fitness add-on OVERVIEW / router — the index that fires on GENERIC or ambiguous fitness requests and points you at the right FOCUSED skill. Use it when the user gestures at fitness without a specific ask — "help me with my fitness", "what can the fitness add-on do", "I want to get fit / train better / level up my training", "set me up for fitness", "where do I start with the fitness coach" — i.e. when the intent is clear (fitness) but the JOB is not. Do NOT use it when the request already names a job — those belong to the focused skills and own their own triggers: a weekly plan → fitness-training-plan; today's readiness / "should I train today" → fitness-pre-workout-brief; "how was my week" → fitness-weekly-review; sleep-vs-performance → fitness-correlations; pushing / logging / reading Apple Watch data → fitness-health-data; setting the training focus / availability / equipment → fitness-athlete-profile; setting the body goal / training status / weight / identity → body-profile. This skill routes; it doe
Surface and INTERPRET the sleep ↔ performance CORRELATIONS the board computes from the logged Apple-Watch + workout data — the deterministic stats twin of the Fitness add-on. The board computes (and persists) the Pearson r and the linear regression deterministically; YOU (the agent) trigger that compute via the `fitness` MCP and then read the numbers back to the user in plain language — strength + direction of the correlation, what the regression slope implies, and ACTIONABLE training guidance (e.g. "your deep-sleep correlation is strong → protect deep sleep before key sessions"), honest about small samples / weak links. You do NOT recompute Pearson yourself; the board owns the math. Use when the user says "how does my sleep affect my performance", "sleep vs performance", "correlate my sleep and training", "what affects my training", "does deep sleep help my workouts", "is my sleep linked to my training", "show me my sleep-performance correlation", or otherwise asks to relate their sleep to how they train. NO