CtrlK
BlogDocsLog inGet started
Tessl Logo

literature-experiment-extract

Extract experimental models, experimental methods, and biomarker information from paper Markdown (typically produced by PDF-to-Markdown tools) when a user provides paper Markdown and needs a structured, evidence-backed summary (1 Markdown + 3 CSVs).

67

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, actionable skill body that properly externalizes detail into its bundle files and sequences the workflow clearly. Its main weakness is redundant, generic boilerplate that inflates token cost without adding skill-specific value.

Suggestions

State the four output filenames once (e.g., in a single Output Contract) and reference that section elsewhere instead of repeating the full list in Example Usage, Implementation Details, and Output Contract.

Replace the generic Required Inputs table — whose examples (PMID, PDF, DOCX) do not match this skill's paper-Markdown input — with the skill's actual required input (converted paper Markdown with optional page headers).

Tighten or remove the templated Failure Handling / User Checkpoints / Quick Validation sections, or make their checks skill-specific (e.g., 'verify CSV headers match the guide.md spec' rather than generic 'check core fields exist').

DimensionReasoningScore

Conciseness

Mostly efficient, but output filenames and naming are restated three times and several generic boilerplate sections (Required Inputs table with irrelevant examples like PMID/PDF/DOCX, Output Contract, Failure Handling, Quick Validation) read as templated padding that could be tightened.

3 / 5

Actionability

Provides concrete, executable guidance — exact output filenames with '{Paper Abbreviation}' placeholders, UTF-8 encoding, and clear pointers to references/guide.md and assets/template.md for rules and structure — with only minor gaps from deferring field definitions to the referenced files.

4 / 5

Workflow Clarity

Steps are clearly sequenced (open Markdown, extract page-by-page, follow guide/template, emit four fixed outputs) with Quick Validation checks and User Checkpoints present; validation is somewhat generic rather than skill-specific, leaving minor gaps.

4 / 5

Progressive Disclosure

Overview lives in SKILL.md while detailed extraction rules and the output template are correctly externalized to references/guide.md and assets/template.md — both real files referenced clearly and only one level deep, making navigation easy.

5 / 5

Total

16

/

20

Passed

Description

92%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, specific description that concretely states both the capability and its trigger conditions with minimal fluff. The only gap is slightly limited synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Extract experimental models, experimental methods, and biomarker information' and 'structured, evidence-backed summary (1 Markdown + 3 CSVs)' — giving comprehensive coverage of the domain.

5 / 5

Completeness

Clearly states what it does ('Extract experimental models, methods, and biomarker information...') and when to use it ('when a user provides paper Markdown and needs a structured, evidence-backed summary'), answering both with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Includes natural terms a user would say ('paper Markdown', 'PDF-to-Markdown', 'biomarker', 'summary') but misses common synonyms like 'research article', 'manuscript', or a file extension, so a few natural terms are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — extracting experiment entities from converted paper Markdown — with distinct triggers and minimal overlap risk against other 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.

Validation15 / 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
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.