CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-analyzer

AI驱动的综合健康分析系统,整合多维度健康数据、识别异常模式、预测健康风险、提供个性化建议。支持智能问答和AI健康报告生成。

49

Quality

55%

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/ai-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The body presents a well-sequenced, well-organized workflow with concrete data sources, but keeps all detail inline, describes core algorithms rather than implementing them, and references a missing script. Validation checkpoints and progressive disclosure to reference files would lift it further.

Suggestions

Provide executable implementations (or reference files) for the core algorithms rather than describing them at a high level, and remove or supply the missing scripts/generate_ai_report.py.

Add explicit validation checkpoints in the workflow (e.g., verify data files exist and are well-formed before analysis; confirm report output before recording history).

Move algorithm details, the data-source table, and safety rules into one-level-deep reference files to reduce inline length and improve navigation.

DimensionReasoningScore

Conciseness

The body is mostly efficient and well-organized, but risk types and algorithms are restated across "核心功能", "执行步骤", and "算法说明", so it could be tightened rather than fully lean.

2 / 3

Actionability

Concrete file paths and readFile/exists snippets are provided, but the core algorithms (CUSUM, Z-score, Framingham, ASCVD) are described rather than given as executable code, and the referenced scripts/generate_ai_report.py does not exist in the bundle.

2 / 3

Workflow Clarity

A clear 9-step sequence is present, but there are no explicit validation checkpoints or validate-fix-retry feedback loops, which keeps it below the level-3 anchor.

2 / 3

Progressive Disclosure

The single SKILL.md is well-sectioned, but at ~220 lines with all algorithm and data-source detail inline and a broken reference to a non-existent script, it is not split into one-level-deep reference files.

2 / 3

Total

8

/

12

Passed

Description

60%

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 concretely enumerates the system's capabilities but omits any explicit "when to use" trigger guidance, capping completeness. Trigger terms are present but lean toward feature-listing rather than natural user phrasing.

Suggestions

Add a "Use when..." clause naming natural user phrases (e.g., "Use when the user asks to analyze their health data, predict health risks, or generate an AI health report").

Include more common natural-language variations of triggers a user would actually say, beyond feature names.

Sharpen the distinctiveness by stating what uniquely separates this from generic health-tracking skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: "整合多维度健康数据、识别异常模式、预测健康风险、提供个性化建议" plus "智能问答和AI健康报告生成", matching the multi-action anchor rather than the single-action level 2.

3 / 3

Completeness

Clearly answers "what" the system does, but provides no "Use when..." or equivalent trigger guidance, so per the rubric guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

Contains some relevant natural terms (健康风险, AI健康报告, 智能问答) but these read as feature descriptions more than phrases a user would naturally say, and common variations are missing.

2 / 3

Distinctiveness Conflict Risk

The AI-health-analysis niche is reasonably specific, but without explicit distinct triggers it could overlap with other health/wellness skills, matching the level-2 anchor.

2 / 3

Total

9

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository
sickn33/antigravity-awesome-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.