CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

iacuc-protocol-drafter

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

Quality

64%

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

Quality

Content

56%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 content is genuinely actionable, with a complete input JSON schema, a parameter table, and verifiable validation commands, and its bundle references are real and one level deep. However, it is heavily padded with generic governance boilerplate, contains duplicated and contradictory sections, and buries the IACUC-specific guidance in meta-text.

Suggestions

Remove the generic boilerplate sections ('Risk Assessment', 'Security Checklist', 'Evaluation Criteria', 'Lifecycle Status', 'Response Template') and the 'See ## X above' cross-references; move any needed audit detail into references/audit-reference.md instead of duplicating it inline.

Resolve the contradiction between 'Python: 3.10+' (Dependencies) and 'Python 3.8+' (Requirements), and unify the script path used across Example Usage and Usage so commands are consistent.

Lead with the IACUC-specific workflow (input JSON with the 3Rs justification structure, generated protocol text, template options) and cut the generic workflow boilerplate to shorten the body.

DimensionReasoningScore

Conciseness

The body is padded with meta-boilerplate sections ('Risk Assessment', 'Security Checklist', 'Evaluation Criteria', 'Lifecycle Status', 'Output Requirements') and self-referential cross-references like 'See `## Prerequisites` above' and 'See `## Usage` above' that point to sections appearing later in the document. It also duplicates and contradicts dependency info ('Python: 3.10+' in Dependencies vs 'Python 3.8+' in Requirements). Matches the anchor 'Noticeably verbose; several unnecessary explanations or padded sections'; not 1 because it never explains basic concepts Claude already knows.

2 / 5

Actionability

Concrete executable guidance is present: 'python scripts/main.py --help', a full parameter table (--input, --output, --template, --format), a complete copy-paste-ready input JSON schema, and stdin/stdout usage commands. Minor gaps: template and format option values are named but not enumerated, and command paths are inconsistent across sections. Matches the anchor 'Mostly executable guidance; concrete code or commands with minor gaps'.

4 / 5

Workflow Clarity

A clear sequence exists (confirm objective and inputs, validate scope, run the packaged script, review the structured output) with validation checkpoints ('python -m py_compile scripts/main.py' Quick Check, --help audit commands) and an explicit error-recovery fallback path in the Error Handling section. Not 5 because the workflow steps are generic boilerplate rather than IACUC-specific, and duplicated sections muddy the sequence. Matches the anchor 'Clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

Referenced bundle files are real and one level deep: 'scripts/main.py' and '[references/audit-reference.md](references/audit-reference.md)' are clearly signaled with a one-line description. However, audit-reference.md largely duplicates commands already inlined in SKILL.md, and large blocks of audit/security content sit inline in the body rather than in separate reference files. Matches the anchor 'Some structure but could be better organized'.

3 / 5

Total

13

/

20

Passed

Description

57%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 accurate and sits in a distinct niche, with a clear statement of what the skill does. Its main weaknesses are the missing 'Use when...' trigger clause and limited coverage of concrete capabilities and natural synonym terms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to draft or revise an IACUC protocol application, animal use protocol, or 3Rs justification section.'

Name the concrete workflow actions: generate IACUC application text from structured input (JSON), covering Replacement, Reduction, and Refinement justification sections.

Include natural synonyms users say, such as 'animal use protocol (AUP)' and 'animal ethics approval', to broaden trigger coverage.

DimensionReasoningScore

Specificity

The phrase 'Draft IACUC protocol applications with focus on the 3Rs principles justification' names the domain and one concrete action, but does not list several specific actions or cover the actual workflow (JSON input, generated protocol text, templates). Matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'.

3 / 5

Completeness

The description gives a clear 'what' ('Draft IACUC protocol applications... 3Rs principles justification') but contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

'IACUC', 'protocol', and '3Rs principles' are natural domain keywords a user would say, but common variations and synonyms are missing ('animal use protocol', 'AUP', 'animal ethics application'). Matches the anchor 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

'IACUC protocol' combined with '3Rs principles justification' is a clear niche with distinct, domain-specific triggers; minimal risk of firing for the wrong skill. Matches the anchor 'Clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

14

/

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/iacuc-protocol-drafter/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.