CtrlK
BlogDocsLog inGet started
Tessl Logo

nutrition-analyzer

分析营养数据、识别营养模式、评估营养状况,并提供个性化营养建议。支持与运动、睡眠、慢性病数据的关联分析。

39

Quality

40%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/nutrition-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

21%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is extremely verbose and poorly structured, reading more like a comprehensive nutritional science reference document than an actionable skill for Claude. The massive inline example report (~200 lines), exhaustive nutrient listings, and detailed algorithm code bloat the file enormously while providing little actionable guidance on how Claude should actually perform the analysis. The content would benefit dramatically from being split into separate reference files and condensed to focus on decision-making logic and workflow steps.

Suggestions

Reduce the content by 70-80%: remove exhaustive nutrient lists Claude already knows, trim the example report to one representative section, and move algorithm code and data schemas to separate bundle files (e.g., ALGORITHMS.md, DATA_SCHEMA.md, EXAMPLE_REPORT.md).

Add concrete validation steps to the workflow: verify data file existence, validate data completeness before analysis, check for anomalous values, and include error recovery paths.

Replace the high-level workflow steps with specific, actionable instructions: instead of '读取数据' and '数据分析', specify exactly what Claude should do at each step, what tools to use, and what decisions to make.

Create bundle files for the referenced data paths (data-example/*.json) and split the safety guidelines, algorithms, and example outputs into separate referenced files with clear navigation links.

DimensionReasoningScore

Conciseness

Extremely verbose at ~500+ lines. Extensively explains nutritional concepts Claude already knows (what RDA is, what vitamins are, what macronutrients are). The massive example report template, exhaustive lists of every vitamin and mineral, and detailed algorithm explanations are heavily padded. Most of this content could be reduced to 20% of its current size.

1 / 5

Actionability

Contains some executable Python code for RDA calculations and nutrient density scoring, but much of the content is descriptive rather than instructive. The code examples are illustrative pseudocode-like snippets (referencing undefined variables like RDA[v], daily_data fields) rather than truly executable code. The workflow steps are high-level ('读取数据', '数据分析') without concrete implementation.

3 / 5

Workflow Clarity

The 4-step workflow (确定分析范围 → 读取数据 → 数据分析 → 生成报告) is extremely high-level with no validation checkpoints. There's no verification that data files exist or are valid, no error handling for missing nutrients, no feedback loops for data quality issues. For a skill involving health data analysis, the absence of data validation steps is a significant gap.

2 / 5

Progressive Disclosure

Monolithic wall of text with everything inlined - massive example reports, full algorithm implementations, complete data schemas, exhaustive nutrient lists, and reference resources all in one file. No bundle files are provided despite references to data-example/ paths. Content that clearly belongs in separate files (algorithms, example reports, data schemas, safety guidelines) is all crammed into the main SKILL.md.

1 / 5

Total

7

/

20

Passed

Description

58%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description provides a solid enumeration of nutrition-related capabilities and mentions cross-domain analysis with exercise, sleep, and chronic disease data, which adds distinctiveness. However, it lacks an explicit 'Use when...' clause, which is critical for skill selection, and could benefit from more natural trigger terms and synonyms that users would actually say.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases, e.g., '当用户提到饮食分析、营养评估、膳食建议、卡路里追踪或食物日志时使用'

Include more natural user-facing synonyms and variations such as '饮食' (diet), '膳食计划' (meal plan), '卡路里' (calories), '食物记录' (food log) to improve trigger term coverage

Specify supported data formats or input types (e.g., CSV files, spreadsheets, API data) to further distinguish from generic health advice skills

DimensionReasoningScore

Specificity

Lists several specific actions: analyzing nutritional data, identifying nutritional patterns, assessing nutritional status, providing personalized nutrition advice, and cross-referencing with exercise/sleep/chronic disease data. Minor gaps in coverage (e.g., no mention of specific file formats or data sources).

4 / 5

Completeness

The 'what' is clearly stated with multiple concrete actions. However, there is no explicit 'when' clause (no 'Use when...' or equivalent trigger guidance), which caps this dimension at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Contains relevant domain keywords like '营养数据' (nutritional data), '营养模式' (nutritional patterns), '营养状况' (nutritional status), '运动' (exercise), '睡眠' (sleep), '慢性病' (chronic disease). However, it lacks common user-facing synonyms, file types, or natural phrasing variations users might say (e.g., 'diet', 'meal plan', 'calorie tracking', 'food log').

3 / 5

Distinctiveness Conflict Risk

The description carves out a fairly distinct niche around nutrition analysis and cross-referencing with health data (exercise, sleep, chronic disease). There is minor overlap risk with general health/wellness or fitness-related skills, but the nutrition-specific focus makes it mostly distinguishable.

4 / 5

Total

14

/

20

Passed

Validation

72%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation8 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (778 lines); consider splitting into references/ and linking

Warning

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

8

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.