claude-ally-health

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

Quality

21%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/claude-ally-health/SKILL.md

Quality

Content

7%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 essentially a placeholder with no substantive content. The same vague description is repeated three times across the overview, 'when to use,' and instructions sections, with no actionable guidance, code, examples, workflows, or supporting references. It fails on every dimension as it provides nothing Claude could use to perform health-related tasks.

Suggestions

Replace the repeated description with concrete instructions: define what health analysis tasks Claude should perform, with specific input/output examples (e.g., symptom input format → structured assessment output).

Add a clear workflow for symptom tracking with explicit steps, such as how to gather symptoms, what questions to ask, how to structure the output, and mandatory safety disclaimers/limitations.

Include actionable code or structured templates (e.g., JSON schema for symptom records, example wellness guidance responses) rather than linking to an external repository.

Add critical safety boundaries and disclaimers — a health skill must explicitly define what Claude should NOT do (e.g., diagnose conditions, replace professional medical advice) and when to recommend consulting a healthcare provider.

Dimension	Reasoning	Score
Conciseness	The content is short but entirely redundant — the description is repeated three times (overview, when to use, instructions) with no new information added each time. Every token is wasted on restating the same vague sentence.	2 / 5
Actionability	There is zero concrete guidance — no code, no commands, no specific steps, no examples. The entire body is a vague description with a link to an external repository, providing nothing actionable for Claude to execute.	1 / 5
Workflow Clarity	No workflow, steps, or process of any kind is described. There are no instructions for symptom tracking, medical information analysis, or wellness guidance — just a repeated abstract description.	1 / 5
Progressive Disclosure	There are no bundle files, no referenced supporting documents, and the only link is to an external GitHub repository with no indication of what content is there. The skill provides no structured navigation or content organization.	1 / 5
	Total	5 / 20 Passed

Description

36%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 too vague and generic, reading more like a category label than a functional skill description. It lacks concrete actions, specific trigger terms, and any 'when to use' guidance. The health domain provides some natural distinctiveness, but the breadth of the claimed scope without specifics makes it weak for skill selection.

Suggestions

Add a 'Use when...' clause with specific trigger phrases like 'Use when the user asks about symptoms, medication interactions, health conditions, or wellness recommendations'.

Replace generic category labels with concrete actions, e.g., 'Analyzes symptoms to suggest possible conditions, tracks daily health metrics, provides evidence-based wellness recommendations, and cross-references medication interactions'.

Include natural synonyms and variations users might say, such as 'health questions', 'feeling sick', 'side effects', 'nutrition advice', 'fitness', or 'medical conditions'.

Dimension	Reasoning	Score
Specificity	Names the domain (health/medical) and lists three high-level areas ('medical information analysis, symptom tracking, wellness guidance'), but these are generic category labels rather than concrete actions. No specific operations like 'log symptoms daily', 'cross-reference drug interactions', or 'generate health reports' are mentioned.	2 / 5
Completeness	Provides a vague 'what' (medical information analysis, symptom tracking, wellness guidance) but has no 'when' clause at all. There is no 'Use when...' or equivalent trigger guidance, which per the rubric should cap completeness at 3, and the weak 'what' brings it down further.	2 / 5
Trigger Term Quality	Includes some relevant keywords like 'medical information', 'symptom tracking', and 'wellness guidance' that users might mention, but misses many natural variations such as 'health advice', 'diagnosis', 'medication', 'fitness', 'nutrition', 'doctor', 'illness', or 'side effects'.	3 / 5
Distinctiveness Conflict Risk	The health/medical domain provides some specificity, but the broad scope covering 'medical information analysis, symptom tracking, and wellness guidance' could overlap with fitness skills, nutrition skills, mental health skills, or general wellness tools. The description doesn't carve out a clear niche.	3 / 5
	Total	10 / 20 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/claude-ally-health/SKILL.md
Commit: 57c135b

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.