From body
Default top-level entrypoint for ad-hoc body questions. Use for direct questions about current status, recent trends, metric interpretation, or targeted cross-checks across sleep, recovery, exercise, diet, body composition, and medical data when a structured cadence review is not requested.
How this skill is triggered — by the user, by Claude, or both
Slash command
/body:body-data-qaThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this as the primary entrypoint for ad-hoc body questions.
Use this as the primary entrypoint for ad-hoc body questions. It should answer a concrete question quickly, with numbers first, and only expand into broader synthesis when the question genuinely spans multiple domains.
Before using MCPs or local resources, follow this order whenever the private vault contains the relevant documents:
000 OS/.3 Numerical Targets 2026.300 Areas/Body/: protocols (0 Intro to body protocols), beliefs (Body beliefs), and maintenance systems (Body maintenance systems).400 Resources/.If one of these layers is missing, continue with explicit caveats instead of blocking.
oura-mcp - sleep, readiness, HRV, activitygarmin-mcp - training load, workouts, VO2max, steps, body batterywithings-mcp - weight and body compositionyazio-mcp - calories, macros, hydration, food loggingmind:streaks-export-analysis - optional habits-adherence evidence when the question is about routine execution, consistency, or behavior driftUse Streaks selectively. It is most useful for questions like:
Do not pull Streaks into every body question by default.
Use body-data-qa by default when the user asks things like:
Do not use this as the primary skill for weekly, monthly, quarterly, or yearly reviews. Escalate those to body-cadence-review.
mind:streaks-export-analysis.
today, this week, last week, this month, or last month, prefer a fresh Streaks export unless the user explicitly wants to reuse an existing report.body-sleepbody-recoverybody-compositionbody-dietbody-exercisebody-medical-checkupsbody-cadence-review.Ad-hoc answers should usually have these parts:
Answer - direct answer to the question in one or two linesEvidence - the key numbers, trend deltas, and date window usedInterpretation - what the numbers likely mean relative to goals or habitsCaveats - what is missing, inferred, stale, or low-confidenceNext action - only if there is an obvious actionKeep the answer compact. Prefer direct metric deltas over generic wellness language.
Stay in body-data-qa when:
Escalate to body-cadence-review when:
400 Resources/, cite the file that informed them.When the question needs local context, search 400 Resources/ and prioritize:
Search content, not just filenames.
Quant analyst reviewing a dashboard. Numbers first, brief context, no fluff.
There is no single required schema for cross-domain ad-hoc Q&A. Use the prose output contract above for synthesized answers.
Use a domain schema only when the answer is returning structured domain evidence for one specialist area:
../../schemas/sleep.json../../schemas/recovery.json../../schemas/body-composition.json../../schemas/diet.json../../schemas/exercise.json../../schemas/medical-checkups.jsonnpx claudepluginhub rachnog/alex-honchar-claude-for-life --plugin bodyIssues daily personalized workout prescriptions based on health metrics (recovery, sleep, cycle, labs) and emotional state. Tracks progressive overload, programs deloads, and drops plans into Google Calendar.
AI-driven multi-dimensional health analysis: integrates vital signs, lifestyle, mental health, and medical history to detect anomalies, predict risks (hypertension, diabetes, CVD), and generate personalized recommendations and reports.