CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

figure-first-paper-reader

Reads a paper figure by figure before re-integrating the full narrative, so the user can identify the core findings quickly and check whether each visual actually supports the authors' main claims. Always separate figure content, figure-linked claim, evidentiary strength, and unsupported interpretation. Never fabricate references, PMIDs, DOIs, figure content, panel labels, result values, or study details that were not actually provided.

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

85%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 instruction skill: the 8-step workflow is concrete, validated, and anchored by real one-level-deep reference modules with clear use conditions. The only weakness is redundancy — three sections restate the procedure and rules, which inflates token cost without adding guidance.

Suggestions

Merge "Core Function" and "What This Skill Should Not Do" into the 8-step execution section and Hard Rules, removing their duplicated restatements of the same points.

Cut the "Quality Standard" closing section — its strong/weak output definitions repeat the steps and Hard Rules verbatim in spirit.

State the never-fabricate rule once (e.g., in Hard Rules plus references/literature-integrity-rules.md) instead of repeating it in the description, section H, and Hard Rule 10.

DimensionReasoningScore

Conciseness

The body is mostly efficient — tight bulleted lists, no explanations of concepts Claude already knows — but it could be tightened: "Core Function", "What This Skill Should Not Do", and "Quality Standard" largely restate the 8-step procedure and Hard Rules, and the separate-observation-from-interpretation and never-fabricate rules each appear 3–4 times across sections. This matches anchor 3 (mostly efficient with some unnecessary repetition) better than anchor 2, since no section is pure padding and the core procedure text earns its place.

3 / 5

Actionability

As an instruction-only skill, the guidance is fully concrete: an ordered 8-step procedure with named classification schemes (four support-strength categories, five overinterpretation patterns, five figure types), a defined figure-to-claim table format in references/figure-to-claim-framework.md, and a mandatory output structure (sections A–H) with specified fields. Specific examples cover the common cases (quick scan vs. full audit, captions-only material, missing figures), matching the top anchor for concrete, executable guidance.

5 / 5

Workflow Clarity

The 8 steps are explicitly ordered ("always run in order") with explicit validation checkpoints: Step 1 requires declaring missing figures before judging support, Step 8 is a dedicated self-critical final check (strongest link, weakest link, biggest overinterpretation risk), and the output's Risk Review section provides a final audit. The 15-item Hard Rules checklist covers edge cases like ambiguous figure-to-claim links and unreadable panels. This matches the anchor for clear sequence with explicit validation steps and checklists.

5 / 5

Progressive Disclosure

The "Reference Module Integration" section clearly signals all 7 one-level-deep references with per-file use conditions ("Use for mapping each figure...", "Use when the visual evidence is weaker..."); all 7 referenced files exist in references/ and none nest further references. The body appropriately keeps the overview (steps, output structure, rules) while details live in the reference files, matching the anchor for a clear overview with well-signaled one-level-deep references.

5 / 5

Total

18

/

20

Passed

Description

71%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 with strong capability coverage and a distinctive figure-to-claim auditing niche, undermined by the absence of an explicit "Use when..." trigger clause and missing natural synonyms like "figure-first". Adding explicit trigger guidance would lift it into the top tier.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for a figure-first read, wants a figure-by-figure analysis of a paper, or wants to check whether the figures actually support the paper's claims."

Include natural synonyms and variations users would say — "figure-first", "figure-by-figure", "plots", "captions", "panels" — to improve trigger-term coverage.

Trim the trailing fabrication-prohibition sentence ("Never fabricate references, PMIDs, DOIs...") or shorten it, since it adds length without adding trigger or capability value; the body's Hard Rules already enforce it.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Reads a paper figure by figure", "identify the core findings quickly", "check whether each visual actually supports the authors' main claims", and "separate figure content, figure-linked claim, evidentiary strength, and unsupported interpretation" — covering the skill's capabilities comprehensively. This matches the anchor for multiple specific concrete actions with comprehensive coverage rather than the anchor 4 example with 'minor gaps in coverage'.

5 / 5

Completeness

The "what" is clear and concrete, but there is no "Use when..." clause or equivalent explicit trigger guidance; the only "when" signal is the weakly implied purpose "so the user can identify the core findings quickly and check whether each visual actually supports the authors' main claims". Per the judging guideline, a missing 'Use when' clause or equivalent caps completeness at 3 — the purpose clause implies the use case but never states it as a trigger.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "paper", "figure by figure", "core findings", "claims", "visual" are phrases users would naturally say when requesting this skill. However, common variations are missing — notably "figure-first" itself (the skill's core concept and name), plus synonyms like "plots", "captions", or "summarize" — so it falls short of the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The figure-by-figure claim-audit framing ("check whether each visual actually supports the authors' main claims", PMIDs/DOIs/panel labels) carves a clear niche that is mostly distinct from generic paper-summarization skills, matching anchor 4. It is not anchor 5 because it would still overlap with general paper-reading/summary skills that also mention figures and claims, and lacks a fully distinct trigger phrase like "figure-first".

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

awesome-med-research-skills/Evidence Insight/figure-first-paper-reader/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.