CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

protocol-deviation-classifier

Classify clinical trial protocol deviations as major or minor based on ICH E6/GCP guidelines. Three-impact-dimension assessment (safety, data integrity, scientific validity), confidence scoring, and regulatory compliance reporting with recommended actions.

Quality

67%

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/Data Analysis/protocol-deviation-classifier/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 classification content is genuinely actionable — verified CLI commands, explicit classification rules, and concrete I/O formats — but it is buried in a monolithic, heavily padded body full of generic boilerplate, with inconsistent commands, a misreferenced workflow step, and a bundle reference file that is never surfaced.

Suggestions

Delete the generic boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, and the seven overlapping output/error/validation contract sections), collapsing them into one concise error-handling and scope block.

Move the classification-standards tables and full JSON format specifications into a reference file (e.g. references/classification-standards.md) linked from a short overview, and link the existing references/runtime_checklist.md, which is currently never mentioned.

Fix correctness inconsistencies: replace the invalid "python scripts/main.py --input ... --format json" audit command with a real subcommand invocation, remove or correct "pip install -r requirements.txt" (the script is stdlib-only, no requirements.txt exists), and correct Workflow step 2's "tables above" to point to the tables below.

Add an output-verification/fix-retry feedback step for batch classification so the batch workflow can exceed the current workflow-clarity cap of 3.

DimensionReasoningScore

Conciseness

Beyond the useful core (classification tables, rules, CLI), the body carries numerous padded sections of generic boilerplate: "Risk Assessment", "Security Checklist", "Evaluation Criteria / Success Metrics", "Lifecycle Status" (including a time-sensitive "Next Review Date: 2026-03-06"), plus seven overlapping generic contract sections ("Output Requirements", "Error Handling", "Input Validation", "Response Template", "Inputs to Collect", "Output Contract", "Validation and Safety Rules"). This is noticeably verbose with several unnecessary padded sections — not score 1, because the core classification content itself is dense and does not explain concepts Claude already knows.

2 / 5

Actionability

Quotes: "python scripts/main.py classify --description \"Subject visit delayed by 2 days\" --type \"Visit Window\"" and "python scripts/main.py batch --input deviations.json --output report.json" — verified against the script's argparse (classify/batch/report/interactive/demo subcommands) and mostly executable, with full JSON input/output formats and a concrete Python API example. Not score 5: the "Audit-Ready Commands" invocation "python scripts/main.py --input ... --format json" does not match the actual subcommand-based CLI, and "Prerequisites: pip install -r requirements.txt" contradicts "No third-party dependencies (pure Python standard library implementation)" with no requirements.txt in the bundle — minor but real gaps in executability.

4 / 5

Workflow Clarity

The 5-step workflow ("Receive deviation" → "Assess impact dimensions" → "Apply classification rules" → "Generate output" → "Fallback") is clearly sequenced with an input checkpoint ("If the description is vague, request clarification before proceeding") and a fallback flagging manual QA review. However, step 2 misreferences "the classification standards tables above" when the tables appear below the workflow, and the batch path ("batch --input deviations.json --output report.json") has no validate-output/fix-retry feedback loop — the judging guidelines cap batch workflows without feedback loops at 3.

3 / 5

Progressive Disclosure

The body is a ~350-line monolith: the two large classification-standards tables, full JSON format specs, and ~10 generic administrative sections are all inlined, content that clearly belongs in separate reference files. The one bundle reference (references/runtime_checklist.md) is never mentioned or linked anywhere in the body (verified by grep), so references are effectively buried. This matches the anchor for content inlined that belongs in separate files plus buried references; it is not score 3 because structure, while present in section headers, provides no navigation to the existing bundle materials at all.

2 / 5

Total

11

/

20

Passed

Description

75%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 specific, third-person, and covers the tool's capabilities comprehensively, with strong domain distinctiveness. Its main weakness is the complete absence of 'when to use' trigger guidance, plus a few missing natural synonyms like 'protocol violation'.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when reviewing clinical trial monitoring reports, audit findings, or deviation logs that must be graded as major or minor deviations under ICH E6/GCP.'

Include natural synonyms and variations users would actually say, such as 'protocol violation', 'deviation report', and 'risk-based quality management', to improve trigger term coverage.

DimensionReasoningScore

Specificity

Quotes: "Classify clinical trial protocol deviations as major or minor based on ICH E6/GCP guidelines", "Three-impact-dimension assessment (safety, data integrity, scientific validity)", "confidence scoring", "regulatory compliance reporting with recommended actions". These are multiple specific, concrete actions with comprehensive coverage of the tool's capabilities, matching the anchor for comprehensive coverage rather than the level-4 anchor (which expects minor gaps in coverage).

5 / 5

Completeness

The 'what' is clearly stated (classify deviations as major/minor with three-dimension assessment, confidence scoring, and compliance reporting), but there is no "Use when..." clause or any equivalent explicit trigger guidance — the judging guidelines explicitly cap completeness at 3 in that case, matching the 'clear what, missing when' anchor.

3 / 5

Trigger Term Quality

Quotes: "clinical trial protocol deviations", "major or minor", "ICH E6/GCP", "safety, data integrity, scientific validity", "regulatory compliance" — natural phrases a clinical trial professional would say. Not score 5 because common synonyms such as "protocol violation" and "deviation report" are absent, leaving a few natural terms missing per the good-coverage anchor.

4 / 5

Distinctiveness Conflict Risk

Quotes: "clinical trial protocol deviations", "ICH E6/GCP guidelines", "major or minor" — a clear niche with distinct domain-specific triggers and minimal overlap risk with generic skills. It is not score 4 because no closely-related skill overlap is apparent; adjacent domains (e.g., adverse-event coding) are separately handled.

5 / 5

Total

17

/

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/Data Analysis/protocol-deviation-classifier/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.