CtrlK
BlogDocsLog inGet started
Tessl Logo

moa-explainer

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

52

Quality

57%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

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

47%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body has a clear, well-checkpointed workflow and a genuine one-level-deep reference, but it is padded with generic templated boilerplate and lacks a concrete example of its actual output (animation storyboard / lay explanation), dragging down conciseness and actionability.

Suggestions

Remove the generic boilerplate that adds no task-specific value (Security Checklist, Lifecycle Status, Risk Assessment table, Evaluation Criteria) or move it into a reference file, keeping SKILL.md lean.

Replace the empty '## Example' stub with a real worked example showing the animation storyboard and simplified lay explanation for the PD-1 inhibitor case.

Add a concrete runnable invocation with real parameter values (e.g. 'python scripts/main.py --drug pembrolizumab --target PD-1 --disease melanoma --audience patient') and the expected output shape.

DimensionReasoningScore

Conciseness

Large portions are templated boilerplate Claude already knows — a generic 9-item Security Checklist, Lifecycle Status 'Draft', 'Known Issues: None', 'Planned Improvements: Performance optimization', and meta sentences like 'Repository baseline for current packaged skills' — padded with unnecessary context, matching the 'verbose; explains concepts Claude knows' anchor rather than the mostly-efficient 2.

1 / 3

Actionability

Provides concrete executable commands ('python -m py_compile scripts/main.py', 'python scripts/main.py --help') and a real script path, but gives no concrete example of the actual deliverable — the '## Example' section is a single label ('PD-1 inhibitor mechanism for patient education') with no storyboard/explanation output, so key details are missing.

2 / 3

Workflow Clarity

The numbered Workflow has explicit validation checkpoints ('stop early if the task would require unsupported assumptions') and a fallback loop ('If execution fails or inputs are incomplete, switch to the fallback path'), with dedicated Quick Check and Audit-Ready Commands sections, matching the 'clear sequence with explicit validation steps; feedback loops' anchor.

3 / 3

Progressive Disclosure

The referenced bundle is real and one-level-deep (references/audit-reference.md is clearly linked and exists, scripts/main.py is signaled), but the ~189-line body itself is inline-heavy — Risk Assessment, Security Checklist, Lifecycle, Evaluation Criteria boilerplate that should live in separate files — so it is 'some structure but content that should be separate is inline' rather than a lean overview pointing outward.

2 / 3

Total

8

/

12

Passed

Description

67%

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 specific and occupies a clear niche, but it omits any explicit 'when to use' trigger guidance and is missing the most common natural phrasing ('MoA' / 'mechanism of action'), which caps completeness and trigger-term quality at 2.

Suggestions

Append an explicit trigger clause, e.g. 'Use when explaining a drug's mechanism of action (MoA), producing visual/MoA animations, or creating patient- or lay-friendly drug explanations.'

Include the common natural terms users actually say — 'mechanism of action', 'MoA', 'drug animation', 'patient-friendly explanation' — alongside 'drug mechanisms'.

Clarify the audience/output pairings (e.g. animation storyboard vs. lay explanation) so the trigger distinguishes this from generic medical-writing skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Generate 3D animation scripts and lay explanations' — for a specific domain (drug mechanisms), matching the 'lists multiple specific concrete actions' anchor rather than the partial coverage of a 2.

3 / 3

Completeness

Clearly states what the skill does but lacks any 'Use when...' trigger clause; per the judging guidelines a missing explicit trigger caps completeness at 2 ('has what, but when is missing or only implied').

2 / 3

Trigger Term Quality

Uses 'drug mechanisms' and '3D animation scripts', which are relevant but misses the canonical natural phrasings users would say ('MoA', 'mechanism of action'), so it lands at 'some relevant keywords but missing common variations' rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

Targets a narrow, distinct niche (drug mechanism visualization plus lay explanation) unlikely to overlap with other skills, matching the 'clear niche with distinct triggers' anchor rather than the broad-overlap 2.

3 / 3

Total

10

/

12

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.

Validation15 / 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
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.