fluxly Search skills… ⌘K 中文 Publish

nutrition-analyzer

Other Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Other
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@huifer · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Permissions
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview nutrition-analyzer.preview 
---
name: nutrition-analyzer
description: 分析饮食和营养数据，识别营养模式，评估营养状况，并提供个性化营养改善建议。 分析营养素摄入的变化趋势，识别改善或需要关注的方面。 评估营养素摄入是否达到推荐标准（RDA/AI）。 分析营养与其…
category: other
runtime: Python
---

# nutrition-analyzer output preview

## PART A: Task fit
- Use case: 分析饮食和营养数据，识别营养模式，评估营养状况，并提供个性化营养改善建议。 分析营养素摄入的变化趋势，识别改善或需要关注的方面。 评估营养素摄入是否达到推荐标准（RDA/AI）。 分析营养与其他健康指标的相关性。 基于用户数据生成个性化营养改善建议。 runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “功能 / 1. 营养趋势分析 / 2. 营养素摄入评估” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “分析饮食和营养数据，识别营养模式，评估营养状况，并提供个性化营养改善建议。 分析营养素摄入的变化趋势，识别改善或需要关注的方面。 评估营养素摄入是否达到推荐标准（RDA/AI）。 分析营养与其他健康指标的相关性。 基于用户数据生成个性化营养改善建议。 runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “功能 / 1. 营养趋势分析 / 2. 营养素摄入评估” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: 分析饮食和营养数据，识别营养模式，评估营养状况，并提供个性化营养改善建议。 分析营养素摄入的变化趋势，识别改善或需要关注的方面。 分析维度： 宏量营养素趋势（蛋白质、碳水、脂肪、纤维、卡路里） 微量营养素趋势（维生素、矿物质） 热量来源分布变化 餐食模式（…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “功能”, “1. 营养趋势分析”, “2. 营养素摄入评估”, “3. 营养状况评估”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name nutrition-analyzer directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “功能 / 1. 营养趋势分析 / 2. 营养素摄入评估” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.