CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

literatureimages-interpretation

Interpret figures in academic papers and their captions when the input is a PDF-to-Markdown document with page markers and image links, producing a structured Markdown report for extracting variables, trends, and conclusions.

Quality

73%

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/Other/literatureimages-interpretation/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 body delivers concrete, actionable operational guidance with a clear workflow and genuine validation checkpoints, supported by real one-level-deep bundle files. Its main weakness is token efficiency: core rules are restated three times and several generic boilerplate sections add padding rather than skill-specific value, which drags conciseness down.

Suggestions

State each core rule once (full image pass, no exported image list, UTF-8 encoding) in Implementation Details and delete the duplicates in Key Features and the Run workflow section.

Replace or remove the generic Required Inputs / Output Contract / Failure Handling / User Checkpoints boilerplate, collapsing the near-duplicate sections into one short skill-specific checklist.

De-duplicate against references/guide.md: keep SKILL.md as the overview with the workflow and constraints, and move the detailed checklist rules entirely into guide.md.

DimensionReasoningScore

Conciseness

Core rules are repeated three times each — "Open **every** image... without skipping" (Key Features, Run workflow, Implementation Details), "do not generate or export any image list" (three restatements), and UTF-8 output (three restatements) — and the generic boilerplate sections (Required Inputs with "PMID, PDF, CSV, DOCX", Output Contract, Failure Handling, User Checkpoints, Input Validation, Quick Validation) largely duplicate one another while adding little skill-specific value. This is noticeably verbose with several padded sections, but the core operational detail is specific rather than explanations of concepts Claude already knows, so it sits above the 1 anchor and below the 3 anchor.

2 / 5

Actionability

The guidance is mostly concrete and executable for an instruction-only skill: exact folder convention ("RateSOX2.md → RateSOX2-images/"), enumerated image classification categories, the "Unassigned" fallback label, a specific bash command for PDF conversion, and concrete template and output paths with an example filename. It is not fully copy-paste ready (the workflow is labeled "Run (conceptual workflow)" and template fields are not shown inline), placing it below the 5 anchor but clearly above the pseudocode-level 3 anchor.

4 / 5

Workflow Clarity

The sequence is clear (convert PDF → verify images folder → read Markdown → open every image → classify → align to figure numbers → fill template → write single output) and validation is present (Quality checks deferred to references/guide.md, a Quick Validation section, PARTIAL marking for partial completion, and user checkpoints before overwriting or batch operations). It falls short of the 5 anchor because checkpoints are somewhat generic and there is no explicit validate-fix-retry feedback loop inline; it is above the 3 anchor because validation steps do exist rather than being absent.

4 / 5

Progressive Disclosure

The body references two real one-level-deep bundle files (references/guide.md, assets/figure_interpretation_template.md), both clearly signaled in the Dependencies section and confirmed to exist, and the body is well organized with section headers. It is not a 5 because guide.md duplicates rules already stated in SKILL.md (full image pass, no image-list export, UTF-8) rather than cleanly splitting detail one level down, and the body itself carries redundant sections.

4 / 5

Total

14

/

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 solid description: it names a clear niche, concrete actions, a concrete deliverable, and an explicit input-condition trigger in third person. Its main gaps are missing synonym-level trigger terms and no explicit "Use when the user..." phrasing, plus omission of some of the skill's actual capabilities.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to interpret or extract data from figures, charts, or plots in a converted academic paper."

Include natural synonyms such as "charts", "plots", and "figure legends" to broaden trigger coverage.

Mention the figure-number alignment (e.g., mapping images to Figure 1A/2) so the stated capabilities match the skill's full scope.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Interpret figures in academic papers and their captions", "producing a structured Markdown report", "for extracting variables, trends, and conclusions" — with a defined deliverable, but omits other real capabilities of the skill (image classification, figure-number alignment, filtering of body-text blocks), so coverage has minor gaps. It exceeds the 3 anchor (only 1-2 concrete actions) but is not comprehensive enough for the 5 anchor.

4 / 5

Completeness

The "what" is clear (figure/caption interpretation producing a structured Markdown report) and the "when" is explicitly stated as an input condition ("when the input is a PDF-to-Markdown document with page markers and image links"). It is not a 5 because there is no explicit user-facing trigger clause ("Use when the user asks for figure interpretation..."), and not a 3 because the when is explicitly written rather than merely implied.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "figures", "academic papers", "captions", "PDF-to-Markdown", "image links", "variables, trends, and conclusions" — phrases a user with such a document would naturally use. It falls short of the 5 anchor because it lacks synonyms and variations ("charts", "plots", "scientific paper", file extensions like .md/.pdf).

4 / 5

Distinctiveness Conflict Risk

The niche is distinct — interpreting figures from PDF-to-Markdown academic papers with paired image folders — with specific trigger conditions minimizing false fires. Minor overlap risk remains with general paper-analysis or pdf-extraction skills ("interpret figures in academic papers" alone is broad), keeping it below the 5 anchor.

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/Other/literatureimages-interpretation/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.