CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

result-figure-consistencycheck

Checks consistency between paper result descriptions and figure legends (text-only) when the input is a PDF-to-Markdown full text containing page breaks (e.g., `## Page XX`) and legend text; outputs a Markdown consistency report and a UTF-8 CSV issue list.

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/result-figure-consistencycheck/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 has a clear structure, real one-level-deep references, and concrete output contracts (paths, CSV columns, template), but it is held back by generic template boilerplate occupying much of the document and by a comparison methodology that remains conceptual both in SKILL.md and in the thin guide.md it defers to. An unreferenced bundled checklist file is a minor organization gap.

Suggestions

Trim or merge the generic boilerplate sections (Required Inputs, Output Contract, Failure Handling, User Checkpoints, Input Validation, Quick Validation) into a few skill-specific lines — e.g., replace the Required Inputs table with the single real prerequisite: a PDF-to-Markdown full text with '## Page XX' markers and legend text.

Make the comparison step concrete: enumerate the specific checks to perform per figure (values, units, n-values, group names, time points, panel-level claims, missing figure references) either inline or with real detail in references/guide.md, instead of 'Compare legend statements against Results statements'.

Reference assets/figure_caption_checklist.csv from the body (e.g., in the workflow) so the bundled checklist is discoverable, and turn the generic Quick Validation section into concrete output checks (every CSV row uses 'Page XX', report follows the template, no-issue sections say 'None found').

DimensionReasoningScore

Conciseness

The skill-specific sections (When to Use, Example Usage, Implementation Details) are reasonably tight, but roughly 40% of the body is generic boilerplate ('Required Inputs' with rows like 'Primary input material | Depends on task | Text, file path, ID, table, or literature', 'Output Contract', 'Failure Handling', 'User Checkpoints', 'Input Validation', 'Quick Validation') that applies to any skill and adds tokens without skill-specific value. Not a 2 because the core instructions are not padded and no concepts Claude already knows are re-explained; not a 4 because the boilerplate sections are clearly trimmable.

3 / 5

Actionability

There is some concrete guidance: exact output paths ('outputs/consistency_report.md', 'outputs/consistency_issues.csv'), a literal CSV header ('Figure Number,Location/Reference,Issue Description,Suggested Revision,Priority'), the 'Page XX' location rule, and the 'None found' convention. But the core methodology is self-described as a 'Run (conceptual workflow)' — 'Compare legend statements against Results statements and record discrepancies' — with the actual checking rules deferred to references/guide.md, which itself only offers generic checks ('Consistency in values, units, and directions'). Not a 4 because the comparison step, the heart of the skill, lacks concrete executable detail.

3 / 5

Workflow Clarity

A clear 4-step sequence is given (read input → identify result paragraphs and legend blocks → compare and record discrepancies → write the two named output files), with explicit checkpoints: the 'None found' no-issue case, a Failure Handling section ('Report the failing step, likely cause, and recovery suggestions — do not silently degrade'), PARTIAL marking for partial completion, and a Quick Validation section. Not a 5 because the validation checkpoints are generic boilerplate rather than concrete checks tied to this workflow (e.g., verifying each CSV row has a 'Page XX' location), and the workflow is labeled 'conceptual'.

4 / 5

Progressive Disclosure

The body is an overview that cleanly defers detail one level deep to real, verified files: 'references/guide.md' (exists) for checking rules and 'assets/consistency_template.md' (exists) for the report format, with paths stated inline at the point of need. Not a 5 because assets/figure_caption_checklist.csv is present in the bundle but never referenced from SKILL.md, leaving a bundled asset undiscoverable, and because the skill is simple enough that some inlined boilerplate sections dilute the overview.

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 strong, third-person description that concretely states what the skill does, its input precondition, and its two output artifacts. Its main limitation is that the 'when' clause is an input-format condition rather than a natural user-intent trigger, and a few common synonyms (e.g., 'figure captions', 'Results section') are absent.

DimensionReasoningScore

Specificity

The description names the domain ('consistency between paper result descriptions and figure legends') and several concrete actions with concrete artifacts: 'outputs a Markdown consistency report and a UTF-8 CSV issue list', plus a specific input format ('PDF-to-Markdown full text containing page breaks (e.g., `## Page XX`)'). It is not a 5 because it does not enumerate the comparison coverage (e.g., detecting missing figure references, numerical/label mismatches) that the body documents; it is above 3 because it goes beyond naming one or two actions.

4 / 5

Completeness

The 'what' is explicit ('Checks consistency between paper result descriptions and figure legends... outputs a Markdown consistency report and a UTF-8 CSV issue list') and a 'when' clause is present ('when the input is a PDF-to-Markdown full text containing page breaks... and legend text'). It is not a 5 because the 'when' is framed as an input precondition rather than a user-intent trigger phrase ('Use when the user asks to verify...'), so the trigger guidance could be more explicit.

4 / 5

Trigger Term Quality

Natural terms a user would say are present: 'paper', 'result descriptions', 'figure legends', 'PDF-to-Markdown', 'consistency', 'CSV'. Missing common synonyms such as 'figure captions', 'Results section', or 'caption check', which keeps it below the comprehensive-synonym anchor of 5 but above the 3 anchor where common variations are missing.

4 / 5

Distinctiveness Conflict Risk

This is a clear niche (text-only result-vs-legend consistency checking for research papers with two defined output artifacts), making wrong-skill triggering unlikely except against closely related figure/QA skills in the same paper-workflow family (e.g., a PDF extraction skill). That minor overlap risk with adjacent medical-research-paper skills keeps it at 4 rather than 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/Other/result-figure-consistencycheck/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.