菜单
Legacy compatibility entrypoint only for explicit old wording such as "body overview", "full body report", or "health dashboard". Route those requests to `body-data-qa` for ad-hoc synthesis or `body-cadence-review` for structured weekly, monthly, quarterly, or yearly reviews.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run structured weekly, monthly, quarterly, or yearly body reviews that compare time periods, cross-check multiple body data sources, and generate recommendations grounded in principles, goals, habits, systems, and local body documents. Trigger on review, recap, retrospective, compare periods, progress review, or holistic body check-in requests.
Provide specialist body-composition evidence from Withings data when `body-data-qa` or `body-cadence-review` needs composition-domain depth, or when the user explicitly asks for a body-composition-only deep dive.
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.
Provide specialist nutrition evidence from Yazio when `body-data-qa` or `body-cadence-review` needs diet-domain depth, or when the user explicitly asks for a nutrition-only deep dive.
Provide specialist exercise evidence from Garmin when `body-data-qa` or `body-cadence-review` needs training-domain depth, or when the user explicitly asks for an exercise-only deep dive.
Provide specialist medical checkup and lab-tracking evidence from local documents when `body-data-qa` or `body-cadence-review` needs medical-domain depth, or when the user explicitly asks for a medical-tracking-only deep dive.
| name | body-overview |
| description | Legacy compatibility entrypoint only for explicit old wording such as "body overview", "full body report", or "health dashboard". Route those requests to `body-data-qa` for ad-hoc synthesis or `body-cadence-review` for structured weekly, monthly, quarterly, or yearly reviews. |
This skill exists for compatibility with the older domain-first routing model. It should not be the main long-term workflow surface. Do not use it for ordinary broad body questions unless the user explicitly uses this older wording.
Use it to route broad requests:
body-data-qabody-cadence-reviewDo not duplicate synthesis logic here. Route first, then let the downstream workflow pull data, read goals, and search resources.
body-data-qa for default ad-hoc body questionsbody-cadence-review for structured reviews and period comparisonsChoose the target workflow before doing heavy analysis.
Route to body-data-qa when:
Route to body-cadence-review when:
Both workflows should rely on specialist domain evidence from:
body-sleepbody-recoverybody-compositionbody-dietbody-exercisebody-medical-checkupsThis skill should avoid duplicating specialist logic.
Routing layer only. Be brief and decisive.
Compatibility wrapper only. Prefer the downstream workflow schema rules:
body-data-qa -> no single schema for synthesized ad-hoc answers; use a domain schema only when returning structured domain evidencebody-cadence-review -> ../../schemas/cadence-review.json