CtrlK
BlogDocsLog inGet started
Tessl Logo

iacuc-protocol-drafter

Draft IACUC protocol applications with focus on the 3Rs principles justification.

44

Quality

46%

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/iacuc-protocol-drafter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%

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

The skill carries genuine actionable material (parameters, input schema, templates) and a valid one-level reference, but it is buried under large amounts of redundant template boilerplate that hurts token efficiency. Trimming the filler and tightening the workflow would substantially improve it.

Suggestions

Remove or relocate the generic Risk Assessment, Security Checklist, Evaluation Criteria, and Lifecycle Status sections; they add no skill-specific value and consume context.

Eliminate duplicate command listings and the dangling "See ## X above" cross-references; keep one Quick Check / Audit-Ready Commands block.

Make the Workflow steps concrete with actual validation commands (e.g. run py_compile before and after edits) instead of abstract guard phrases.

Resolve the contradictory Python version (Dependencies says 3.10+, Requirements says 3.8+) and consolidate dependency statements into one place.

DimensionReasoningScore

Conciseness

The ~240-line body is heavily padded with redundant boilerplate (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status tables) plus repeated command listings and cross-references to "above" sections that do not exist, none of which earn their tokens.

1 / 3

Actionability

It provides a concrete Parameters table, a complete Input Format JSON example, and executable Usage commands, but these are interleaved with abstract process guidance ("confirm the source files", "choose the packaged workflow") that dilutes the actionable content.

2 / 3

Workflow Clarity

A 5-step Workflow plus Error Handling and Input Validation sections are sequenced, but the checkpoints are abstract/implicit ("stop early", "switch to fallback") rather than concrete validation steps.

2 / 3

Progressive Disclosure

There is one real, well-signaled one-level reference (references/audit-reference.md) and a real scripts/main.py, but the body itself is overstuffed with inline content that should be split out or removed, so the structure is only partially organized.

2 / 3

Total

7

/

12

Passed

Description

57%

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 clear and distinctive within a well-defined niche, but it is a single-action statement lacking an explicit trigger clause. Adding a "Use when..." sentence and a few more natural trigger terms would raise it.

Suggestions

Add an explicit trigger clause, e.g. "Use when drafting IACUC protocol applications or when the user mentions 3Rs justification, animal study protocols, or IACUC submissions."

Broaden trigger terms to include natural variations like "animal research", "animal care", and "IACUC application".

Optionally enumerate concrete actions (draft justification, generate application text, structure the 3Rs sections) to lift specificity to 3.

DimensionReasoningScore

Specificity

Names a concrete domain and one action ("Draft IACUC protocol applications") plus a focus ("3Rs principles justification"), but it lists a single action rather than multiple specific concrete actions.

2 / 3

Completeness

It states what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

"IACUC protocol", "3Rs principles", and "justification" are natural domain terms, but common variations a user might say (e.g. "animal research protocol", "IACUC submission") are missing.

2 / 3

Distinctiveness Conflict Risk

The IACUC/3Rs niche is highly specific with distinct triggers and is unlikely to fire for unrelated skills.

3 / 3

Total

9

/

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.