CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moa-explainer

Generate 3D animation scripts and lay explanations for drug mechanisms.

Quality

61%

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/Academic Writing/moa-explainer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 well-structured with a real, runnable script and clear fallback/error-handling paths, but it is padded with generic template sections and repeated commands that waste tokens. Its biggest functional gap is the absence of a real execution example showing the script invoked with actual parameter values. Trimming boilerplate and adding one concrete end-to-end example would substantially raise quality.

Suggestions

Cut the redundant boilerplate: collapse "Quick Check" and "Audit-Ready Commands" into the example section, merge "Dependencies" with "Prerequisites", and drop or drastically shorten the generic Risk Assessment, Security Checklist, Evaluation Criteria, and Lifecycle Status sections that carry no domain-specific guidance.

Add a real invocation example with concrete values, e.g., `python scripts/main.py --drug pembrolizumab --target PD-1 --mechanism "Blocks PD-1 binding to PD-L1" --type explanation`, alongside a sample of the expected output.

Move detail that must be kept (e.g., audit commands, fallback boundaries) into references/audit-reference.md instead of duplicating it in both the body and the reference file, and remove the time-sensitive "Next Review Date".

DimensionReasoningScore

Conciseness

The body is noticeably verbose with multiple padded template sections ("Key Features", "Implementation Details", "Risk Assessment", "Security Checklist", "Lifecycle Status", "Output Requirements") that restate generic process boilerplate rather than domain guidance. The same two commands (py_compile and --help) are repeated across "Example Usage", "Quick Check", and "Audit-Ready Commands", and "Dependencies"/"Prerequisites" duplicate each other; a stale review date (2026-03-06) adds time-sensitive clutter. It is not score 1 because it never explains concepts Claude already knows, and not score 3 because the redundancy goes beyond a few trimmable sentences.

2 / 5

Actionability

The body provides real, executable verification commands ("python -m py_compile scripts/main.py", "python scripts/main.py --help") and a real script path, but never demonstrates an actual task invocation with parameter values (e.g., running main.py with --drug/--mechanism/--target). The "Example" section is a single phrase ("PD-1 inhibitor mechanism for patient education") with no concrete input-to-output case. This matches anchor 3 — some concrete guidance but missing key details — rather than 4, because the reader cannot execute the core task from the body alone.

3 / 5

Workflow Clarity

The Workflow section lists a clear 5-step sequence including a fallback path ("If execution fails or inputs are incomplete, switch to the fallback path and state exactly what blocked full completion"), supported by an explicit pre-execution checkpoint (py_compile in "Quick Check") and an Error Handling section with a feedback path. It is not score 5 because the validation commands live in separate sections rather than being woven into the workflow steps and there is no output-validation example; it is above score 3 because checkpoints and an error-recovery loop are explicitly present. The skill is non-destructive, so the validation cap does not apply.

4 / 5

Progressive Disclosure

The bundle structure is sound: a single reference (references/audit-reference.md) is clearly signaled as a proper markdown link in a "References" section, is one level deep, and exists on disk, as does the referenced scripts/main.py. It is not score 5 because the reference largely duplicates commands already in the body rather than moving detail out of SKILL.md, and bulky boilerplate (risk tables, checklists) remains inlined. It is above score 3 because navigation is easy and all referenced paths are real and shallow.

4 / 5

Total

13

/

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 is concise, third-person, and states a specific dual capability, but it omits any explicit "Use when..." trigger guidance and lacks the natural synonyms (mechanism of action, MoA, patient education) that would help users and Claude select it. It defines a distinct niche yet relies on a single sentence to carry both capability and triggering. Adding a trigger clause and synonym coverage would move it from adequate to strong.

Suggestions

Add an explicit trigger clause, e.g., "Use when asked to explain how a drug works, its mechanism of action (MoA), or when creating patient-friendly or training materials for a medication."

Include natural synonyms and audience terms such as "mechanism of action", "MoA", "drug explanation", and "patient education" so the skill matches how users actually phrase these requests.

Optionally enumerate the concrete outputs (animation storyboard, voiceover script, key visual concepts) to round out capability coverage beyond the current two actions.

DimensionReasoningScore

Specificity

The description names the domain ("drug mechanisms") and exactly two concrete actions ("Generate 3D animation scripts", "lay explanations"), matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not score 4 because other real capabilities of the skill (storyboards, voiceover scripts, visual concepts) are unmentioned, and not score 2 because the actions stated are concrete rather than generic.

3 / 5

Completeness

The description has a clear, specific "what" ("Generate 3D animation scripts and lay explanations for drug mechanisms") but no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not score 2 because the "what" is concrete rather than vague, and cannot be 4 because "when" is entirely absent rather than just implicit or under-specified.

3 / 5

Trigger Term Quality

Phrases like "3D animation scripts", "lay explanations", and "drug mechanisms" are natural terms users would say, but common variations are missing — notably "mechanism of action", "MoA", and audience terms like "patient education" or "training". This matches anchor 3 (some relevant keywords, missing synonyms); it is above anchor 2 because the terms present are natural rather than generic, and below anchor 4 because the most common practitioner phrasing is absent.

3 / 5

Distinctiveness Conflict Risk

The combination of drug-mechanism animation and lay explanation carves a fairly distinct niche unlikely to trigger general document or coding skills. It is not score 5 because adjacent skills (medical writing, patient-education, or general animation skills) could still plausibly claim overlap given no distinct trigger phrases, and not score 3 because the domain is specific rather than broad.

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/Academic Writing/moa-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.