CtrlK
BlogDocsLog inGet started
Tessl Logo

sexual-health-analyzer

Sexual Health Analyzer

33

Quality

30%

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/sexual-health-analyzer/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

31%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 comprehensive but bloated medical knowledge dump inlined into one file. It has useful concrete scoring tables yet lacks executable procedures, validation checkpoints, and any progressive-disclosure structure to keep the overview lean.

Suggestions

Move the detailed reference material (STD test details, contraceptive method comparisons, nutrient/exercise guidance, drug-interaction tables) into files under references/ and keep SKILL.md as a concise overview that links to them one level deep.

Cut explanations of general medical knowledge Claude already has (e.g., what ED is, how PDE5 inhibitors work, basic nutrient functions) and retain only the skill-specific decision criteria and thresholds.

Add a defined input data schema and explicit analysis workflows with validation checkpoints (e.g., verify data completeness before scoring, flag out-of-range IIEF-5 values) so the analysis steps are executable rather than descriptive.

DimensionReasoningScore

Conciseness

The body is an ~1100-line medical reference that extensively explains concepts Claude already knows (ED risk factors, STD windows, contraceptive efficacy, nutrient functions, exercise mechanisms). This matches anchor 1 ('Severely verbose; extensively explains concepts Claude already knows; heavily padded').

1 / 5

Actionability

Concrete guidance exists via scoring tables and numeric thresholds (IIEF-5 ED severity bands, weighted STD/ED risk scores, screening-frequency matrices), but there is no data schema, no code/commands, and the actual analysis execution remains high-level. This fits anchor 3 ('Some concrete guidance but incomplete; missing key details').

3 / 5

Workflow Clarity

The "使用场景" sections list numbered analysis sequences (e.g., ED辅助诊断 steps 1-6), so a sequence is present, but there are no validation/verification checkpoints or feedback loops. This matches anchor 3 ('Steps listed but validation gaps; checkpoints missing or implicit').

3 / 5

Progressive Disclosure

The skill is a single monolithic file with no bundle files and zero external references, while large blocks (STD details, contraceptive methods, nutrition, exercise, drug interactions) clearly belong in separate reference files. Section headers provide some structure, so it sits at anchor 2 ('Minimal structure; content that clearly belongs in separate files is inlined') rather than anchor 1.

2 / 5

Total

9

/

20

Passed

Description

28%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 effectively just a title — a domain label with no concrete actions and no trigger guidance. It tells Claude almost nothing about what the skill does or when to invoke it.

Suggestions

Rewrite the description to state concrete actions in third person, e.g. "Analyzes IIEF-5 scores, manages STD screening schedules, evaluates contraceptive efficacy, and correlates sexual-health data with medication, chronic-disease, and lifestyle modules."

Add an explicit 'Use when...' trigger clause naming natural user phrases, e.g. "Use when the user asks about erectile function (IIEF-5), STD screening, contraceptive choice, or sexual-health trends."

Include common synonyms/trigger terms (e.g. "ED", "STI screening", "birth control", "FSFI") so the skill surfaces for the phrasings users actually say.

DimensionReasoningScore

Specificity

The description is just the label "Sexual Health Analyzer"; it names the domain (sexual health) and implies an action via "Analyzer", but states no concrete actions at all. It is below anchor 3 ('1-2 concrete actions') but does name a domain, so it sits at anchor 2 ('Names the domain but actions are minimal or generic').

2 / 5

Completeness

It offers only a vague 'what' (a label implying analysis of sexual health) and entirely omits any 'when'/Use-when clause, matching anchor 2 ('Has a vague what and no when'). It cannot reach 3 because no trigger guidance is present, and the cap on missing 'Use when' guidance reinforces staying at or below 3.

2 / 5

Trigger Term Quality

Only the phrase "Sexual Health" is a somewhat natural keyword; "Analyzer" is not something a user would say, and there are no trigger phrases users would utter when needing the skill. This matches anchor 2 ('One or two generic keywords; missing the natural phrases users say').

2 / 5

Distinctiveness Conflict Risk

"Sexual Health" names a fairly specific niche, so it is somewhat distinguishable, but with no trigger phrases it could still overlap with general medical/health skills. This fits anchor 3 ('Somewhat specific but could still overlap with similar skills').

3 / 5

Total

9

/

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

skill_md_line_count

SKILL.md is long (1121 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
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.