CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clinical-data-cleaner

Use when cleaning clinical trial data, preparing data for FDA/EMA submission, standardizing SDTM datasets, handling missing values in clinical studies, detecting outliers in lab results, or converting raw CRF data to CDISC format. Cleans and standardizes clinical trial data fo...

Quality

77%

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/clinical-data-cleaner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 domain half of this skill is excellent — verified, copy-paste-ready code against a real script with well-signaled one-level-deep references. The body is dragged down by a large tail of generic, non-domain agent-contract boilerplate, a nonsensical audit command, an irrelevant study-design checklist, and an abstract workflow that never sequences the actual cleaning pipeline.

Suggestions

Delete the ~80 lines of generic agent-contract boilerplate (Output Requirements, Error Handling, Input Validation, Response Template, When Not to Use, Required Inputs, Output Contract, Failure Handling, User Checkpoints, Quick Validation) and the duplicated Quick Check/Audit-Ready Commands section — they are non-domain, largely duplicate each other, and consume context without teaching the cleaning task.

Rewrite the Workflow section as the concrete cleaning pipeline with validation checkpoints, e.g. load → `validate_domain()` (stop and report missing required fields) → `handle_missing_values()` → `detect_outliers()` → `standardize_dates()` → `save_report()`, with a concrete validation command (e.g. re-run `validate_domain` on cleaned output) before declaring completion.

Remove the broken audit command (`--input "Audit validation sample with explicit symptoms..."` passes prose as a file path) and the Pre-Cleaning checklist items about IACUC approval, statistical power, and randomization, which are study-design concerns outside this skill's data-cleaning scope.

DimensionReasoningScore

Conciseness

The core capability sections are lean and code-first, but the body carries substantial padding: ~80 lines of generic agent-contract boilerplate ("Output Requirements", "Error Handling", "Input Validation", "Response Template", "When Not to Use", "Required Inputs", "Output Contract", "Failure Handling", "User Checkpoints", "Quick Validation" — three of which duplicate each other), a "When to Use" bullet that mechanically repeats the frontmatter description inside a broken sentence ("Use this skill when the task needs Use when cleaning clinical trial data..."), a duplicated py_compile command in both "Quick Check" and "Audit-Ready Commands", and an irrelevant study-design checklist ("IACUC approval obtained", "Sample size adequately powered", "Randomization method documented") that is not data cleaning. This matches anchor 2: "Noticeably verbose; several unnecessary explanations or padded sections".

2 / 5

Actionability

The Quick Start, per-capability snippets, Complete Pipeline, CLI examples, threshold table, and required-field lists are concrete and were verified executable against scripts/main.py (class name, all methods, and CLI flags match). Not 5 because one example is broken as written — `python scripts/main.py --input "Audit validation sample with explicit symptoms, history, assessment, and next-step plan."` passes a prose string as an input file path — a minor gap consistent with anchor 4.

4 / 5

Workflow Clarity

The "Workflow" section lists six steps but they are a generic consulting template ("Confirm the user objective", "Return a structured result") rather than the actual cleaning pipeline (load → validate_domain → handle_missing_values → detect_outliers → standardize_dates → save_report, which only appears implicitly as the capabilities list). The skill batch-processes datasets and overwrites output files, yet validation is abstract prose with no concrete in-flow checkpoint, so per the rubric cap workflow_clarity cannot exceed 3.

3 / 5

Progressive Disclosure

Good structure: SKILL.md is an overview with quick-start and capability summaries, and details are split into five real, verified, one-level-deep reference files (common-patterns.md, troubleshooting.md, sdtm_ig_guide.md, domain_specs.json, outlier_thresholds.json) plus a working script, each clearly signaled with links and content summaries. Not 5 because the inlined generic contract sections are content that belongs in no file at all, and the 262-line body is heavier than a clean overview should be.

4 / 5

Total

13

/

20

Passed

Description

91%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.

A strong, highly specific description with explicit trigger guidance and natural domain vocabulary. Its one real defect is that the file's description field is physically truncated mid-word ("...clinical trial data fo..."), cutting the 'what' statement short and likely clipping the regulatory-compliance/audit-trail purpose.

Suggestions

Complete the truncated final sentence — the description ends mid-word ("Cleans and standardizes clinical trial data fo..."), cutting off the 'what' statement and the regulatory-compliance/audit-trail purpose it was presumably conveying.

Once restored, verify the what-clause complements the trigger list rather than restating it (e.g., mention audit trails/SDTM compliance outputs) so both halves of the description carry distinct information.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — "cleaning clinical trial data", "standardizing SDTM datasets", "handling missing values in clinical studies", "detecting outliers in lab results", "converting raw CRF data to CDISC format" — comprehensively covering the skill's scope, matching the 5 anchor ("Lists multiple specific concrete actions; comprehensive coverage"). Not 4 because the action coverage is not merely "several" with gaps; it spans validation, missing values, outliers, dates, and regulatory formatting.

5 / 5

Completeness

The 'when' is explicitly and concretely answered by the "Use when cleaning clinical trial data... or converting raw CRF data to CDISC format" clause, but the 'what' sentence "Cleans and standardizes clinical trial data fo..." is literally truncated mid-word in the file, leaving the capability statement incomplete. It sits above anchor 4 ('when could be more explicit' — here the when is fully explicit) but the damaged what-clause keeps it from a clean 5.

4 / 5

Trigger Term Quality

Natural domain keywords are comprehensively covered, including synonyms: "clinical trial data" and "clinical studies", "FDA/EMA submission", "SDTM datasets", "outliers in lab results", "CRF data", "CDISC". A user needing this skill would naturally say these exact phrases; no common variants are missing.

5 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche with distinct triggers — SDTM, CDISC, CRF, FDA/EMA submission are unambiguous clinical-regulatory terms with minimal overlap risk against general data-cleaning skills.

5 / 5

Total

19

/

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/clinical-data-cleaner/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.