CtrlK
BlogDocsLog inGet started
Tessl Logo

claude-ally-health

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

39

Quality

38%

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

26%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 structurally clean and token-light but content-empty: it restates the description across three sections and provides no actionable guidance, concrete steps, or workflow. It functions as a stub rather than usable skill instructions.

Suggestions

Replace the abstract Instructions section with concrete, executable guidance or code examples for the skill's core tasks (symptom tracking, medical information analysis).

Add a numbered workflow with explicit validation checkpoints for any destructive or batch health-data operations.

Remove the redundant restatements across Overview, When to Use, and Instructions so each section adds distinct information.

DimensionReasoningScore

Conciseness

The body is short and does not explain concepts Claude already knows, but it pads three sections ('Overview', 'When to Use This Skill', 'Instructions') with near-identical restatements of the same sentence, so it could be tightened; not a 4 because the redundancy is unnecessary padding.

3 / 5

Actionability

The Instructions section only states 'This skill provides guidance and patterns for...' with no concrete code, commands, or specific steps, matching the 'entirely vague or abstract; only describes rather than instructs' anchor; it cannot be lower and is clearly not a 2 since there are no high-level executable hints.

1 / 5

Workflow Clarity

There are no steps, sequence, or validation checkpoints anywhere in the body, matching the 'steps missing or incoherent; no sequence' anchor; not a 2 because even a rough sequence is absent.

1 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references beyond a source link, and is organized into clear sections (Overview, When to Use, Instructions), so the simple-skill exception applies; not a 5 because the content is thin and repetitive rather than cleanly well-organized.

4 / 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 conveys a clear domain and several capability categories but lacks concrete action specifics, trigger-term variations, and any 'when to use' guidance. It reads as a generic health-assistant label rather than a distinctive, trigger-rich description.

Suggestions

Add a concrete 'Use when...' clause with natural trigger phrases (e.g., 'Use when the user asks about symptoms, wants to track wellness metrics, or needs medical information analysis').

Replace abstract category labels with specific concrete actions (e.g., 'log symptoms over time', 'summarize lab results', 'suggest wellness routines').

Include synonyms and natural variations of trigger terms to improve distinctiveness and reduce conflict with other skills.

DimensionReasoningScore

Specificity

Names the health domain and lists a few action categories ('medical information analysis, symptom tracking, and wellness guidance'), but they are abstract labels rather than concrete operations, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; not a 4 because no specific actionable capabilities are enumerated.

3 / 5

Completeness

Clearly states what the skill does but includes no 'Use when...' or equivalent trigger clause, so per the guideline completeness is capped at 3; not a 4 because 'when' guidance is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Contains relevant keywords like 'health', 'medical', 'symptom', and 'wellness' that users might say, but misses common variations and synonyms; not a 4 because coverage is partial rather than good.

3 / 5

Distinctiveness Conflict Risk

The broad health/wellness framing ('health assistant skill for medical information analysis, symptom tracking, and wellness guidance') is somewhat specific but could overlap with other medical or wellness skills; not a 4 because the niche is not sharply distinguished.

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.