Medical-research-skills 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.

install
source · Clone the upstream repo
git clone https://github.com/aipoch/medical-research-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/aipoch/medical-research-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/scientific-skills/Other/result-figure-consistencycheck" ~/.claude/skills/aipoch-medical-research-skills-result-figure-consistencycheck && rm -rf "$T"
manifest: scientific-skills/Other/result-figure-consistencycheck/SKILL.md
source content

Source: https://github.com/aipoch/medical-research-skills

When to Use

  • You converted a paper PDF to Markdown and need to verify that Results text matches figure legends (without inspecting the images).
  • You want to detect missing figure references in the Results section (e.g., a legend describes an analysis not mentioned in text).
  • You need to find numerical/label mismatches (e.g., group names, time points, units, n-values) between Results paragraphs and legends.
  • You are preparing a revision and want an actionable discrepancy list down to the panel/sub-figure level.
  • You need standardized outputs (Markdown report + CSV) for editorial or QA workflows.

Key Features

  • Compares Results descriptions vs figure legend text using the PDF-to-Markdown source (including
    ## Page XX
    markers).
  • Produces:
    • A Markdown consistency report (UTF-8).
    • A CSV issue list (UTF-8) with structured fields for tracking and revision.
  • Enforces a template-based report format using
    assets/consistency_template.md
    .
  • Uses a rule/checklist reference from
    references/guide.md
    .
  • Text-only validation: does not read figure images and does not infer visual content.

Dependencies

  • None (no external runtime dependencies specified).
  • Input prerequisite (if starting from PDF): a PDF-to-Markdown conversion step (e.g.,
    pdf-extract
    ) must be completed before running this check.

Example Usage

Input

Place the converted full text Markdown in your working location (example:

inputs/paper_fulltext.md
). The file should include page headers like:

## Page 12
... Results text ...

Figure 3. ...
(A) ...
(B) ...

Run (conceptual workflow)

  1. Read the full Markdown input (PDF conversion output).
  2. Identify:
    • Result paragraphs describing findings.
    • Figure legend blocks (including panel labels such as A/B/C).
  3. Compare legend statements against Results statements and record discrepancies.
  4. Write outputs to
    outputs/
    :
    • outputs/consistency_report.md
      (UTF-8)
    • outputs/consistency_issues.csv
      (UTF-8)

Output files

outputs/consistency_issues.csv
(UTF-8) columns:

Figure Number,Location/Reference,Issue Description,Suggested Revision,Priority

Notes:

  • Location/Reference
    must contain only
    Page XX
    .
  • Issues should be granular to the panel/sub-figure level when applicable.

outputs/consistency_report.md
(UTF-8) must follow:

  • Template:
    assets/consistency_template.md
  • If no issues are found, write "None found" in the relevant sections.

Implementation Details

  • Scope of comparison

    • Only compare main text Results descriptions and figure legend text present in the Markdown input.
    • Do not inspect images or infer information not explicitly stated in text.
  • Rules and checklist

    • Follow the specific checking rules and required output points defined in:
      • references/guide.md
  • Report formatting

    • The Markdown report must be generated by filling:
      • assets/consistency_template.md
    • Ensure all outputs are saved under:
      • outputs/
        (within the skill directory)
  • Granularity and actionability

    • Record discrepancies at the most specific level possible (e.g., Figure 2B vs Figure 2 overall).
    • Provide a concrete Suggested Revision whenever feasible (e.g., align terminology, correct numbers/units, add missing reference).
  • Language

    • Default output language is Chinese.
    • If the user explicitly specifies another language, output in that language.