CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clinical-study-info-extractor

Batch extracts and verifies structured information (PMID, title, abstract, methodology, results, etc.) from clinical research literature using PMIDs. Use when the user wants to extract details from specific PMIDs.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/clinical-study-info-extractor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 skill has a genuinely clear workflow with a real verification phase and a well-signaled one-level reference file, but it is wrapped in substantial templated padding and its Example Usage section contains non-functional guidance (a --help command the script does not support and a nonexistent CONFIG block). Tightening the boilerplate and fixing the executable examples would lift both conciseness and actionability.

Suggestions

Remove the templated filler sections (Key Features, When to Use boilerplate bullets, Dependencies meta-commentary, Implementation Details) that restate the description or give generic process advice — this would cut the body roughly in half and push conciseness toward 5.

Fix the non-functional executable guidance: replace 'python scripts/utils.py --help' (the script has no argparse and only runs a self-test) and the nonexistent 'in-file CONFIG block' with a real end-to-end invocation using sample PMIDs (e.g., importing normalize_pmids/fetch_pubmed_data/format_table and running the two-phase extraction).

Correct the broken cross-references so 'See ## Usage above' and 'See ## Workflow above' point to sections in the right direction (or reorder sections), improving navigability of the body.

DimensionReasoningScore

Conciseness

The core sections (Workflow, Usage, Quality Rules) are tight and efficient, but several sections are padded boilerplate: 'Scope-focused workflow aligned to: Batch extracts and verifies structured information...' restates the description verbatim, 'Use this skill when a evidence insight task needs a packaged method instead of ad-hoc freeform output' is generic filler, and 'Add pinned versions if this skill needs stricter environment control' is meta-commentary. This is 'mostly efficient but includes some unnecessary explanation'; not score 2 because the essential instructions carry no conceptual over-explanation, but clearly not 4 given ~40% of the body is templated redundancy.

3 / 5

Actionability

Concrete elements exist — the named functions (normalize_pmids, fetch_pubmed_data, format_table) are real, and references/extraction_rules.md exists — but key executable guidance is incomplete or wrong: the documented 'python scripts/utils.py --help' cannot work (the script has no argument parsing; running it executes a hardcoded self-test), and 'Edit the in-file CONFIG block' refers to a CONFIG block that does not exist in utils.py. No end-to-end example with actual PMID input is shown. This matches anchor 3 (some concrete guidance but incomplete, missing key details) rather than 4, whose commands should be mostly executable.

3 / 5

Workflow Clarity

A clear 5-step Workflow ('Input Normalization... Verification: Enforces quality rules... Output Formatting') and a 4-step Usage with an explicit two-phase extract-then-verify design backed by a verification checklist in references/extraction_rules.md. The batch-operation cap does not apply since a validation step is present. Missing only error-recovery guidance (the script returns error JSON on fetch failure but the doc never says what to do with it), which keeps it at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

Good structure against the actual bundle: the single reference (references/extraction_rules.md) is real, one level deep, and clearly signaled ('See references/extraction_rules.md for detailed extraction logic and constraints'), and scripts/utils.py is correctly referenced. Minor gaps: broken internal cross-references ('See `## Usage` above' and 'See `## Workflow` above' both point to sections that appear below those pointers) and the templated sections dilute navigation, preventing a 5.

4 / 5

Total

14

/

20

Passed

Description

78%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 focused, third-person description that clearly states both what the skill does and when to use it, with strong PMID-centric trigger terms. Weaknesses are minor: the trigger list covers only one phrasing (no 'PubMed', 'papers', or 'literature' variations) and the what-clause omits the deliverable (consolidated Markdown table).

DimensionReasoningScore

Specificity

Lists several concrete actions and output fields — 'Batch extracts and verifies structured information (PMID, title, abstract, methodology, results, etc.)' — anchored to a named domain (clinical research literature). Minor gaps: does not mention the consolidated Markdown table output or the Chinese-language requirement, so coverage is not comprehensive enough for a 5.

4 / 5

Completeness

Explicitly answers both: what ('Batch extracts and verifies structured information... from clinical research literature using PMIDs') and when ('Use when the user wants to extract details from specific PMIDs'). The 'when' clause is a single narrow trigger though; it does not cover related cases (batch processing, literature review tables), so it fits anchor 4 ('when' could be more explicit or specific) better than anchor 5's multiple concrete trigger phrases.

4 / 5

Trigger Term Quality

Strong natural keywords: 'PMID', 'clinical research literature', 'extract details from specific PMIDs'. Missing common variations and synonyms a user might say — 'PubMed', 'papers', 'articles', 'literature lookup' — which keeps it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche — PMID-keyed structured extraction from clinical literature via the PubMed API — with distinct triggers ('PMIDs') that few other skills would share, giving minimal conflict risk.

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/Evidence Insight/clinical-study-info-extractor/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.