CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

concept-explainer

Uses analogies to explain complex medical concepts in accessible terms.

Quality

60%

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 ./scientific-skills/Evidence Insight/concept-explainer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 core usage content (commands, parameters, output format, examples) is solid and actionable, but it is buried in roughly 19 sections of template boilerplate, self-referential filler, and duplicated sections that waste the context window. The bundle's single reference file is neither named nor meaningfully populated, leaving progressive disclosure weak.

Suggestions

Cut the template filler: remove the self-referential 'See `## X` above' cross-reference lines and merge the duplicate sections (Example Usage into Usage, Quick Check into Audit-Ready Commands).

Delete or drastically trim generic governance sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements, Response Template, Input Validation) that add no skill-specific value — keep only Error Handling's concrete fallback guidance.

Fix the placeholder path in Example Usage ('cd 20260318/scientific-skills/...'), and either link references/guidelines.md by name with real content in it or remove the reference directory.

DimensionReasoningScore

Conciseness

The body has ~19 sections for a simple single-script skill, with several padded or redundant blocks: template filler like "See `## Features` above for related details", a Quick Check section duplicating Audit-Ready Commands, an Example Usage section duplicating Usage, and generic governance boilerplate (Lifecycle Status, Response Template, Output Requirements, Evaluation Criteria). This matches 'noticeably verbose; several unnecessary explanations or padded sections' rather than score 3, because the padding is extensive, not incidental.

2 / 5

Actionability

The Usage section provides copy-paste-ready commands ("python scripts/main.py --concept \"thrombosis\""), a complete parameter table, and a concrete output JSON schema, which is mostly executable guidance. It falls short of score 5 because the 'Example run plan' is abstract and the Example Usage section uses a broken placeholder path ("cd 20260318/scientific-skills/Evidence Insight/concept-explainer") that contradicts its own 'avoid placeholder paths' claim.

4 / 5

Workflow Clarity

The Workflow section lists a real sequence with a stop-early check and a fallback path, but the steps are generic governance language ("use the packaged script path or the documented reasoning path") rather than concrete checkpoints, and the duplicated sections (Example Usage vs Usage, Quick Check vs Audit-Ready Commands) obscure the actual sequence. This fits 'steps listed but validation gaps; checkpoints missing or implicit' rather than score 4's 'clear sequence with most checkpoints present'.

3 / 5

Progressive Disclosure

The bundle has one script (scripts/main.py) and one reference (references/guidelines.md), but the body never names guidelines.md — it only says "Reference material available in `references/`" — and that file itself contains just three contentless bullet lines with no link back. This matches 'references present but not clearly signaled' rather than score 4's 'references mostly clear'.

3 / 5

Total

12

/

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 states a clear, concrete purpose in the correct third-person voice, but it is incomplete: it answers only 'what this does' with no 'when to use it' guidance. Adding a 'Use when...' clause with natural trigger terms (e.g., patient education, explaining a diagnosis, health literacy) would materially improve completeness and trigger quality.

Suggestions

Append an explicit trigger clause, e.g., "Use when the user asks to simplify, explain, or teach a medical concept to patients, students, or non-experts."

Add natural synonym keywords users would say, such as 'patient education', 'plain language', 'health literacy', and 'explain a diagnosis'.

Optionally enumerate the concrete capabilities (multiple explanation levels, audience adaptation, key-point summaries) to strengthen specificity.

DimensionReasoningScore

Specificity

"Uses analogies to explain complex medical concepts" names the domain and one concrete action (analogy-based explanation), matching the 'domain plus 1-2 concrete actions, not comprehensive' anchor. It is not score 4 because only a single action is listed, and not score 2 because 'use analogies to explain' is a concrete action rather than generic filler.

3 / 5

Completeness

The 'what' is clearly stated (explains complex medical concepts using analogies in accessible terms) but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It does not reach score 4 because 'when' is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

Some relevant natural keywords are present ("analogies", "explain", "medical concepts", "accessible terms"), but common variations users would actually say are missing (e.g., "patient education", "simplify", "explain to a patient", "health literacy"), matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The medical-concepts-plus-analogies framing is a clear niche that would rarely fire for unrelated skills, but the description sits between anchors: it lacks the explicit trigger phrases of the score-5 example and has minor overlap risk with sibling patient-education or medical-explanation skills, so score 4 is the best fit.

4 / 5

Total

13

/

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.

Validation — 15 / 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

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/concept-explainer/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.