CtrlK
BlogDocsLog inGet started
Tessl Logo

claude-ally-health

A health assistant skill for medical information analysis, symptom tracking, and wellness guidance.

40

Quality

39%

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/claude-ally-health/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

28%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 body is a thin, repetitive overview that restates the description three times without any actionable guidance, workflow steps, or substantive references. It avoids verbosity but offers almost nothing for Claude to act on.

Suggestions

Replace the repeated description with concrete instructions: specific commands, data formats, or example prompts the skill should follow.

Add a clear sequenced workflow for the core task (e.g., intake → symptom analysis → guidance output) with validation checkpoints.

Remove the verbatim duplication across Overview/When to Use/Instructions and point to real reference files for detailed material.

DimensionReasoningScore

Conciseness

The body is short, but the same description phrase is repeated verbatim three times (Overview, When to Use, Instructions) with awkward double periods, so it is mostly efficient yet padded with unnecessary repetition that could be tightened.

3 / 5

Actionability

The Instructions section only states 'This skill provides guidance and patterns for...' with no code, commands, or concrete steps — it describes rather than instructs, matching the 'entirely vague or abstract; only describes rather than instructs' anchor.

1 / 5

Workflow Clarity

No multi-step sequence or single unambiguous action is present; the sections give rough structure but no defined steps, checkpoints, or validation, sitting just above the incoherent/missing anchor at 'rough structure present but many gaps'.

2 / 5

Progressive Disclosure

The file is under 50 lines with organized sections, but the content is duplicated across sections and the only reference is an external GitHub URL rather than one-level-deep bundle files, so structure is present but organization and signaling are mediocre.

3 / 5

Total

9

/

20

Passed

Description

50%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 a competent but generic health-domain summary: it states what the skill covers without concrete actions or an explicit 'Use when' trigger clause. All dimensions land at the midpoint because the phrasing is recognizable yet unspecific.

Suggestions

Replace abstract noun phrases with concrete verbs (e.g., 'Triages symptoms, logs vitals, and summarizes lab results') to lift specificity.

Add an explicit trigger clause: 'Use when the user mentions symptoms, wants to track health metrics, or asks for wellness guidance.'

Include natural synonyms and concrete file/data terms users would actually say to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the health domain and lists three action areas ('medical information analysis, symptom tracking, and wellness guidance'), but these are abstract noun phrases rather than concrete executable actions like 'extracts text' or 'fills forms', matching the 'names domain and a few actions but not comprehensive' anchor.

3 / 5

Completeness

It clearly states what the skill does but provides no 'Use when...' clause or explicit trigger guidance, which per the judging guidelines caps completeness at 3 — exactly matching the 'clear what but when missing' anchor.

3 / 5

Trigger Term Quality

It includes some natural terms a user might say ('symptom tracking', 'wellness', 'medical information') but misses common variations, synonyms, and concrete triggers, fitting the 'some relevant keywords but missing common variations' anchor rather than the fuller coverage of 4.

3 / 5

Distinctiveness Conflict Risk

The medical/health niche is a recognizable domain, but 'wellness guidance' is broad and could overlap with general wellness or fitness skills, placing it at 'somewhat specific but could still overlap' rather than the mostly-distinct 4.

3 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

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.