\u5065\u5eb7\u8d8b\u52bf\u5206\u6790\u5668 workflow skill. Use this skill when the user needs \u5206\u6790\u4e00\u6bb5\u65f6\u95f4\u5185\u5065\u5eb7\u6570\u636e\u7684\u8d8b\u52bf\u548c\u6a21\u5f0f\u3002\u5173\u8054\u836f\u7269\u3001\u75c7\u72b6\u3001\u751f\u547d\u4f53\u5f81\u3001\u5316\u9a8c\u7ed3\u679c\u548c\u5176\u4ed6\u5065\u5eb7\u6307\u6807\u7684\u53d8\u5316\u3002\u8bc6\u522b\u4ee4\u4eba\u62c5\u5fe7\u7684\u8d8b\u52bf\u3001\u6539\u5584\u60c5\u51b5\uff0c\u5e76\u63d0\u4f9b\u6570\u636e\u9a71\u52a8\u7684\u6d1e\u5bdf\u3002\u5f53\u7528\u6237\u8be2\u95ee\u5065\u5eb7\u8d8b\u52bf\u3001\u6a21\u5f0f\u3001\u968f\u65f6\u95f4\u7684\u53d8\u5316\u6216"\u6211\u7684\u5065\u5eb7\u72b6\u51b5\u6709\u4ec0\u4e48\u53d8\u5316\uff1f"\u65f6\u4f7f\u7528\u3002\u652f\u6301\u591a\u7ef4\u5ea6\u5206\u6790\uff08\u4f53\u91cd/BMI\u3001\u75c7\u72b6\u3001\u836f\u7269\u4f9d\u4ece\u6027\u3001\u5316\u9a8c\u7ed3\u679c\u3001\u60c5\u7eea\u7761\u7720\uff09\uff0c\u76f8\u5173\u6027\u5206\u6790\uff0c\u53d8\u5316\u68c0\u6d4b\uff0c\u4ee5\u53ca\u4ea4\u4e92
\u5065\u5eb7\u8d8b\u52bf\u5206\u6790\u5668 workflow skill. Use this skill when the user needs \u5206\u6790\u4e00\u6bb5\u65f6\u95f4\u5185\u5065\u5eb7\u6570\u636e\u7684\u8d8b\u52bf\u548c\u6a21\u5f0f\u3002\u5173\u8054\u836f\u7269\u3001\u75c7\u72b6\u3001\u751f\u547d\u4f53\u5f81\u3001\u5316\u9a8c\u7ed3\u679c\u548c\u5176\u4ed6\u5065\u5eb7\u6307\u6807\u7684\u53d8\u5316\u3002\u8bc6\u522b\u4ee4\u4eba\u62c5\u5fe7\u7684\u8d8b\u52bf\u3001\u6539\u5584\u60c5\u51b5\uff0c\u5e76\u63d0\u4f9b\u6570\u636e\u9a71\u52a8\u7684\u6d1e\u5bdf\u3002\u5f53\u7528\u6237\u8be2\u95ee\u5065\u5eb7\u8d8b\u52bf\u3001\u6a21\u5f0f\u3001\u968f\u65f6\u95f4\u7684\u53d8\u5316\u6216"\u6211\u7684\u5065\u5eb7\u72b6\u51b5\u6709\u4ec0\u4e48\u53d8\u5316\uff1f"\u65f6\u4f7f\u7528\u3002\u652f\u6301\u591a\u7ef4\u5ea6\u5206\u6790\uff08\u4f53\u91cd/BMI\u3001\u75c7\u72b6\u3001\u836f\u7269\u4f9d\u4ece\u6027\u3001\u5316\u9a8c\u7ed3\u679c\u3001\u60c5\u7eea\u7761\u7720\uff09\uff0c\u76f8\u5173\u6027\u5206\u6790\uff0c\u53d8\u5316\u68c0\u6d4b\uff0c\u4ee5\u53ca\u4ea4\u4e92\u5f0fHTML\u53ef\u89c6\u5316\u62a5\u544a\uff08ECharts\u56fe\u8868\uff09\u3002 and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/health-trend-analyzer from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
健康趋势分析器 分析一段时间内健康数据的趋势和模式，识别变化、相关性，并提供数据驱动的健康洞察。
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: 核心功能, 使用说明, 输出格式, 数据源, 分析算法, 安全与隐私.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
需要分析一段时间内健康数据的趋势、相关性或显著变化时使用。
任务涉及体重、症状、用药、化验、情绪或睡眠等多维度随时间变化。
用户询问“最近健康状况有什么变化”或需要趋势报告时使用。
Use when the request clearly matches the imported source intent: 分析一段时间内健康数据的趋势和模式。关联药物、症状、生命体征、化验结果和其他健康指标的变化。识别令人担忧的趋势、改善情况，并提供数据驱动的洞察。当用户询问健康趋势、模式、随时间的变化或"我的健康状况有什么变化？"时使用。支持多维度分析（体重/BMI、症状、药物依从性、化验结果、情绪睡眠），相关性分析，变化检测，以及交互式HTML可视化报告（ECharts图表）。.
Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Use when provenance needs to stay visible in the answer, PR, or review packet.
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
Validate the result against the upstream expectations and the evidence you can point to in the copied files.
Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.
Imported Workflow Notes
Imported: 核心功能
1. 多维度趋势分析
体重/BMI 趋势：追踪体重和BMI随时间的变化，评估健康趋势
症状模式：识别反复出现的症状、频率变化、潜在诱因
药物依从性：分析用药规律，识别漏服模式和改善空间
化验结果趋势：追踪生化指标变化（胆固醇、血糖、血压等）
情绪与睡眠：关联情绪状态与睡眠质量，识别心理健康趋势
2. 相关性分析引擎
药物-症状相关性：识别新药物是否与症状变化相关
生活方式影响：关联饮食/睡眠与症状和情绪
治疗效果评估：衡量治疗是否导致改善
周期-症状相关性：女性健康追踪中的周期相关性
3. 变化检测
显著变化：警告快速体重变化、新症状、药物变化
恶化模式：早期识别健康状况下降
改善识别：强调积极的健康变化
阈值警报：接近危险水平时警告（辐射、BMI极值）
4. 预测性洞察
风险评估：基于趋势识别风险因素
预防建议：基于模式建议预防措施
早期预警：在问题变得严重之前预测
Examples
Example 1: Ask for the upstream workflow directly
Use @health-trend-analyzer to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @health-trend-analyzer against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @health-trend-analyzer for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @health-trend-analyzer using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Treat generated examples as scaffolding; adapt them to the concrete task before execution.
Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/health-trend-analyzer, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
