CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

baseline-extraction-for-clinical-trials

Extracts clinical trial baseline data (study, region, participants, etc.) from article text or PMID. Checks PubMed for metadata; always falls back to LLM extraction for full details.

Quality

63%

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/baseline-extraction-for-clinical-trials/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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 two-step PubMed-then-LLM workflow is well sequenced with status-based checkpoints and a valid one-level-deep reference, but the body is padded with boilerplate sections, references a script missing from the bundle, and is visibly truncated mid-instruction in the PDF helper section. Tightening the file and fixing the broken script reference would materially improve it.

Suggestions

Fix the bundle mismatch: either add scripts/baseline_extractor.py or rewrite Step 1 to use the existing extract_pdf.py / a real PubMed-check command.

Delete the generic 'Key Features', 'Dependencies', and 'Implementation Details' filler sections and repair the garbled first 'When to Use' bullet; they restate the description without adding guidance.

Complete the truncated 'PDF Text Extraction' section (it ends mid-sentence at 'before assessment:') and replace the dated cd '20260316/scientific-skills/...' path with the skill's own directory.

DimensionReasoningScore

Conciseness

Several padded sections add no actionable information: 'When to Use' contains garbled restatements of the description ("when you need extracts clinical trial baseline data ... in a reproducible workflow"), 'Key Features' repeats the description verbatim, and 'Dependencies'/'Implementation Details' offer generic packaging boilerplate ("Reference guidance: references/ contains supporting rules, prompts, or checklists", "See ## Workflow above for related details"). This matches 'noticeably verbose; several unnecessary explanations or padded sections', though it stops short of the score-1 level of explaining concepts Claude already knows.

2 / 5

Actionability

There is concrete guidance — a subprocess call for the PubMed check with explicit status-based handling, a link to the extraction schema, and a specified JSON output format — but key pieces are incomplete: 'scripts/baseline_extractor.py' does not exist in the bundle (only extract_pdf.py), the Example Usage cds into a dated local path ('20260316/scientific-skills/...') that won't exist elsewhere, and the 'PDF Text Extraction' section is truncated mid-sentence ('before assessment:'). This lands on the 'some concrete guidance but incomplete ... missing key details' anchor rather than 4, whose code/commands should be mostly executable as written.

3 / 5

Workflow Clarity

The hybrid workflow is clearly sequenced with an explicit validation checkpoint: Step 1 checks PubMed and branches on status ('If status is "success": Stop here ... If "not_found", "incomplete", or "error" ... Proceed to Step 2'), and Step 2 includes an anti-hallucination constraint ('If a field is not mentioned in the text, set it to null'). It falls short of 5 because there is no recovery loop for a failed extraction (e.g., retry or escalate) and the truncated helper section leaves the PDF path unfinished. No destructive/batch cap applies.

4 / 5

Progressive Disclosure

Scored against the actual bundle: references/extraction_schema.md exists, is one level deep, and is clearly signaled with a markdown link — good — but the body's primary script reference 'scripts/baseline_extractor.py' does not exist in scripts/ (which contains only extract_pdf.py), and generic boilerplate that belongs in no file at all is inlined in SKILL.md. A nonexistent referenced script plus inlined filler is more than the 'minor organization gaps' of 4, fitting 'some structure but could be better organized'.

3 / 5

Total

12

/

20

Passed

Description

62%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 specific, third-person description that clearly conveys the hybrid PubMed-check + LLM-fallback approach for a well-defined niche. Its main weaknesses are the complete absence of 'when to use' trigger guidance and sparse natural-language synonyms for the domain.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when extracting baseline characteristics or the baseline table from a clinical trial article, RCT report, or PubMed record.'

Include natural synonyms users would actually say: RCT, randomized controlled trial, baseline characteristics, baseline table, and PDF input.

Replace the trailing 'etc.' with the full field list (sex, age, intervention, comparator, outcome, study design) or a concrete count ('10 baseline fields') to strengthen specificity.

DimensionReasoningScore

Specificity

Lists several specific actions — "Extracts clinical trial baseline data (study, region, participants, etc.)", "Checks PubMed for metadata", "falls back to LLM extraction for full details" — with an enumerated field list. It falls below the comprehensive 5 anchor because the field enumeration trails off with "etc." and no other capabilities (e.g., PDF input handling) are named.

4 / 5

Completeness

The 'what' is clearly stated (extract baseline data via PubMed check plus LLM fallback), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description — the 'when' is entirely absent, matching the anchor for a clear 'what' with missing 'when'. Per the guidelines, a missing 'Use when...' clause caps completeness at 3; it cannot be 4 or 5 without explicit trigger phrases.

3 / 5

Trigger Term Quality

Relevant domain keywords are present ("clinical trial baseline data", "article text", "PMID", "PubMed") but common natural variations are missing — users would likely say "RCT", "randomized controlled trial", "baseline characteristics/table", or mention PDFs. This matches the 'some relevant keywords but missing common variations or synonyms' anchor, not 4, which requires good coverage with only a few terms missing.

3 / 5

Distinctiveness Conflict Risk

"clinical trial baseline data ... from article text or PMID. Checks PubMed for metadata" carves out a clear niche (clinical-trial baseline-table extraction from biomedical articles) with distinct triggers, so conflict risk with generic data-extraction skills is minimal. It clearly fits the 'clear niche with distinct triggers' anchor rather than 4, whose residual overlap risk would require broader wording.

5 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Data Analysis/baseline-extraction-for-clinical-trials/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.