CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skin-health-analyzer

Analyze skin health data, identify skin problem patterns, assess skin health status. Supports correlation analysis with nutrition, chronic diseases, and medication data.

Quality

56%

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

Quality

Content

42%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.

A well-structured but bloated monolith: the genuinely valuable skill-specific material (ABCDE scoring algorithm, weighted composite score, warning levels, scenario flows) is buried in ~700 lines of dermatology reference knowledge Claude already knows and non-instructional padding sections. No progressive disclosure is used despite the volume of reference-type content.

Suggestions

Cut the textbook knowledge sections (vitamin effects, drug reactions, disease-skin lists, ingredient knowledge) — Claude already knows this; keep only skill-specific scoring algorithms, thresholds, and output formats.

Delete non-instructional sections (未来扩展, 研究方向, 质量保证's 持续改进, generic 局限性 bullets) that direct no action.

Move clinical reference material (drug-skin interactions, disease associations, guideline citations) into reference files (e.g. references/drug-reactions.md) linked from a concise SKILL.md overview, and embed data-validation checkpoints directly into the scenario workflows instead of a separate QA section.

DimensionReasoningScore

Conciseness

The ~700-line body extensively enumerates textbook knowledge Claude already knows (vitamin effects on skin, drug-reaction types, disease-skin manifestations, generic prevention advice like SPF 30+ and 7-9 hours of sleep), plus non-instructional padding sections (局限性, 未来扩展, 研究方向, 质量保证/持续改进). This is noticeably verbose with several unnecessary sections — above the "heavily padded, no skill-specific value" of score 1 only because a minority of content (ABCDE algorithm, composite score, scenarios) is skill-specific, but far below score 3's "mostly efficient".

2 / 5

Actionability

Some genuinely concrete guidance exists: the ABCDE algorithm specifies 0-2 points per feature with a ≥4 referral threshold, the composite health score defines exact weights (30/25/20/15/10) and bands, warning levels carry timeframes (1 week), and six scenarios give numbered 6-step flows. But key execution details are missing — no data access method, no formats or thresholds behind steps like "分析血糖控制情况". This matches "some concrete guidance but incomplete / missing key details" rather than score 4, and exceeds score 2 because specific steps are given, not just high-level hints.

3 / 5

Workflow Clarity

The six scenarios provide clear, complete numbered sequences (e.g. retrieve 6 months of records → analyze → compute score → identify trends → generate report), but validation exists only as a separate 质量保证 section (data completeness, outlier detection) and is never embedded as a checkpoint within any workflow. This fits "steps listed but validation gaps; checkpoints missing or implicit" — the sequence quality exceeds score 2, but the disconnected validation keeps it below score 4.

3 / 5

Progressive Disclosure

The body has a clear, well-organized section hierarchy, so it is above score 2's "minimal structure". However, it is a single ~700-line monolith with hundreds of lines of clinical reference material (drug reactions, disease-skin associations, clinical guidelines, ingredient lists) inlined that clearly belongs in separate reference files — no bundle files exist and no external references are signaled. This matches "some structure but content that should be separate is inline"; score 4 would require the bulk of that material to live in well-signaled separate files.

3 / 5

Total

11

/

20

Passed

Description

53%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 names a distinct domain and several actions, but the verbs are abstract, the trigger vocabulary misses the natural terms users would say (acne, mole, rash, skincare), and it completely lacks a "Use when..." clause. It reads as a capability summary rather than an invocation trigger.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about skin problems, acne, moles, rashes, sun protection, or wants skin health trends or a skincare plan."

Replace abstract verbs with concrete deliverables, e.g. "track mole changes with ABCDE scoring, grade acne severity, compute a 0-100 skin health score, and generate skincare routines".

Include natural synonyms and scenario words users actually say (acne, mole, eczema, rash, sunscreen, skincare routine) to improve trigger matching.

DimensionReasoningScore

Specificity

The description lists several actions ("Analyze skin health data", "identify skin problem patterns", "assess skin health status", "Supports correlation analysis with nutrition, chronic diseases, and medication data"), but the verbs are abstract with no concrete deliverables, and coverage has gaps (trend analysis, mole monitoring, personalized recommendations from the body are absent). It exceeds the bare domain-naming of score 2 but lacks the concrete action specificity of score 4 examples like "Extracts text from PDF files, fills forms".

3 / 5

Completeness

The "what" is stated clearly (analyze data, identify patterns, assess status, correlation analysis), but the "when" is entirely absent — there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It fits the anchor "Has a clear 'what' but 'when' is missing or only weakly implied" exactly.

3 / 5

Trigger Term Quality

Relevant keywords are present ("skin health", "skin problem patterns", "nutrition", "chronic diseases", "medication data"), but common natural phrasings users would actually say are missing — acne, mole, rash, eczema, skincare, sunburn, dermatology. This matches "some relevant keywords but missing common variations or synonyms"; it is above score 2 (more than one or two generic keywords) but below score 4 (no synonym coverage of natural user terms).

3 / 5

Distinctiveness Conflict Risk

"Skin health" carves out a mostly distinct niche with a clear primary domain, but the correlation mentions ("nutrition, chronic diseases, and medication data") create minor overlap risk with general nutrition/chronic-disease/medication analysis skills — analogous to "Works with PDF and Word document files". It is not score 5 because the cross-module framing could pull triggers from adjacent health skills, and not score 3 because the skin-specific focus is clearly narrower than a generic "document files" analog.

4 / 5

Total

13

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (711 lines); consider splitting into references/ and linking

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

Path

skills/skin-health-analyzer/SKILL.md

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.