CtrlK
BlogDocsLog inGet started
Tessl Logo

family-health-analyzer

分析家族病史、评估遗传风险、识别家庭健康模式、提供个性化预防建议

52

Quality

60%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/family-health-analyzer/SKILL.md

The canonical home for this skill is family-health-analyzer in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

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

The content is well-structured and reasonably concise with concrete risk-scoring and JSON examples, but algorithm details are incomplete and the batch/report workflow lacks explicit validation checkpoints and error-recovery feedback loops. Adding executable computation for the aggregation metrics and a validate-then-fix loop would lift actionability and workflow clarity.

Suggestions

Define how 家族聚集度 and the input counts are actually computed (executable formula or script), since the risk score currently depends on an undefined metric.

Add explicit validation checkpoints with fix-and-retry feedback loops after data loading and before report generation, given this is a batch data-integration + output workflow.

Tighten the overlap between 触发条件 and 步骤1 (确定分析目标) to remove the duplicated request-type listing.

DimensionReasoningScore

Conciseness

The body is lean and mostly assumes Claude's competence, with concrete formula/JSON snippets and a necessary medical disclaimer; minor repetition between 触发条件 and 步骤1 keeps it just below 5.

4 / 5

Actionability

Provides concrete elements (weighted risk formula, JSON advice schema, specific file paths, ECharts components) but key algorithm details like how 家族聚集度 is computed are undefined and no executable script code is given, matching the 'incomplete guidance' anchor.

3 / 5

Workflow Clarity

Eight steps are clearly sequenced and a validation step exists, but for a batch data-integration + report-generation workflow the validation is only listed without explicit checkpoints or fix-and-retry feedback loops, capping workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

Single self-contained file with clear section headers and no nested references; organization is good with minor gaps (disclaimer/JSON/viz detail could be split out), landing above the midpoint but below the well-signaled multi-file 5 anchor.

4 / 5

Total

14

/

20

Passed

Description

58%Weight 40%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 is reasonably specific and distinct, naming four concrete actions in a third-person voice, but it omits any explicit 'when to use' trigger guidance, which caps completeness at 3. Adding a 'Use when...' clause with natural user-facing phrases would lift both completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause with natural trigger phrases users would actually say (e.g. 'Use when the user asks for a family health report, family medical history analysis, or genetic risk assessment').

Add synonyms and concrete trigger tokens (家族病史/家族病史分析/遗传风险/家庭健康报告) to improve trigger-term coverage toward 5.

Mention report/visualization generation in the description so the 'what' covers the body's full capability set.

DimensionReasoningScore

Specificity

Lists four concrete actions (analyze family history, assess genetic risk, identify family health patterns, provide personalized prevention advice), matching the 'several specific actions' anchor; falls short of 5 because report generation and other body-level capabilities are absent.

4 / 5

Completeness

The description gives a clear 'what' (four named actions) but no explicit 'when' guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant domain keywords like 家族病史 and 遗传风险 that users might say, but provides no 'Use when...' phrasing, no synonyms, and no natural trigger variations, leaving it below 4.

3 / 5

Distinctiveness Conflict Risk

The family-health/genetic-risk niche is specialized and mostly distinct from other skills, with only minor overlap risk against closely related health skills; not 5 because the trigger phrasing is not sharply distinctive.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation14 / 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

Total

14

/

16

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.