CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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).

Quality

70%

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/Evidence Insight/literature-experiment-extract/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 skill has a genuinely good progressive-disclosure structure (real, well-labeled reference and template files) and concrete, mostly executable output contracts. It is dragged down by substantial generic boilerplate sections and internal contradictions (direct-output vs. user checkpoints; Markdown-only input vs. PMID/PDF/CSV/DOCX inputs) that pad the body and blur the workflow.

Suggestions

Delete or rewrite the generic boilerplate sections (Required Inputs, Output Contract, Failure Handling, User Checkpoints, Input Validation, Quick Validation) with skill-specific content — the fixed outputs, input assumption, and validation checks are already stated elsewhere in the body or in references/guide.md.

Resolve the contradictory directives: pick one policy on user confirmation ("Output must be produced directly (no confirmation steps)" vs. "User Checkpoints"), and align the Required Inputs table with the Markdown-only input assumption instead of listing PMID/PDF/CSV/DOCX.

State the output file naming, encoding, and language rules once (in a single Outputs section or solely in references/guide.md) instead of repeating them across Example Usage, Implementation Details, and the guide, and add one worked example of a filled table row plus a definition of how the Paper Abbreviation is derived.

DimensionReasoningScore

Conciseness

Noticeably verbose with several padded sections: generic boilerplate ("Required Inputs" table listing "PMID, PDF, CSV, DOCX", "Output Contract: Structured result or target file aligned with this skill's objective", "Failure Handling", "User Checkpoints", "Input Validation", "Quick Validation") carries no skill-specific information, and the output filenames/encoding/language rules are repeated three times across "Example Usage → Steps", "Implementation Details → Paths and naming", and again in references/guide.md. This matches anchor 2 (several unnecessary explanations or padded sections) better than anchor 3.

2 / 5

Actionability

Mostly executable guidance: exact output paths ("outputs/{Paper Abbreviation}-experiment-summary.md", "-models.csv", "-methods.csv", "-biomarkers.csv"), explicit pointers to real bundle files with their purpose ("Extraction rules and evidence requirements: references/guide.md", "Output template: assets/template.md"), and a concrete extraction sequence. Minor gaps keep it below anchor 5: no worked example of a filled output row, and how the "Paper Abbreviation" is derived is never specified.

4 / 5

Workflow Clarity

The sequence is listed (open the Markdown → extract models/methods/biomarkers page by page → follow guide.md and template.md → output exactly 4 files) and validation sections exist, but written directives contradict each other: "Output must be produced directly (no confirmation steps or optional branches)" vs "User Checkpoints" demanding confirmation before multi-stage generation; and a Markdown-only input assumption ("paper content is available as Markdown") vs a Required Inputs table accepting "PMID, PDF, CSV, DOCX". These incoherences leave it at anchor 3 (steps present, checkpoints undermined) rather than 4.

3 / 5

Progressive Disclosure

The bundle structure is clean and one level deep: rules live in references/guide.md and the output structure in assets/template.md — both real files, clearly signaled with their purpose in "Key Features" and "Steps". The minor gap versus anchor 5 is that naming/encoding/language rules are duplicated inline in the body instead of being left solely to the reference, adding redundant content to the overview.

4 / 5

Total

13

/

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.

A strong description in third-person verb form: it names the three entity groups, the expected input format, the deliverable structure, and an explicit when-clause. Its weaknesses are mild — the trigger condition is singular and slightly circular, and a few natural synonyms are absent.

DimensionReasoningScore

Specificity

Quotes: "Extract experimental models, experimental methods, and biomarker information from paper Markdown", "structured, evidence-backed summary (1 Markdown + 3 CSVs)". It names three concrete extraction targets, the input format ("paper Markdown (typically produced by PDF-to-Markdown tools)"), and a concrete output contract, which is more than the 1-2 actions of anchor 3. It falls short of anchor 5's comprehensive coverage because page-aware evidence organization and the per-table schemas are not mentioned.

4 / 5

Completeness

Both parts are present: what ("Extract experimental models, experimental methods, and biomarker information... summary (1 Markdown + 3 CSVs)") and when ("when a user provides paper Markdown and needs a structured, evidence-backed summary"). The when clause is explicit but is a single, somewhat circular condition rather than the multiple concrete trigger phrases of anchor 5.

4 / 5

Trigger Term Quality

Natural terms a user would say appear: "experimental models", "experimental methods", "biomarker", "paper Markdown", "PDF-to-Markdown", "CSV". Good coverage, but common synonyms a user might naturally use — "literature", "cell lines", "animal models", "protocols/assays", "PDF" — are missing, so it does not reach anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche — literature experiment extraction with a fixed 1 Markdown + 3 CSV output — makes it mostly distinct, matching anchor 4. Minor overlap risk remains with sibling literature-analysis/extraction skills that also trigger on "paper Markdown" or "extract from paper", so it is not the minimal-conflict niche of anchor 5.

4 / 5

Total

16

/

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/literature-experiment-extract/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.