Agent skill

Consistency Checker Across Manuscript

by aipoch in aipoch/medical-research-skills

Checks consistency across title, abstract, methods, results, figures, tables, and supplements to identify internal contradictions and version drift in biomedical manuscripts.

MITAuto-check passedResearch & Science

Install Consistency Checker Across Manuscript

skills CLI
$ npx skills add aipoch/medical-research-skills --skill consistency-checker-across-manuscript -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aipoch/medical-research-skills consistency-checker-across-manuscript --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aipoch/medical-research-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'awesome-med-research-skills/Academic Writing/consistency-checker-across-manuscript' .claude/skills/consistency-checker-across-manuscript && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
consistency-checker-across-manuscript
GitHub stars
1.9k
Token cost
~2.9k tokens
SKILL.md length
1,363 words
Files
10 (incl. references)
Skills in repo
578
Repo updated
First seen
Licence
MIT

At a glance

Checks consistency across title, abstract, methods, results, figures, tables, and supplements to identify internal contradictions and version drift in biomedical manuscripts.

  • Works in 8 steps: Clarify before checking → Define the comparison scope → Compare the core manuscript components → …
  • Research & Science work in your project
  • SKILL.md covers Task, Scope Boundary, Important Distinctions and Reference Module Integration, plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Consistency Checker Across Manuscript is an agent skill from aipoch/medical-research-skills. Checks consistency across title, abstract, methods, results, figures, tables, and supplements to identify internal contradictions and version drift in biomedical manuscripts.

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `eval_report_consistency-checker-across-manuscript_result.json`, `references/clarification-first-rule.md` and `references/component-alignment-rules.md`).

It sits in Research & Science. The repository describes itself as: Hundreds of agent skills for medical research, including protocol design, data analysis, evidence insights, and academic writing. The licence is MIT.

When your agent uses it

  • Research & Science work in your project

Example prompts

  • “Use the consistency-checker-across-manuscript skill to check consistency across title, abstract, methods, results, figures, tables, and supplements…”
  • “/consistency-checker-across-manuscript”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Clarify before checking
  2. Define the comparison scope
  3. Compare the core manuscript components
  4. Detect high-risk inconsistency patterns
  5. Classify severity
  6. Explain correction priority
  7. Explain the consistency logic
  8. Produce the final structured output

What it can do on your machine

Read from SKILL.md and the folder at commit 686e09d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Consistency Checker Across Manuscript loads about 2.9k tokens when it runs, and up to ~4k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 1,363 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aipoch/medical-research-skills at commit 686e09d, republished under its MIT licence (© aipoch). 1,363 words, ~2,877 tokens.

Download SKILL.mdSave it as .claude/skills/consistency-checker-across-manuscript/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
consistency-checker-across-manuscript
description
Checks consistency across title, abstract, methods, results, figures, tables, and supplements to identify internal contradictions and version drift in biomedical manuscripts.
license
MIT
author
AIPOCH

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

Consistency Checker Across Manuscript

You are a biomedical academic writing specialist focused on cross-manuscript consistency checking.

Your job is not to do generic proofreading or cosmetic editing.
Your job is to determine whether the manuscript’s major components are internally aligned, and to identify where version drift, wording drift, numerical inconsistency, structural mismatch, or evidence mismatch creates risk for confusion, reviewer criticism, or loss of credibility.

Task

Given a manuscript draft, selected sections, figure list, table set, supplement materials, revision package, or submission draft, produce a cross-manuscript consistency review that:

  1. checks whether title, abstract, methods, results, figures, tables, and supplements agree with each other,
  2. identifies internal inconsistencies such as sample-size drift, endpoint wording drift, figure-number mismatch, and mismatch between conclusions and presented results,
  3. distinguishes major credibility risks from moderate or minor version-control issues,
  4. separates true inconsistency from acceptable section-specific wording differences,
  5. explains why specific inconsistencies matter,
  6. requests additional material when the input is insufficient,
  7. and helps the user reduce avoidable reviewer confusion caused by internal manuscript misalignment.

Scope Boundary

This skill is for consistency checking across manuscript components, not for rewriting the whole paper or re-evaluating the underlying science from scratch.

It is appropriate for:

  • full manuscript pre-submission review,
  • revision-stage version checks,
  • title / abstract / methods / results alignment review,
  • figure and supplement consistency checks,
  • cross-section terminology consistency review,
  • sample-size and endpoint consistency review,
  • response-to-review cross-version checking.

It is not for:

  • inventing missing manuscript elements,
  • pretending consistency can be checked from only a topic or title,
  • treating all wording differences as errors,
  • or certifying internal consistency when the relevant sections are unavailable.

Important Distinctions

This skill must clearly distinguish:

  • true inconsistency vs acceptable wording variation,
  • numerical contradiction vs section-specific summarization difference,
  • figure-number mismatch vs simple ordering preference,
  • endpoint drift vs different but compatible phrasing,
  • conclusion-result mismatch vs interpretive emphasis,
  • minor version-control issue vs major credibility risk.

Reference Module Integration

Use the reference files actively when producing the output:

  • references/clarification-first-rule.md

    • Use before any long-form consistency review.
    • If the manuscript components under comparison are incomplete or unclear, ask for the missing materials first.
  • references/component-alignment-rules.md

    • Use to compare core manuscript parts:
      • title,
      • abstract,
      • methods,
      • results,
      • figures,
      • tables,
      • supplements.
  • references/version-drift-rules.md

    • Use to detect sample-size drift, endpoint drift, outcome-label drift, analysis-description drift, and other revision-induced inconsistencies.
  • references/figure-table-supplement-linkage-rules.md

    • Use to check figure numbering, table numbering, supplement references, and whether cited display items match the prose.
  • references/conclusion-boundary-rules.md

    • Use to determine whether the manuscript’s summary claims still match the actual presented results.
  • references/severity-classification-rules.md

    • Use to classify consistency problems into major, moderate, minor, or uncertain due to missing material.
  • references/logic-reporting-rule.md

    • Use to explain why a given inconsistency creates credibility risk or only limited cleanup burden.
  • references/hard-rules.md

    • Apply throughout the entire response.
    • These rules override surface fluency and false reassurance.

Input Validation

Before producing a long output, determine whether the user has clearly supplied enough information about:

  • which manuscript components are being checked,
  • whether the review is full-manuscript or targeted,
  • whether figures/tables/supplements are available,
  • whether the manuscript is in pre-submission or revision stage,
  • and whether the goal is contradiction detection, version-drift review, or general alignment review.

If these are not clear enough, do not jump into a full consistency assessment.
First tell the user what information is missing and what additional inputs would materially improve accuracy.
When helpful, explicitly recommend uploading:

  • title and abstract,
  • Methods and Results sections,
  • figure list,
  • table list,
  • supplement references,
  • or the full draft.

Sample Triggers

Use this skill when the user asks things like:

  • “Can you check whether my manuscript is internally consistent?”
  • “Please look for contradictions across abstract, methods, and results.”
  • “Are the sample sizes and endpoints described consistently?”
  • “Do the figure references and tables match the Results text?”
  • “Can you check for version drift after revision?”
  • “Does the conclusion still match the actual data shown?”

Core Function

This skill should:

  1. identify the consistency-checking scope,
  2. compare key manuscript components,
  3. detect contradictions and drift,
  4. classify issue severity,
  5. explain why the inconsistency matters,
  6. request better materials when needed,
  7. and protect the user from false reassurance about manuscript alignment.

Execution

Step 1 — Clarify before checking

If the user provides only a vague request to “check consistency” without the actual sections or components to compare, do not immediately produce a full review.
First explain what is missing, ask focused follow-up questions, or recommend uploading the relevant manuscript materials.

Step 2 — Define the comparison scope

Determine whether the review is mainly about:

  • title / abstract / main-text alignment,
  • methods / results alignment,
  • results / figures / tables alignment,
  • supplement linkage,
  • revision-stage version drift,
  • or full-manuscript consistency.
Step 3 — Compare the core manuscript components

Check whether:

  • title matches the study actually reported,
  • abstract matches methods and results,
  • methods support the analyses described later,
  • results match the figures/tables cited,
  • supplements are referenced correctly and consistently,
  • terminology is stable across sections.
Step 4 — Detect high-risk inconsistency patterns

Identify issues such as:

  • sample-size inconsistencies,
  • shifting endpoint wording,
  • population-definition drift,
  • model or variable-description drift,
  • figure/table numbering mismatch,
  • result-conclusion mismatch,
  • supplementary material citation mismatch.
Show full SKILL.md (536 more words)Show less
Step 5 — Classify severity

Separate findings into:

  • major consistency risk,
  • moderate consistency concern,
  • minor cleanup issue,
  • uncertain due to missing section access.
Step 6 — Explain correction priority

State which inconsistencies most urgently need:

  • numerical correction,
  • terminology harmonization,
  • figure/table renumbering,
  • abstract revision,
  • conclusion narrowing,
  • supplement linkage repair,
  • or cross-section rewrite.
Step 7 — Explain the consistency logic

For major issues, explicitly explain:

  • what the inconsistency is,
  • which sections are in conflict,
  • and why it creates reviewer, editor, or credibility risk.
Step 8 — Produce the final structured output

Follow the mandatory output structure below.

Mandatory Output Structure

A. Input Match Check

State whether the provided material is sufficient for high-confidence consistency checking. If not, clearly say what is missing.

B. Review Scope Determination

State whether the review is full-manuscript, targeted cross-section, figure/table linkage, supplement linkage, or revision-drift review.

C. Main Consistency Findings

State the main problems found, such as:

  • sample-size drift,
  • endpoint wording drift,
  • terminology inconsistency,
  • figure/table mismatch,
  • supplement mismatch,
  • abstract-result mismatch,
  • conclusion-result mismatch.
D. Major Consistency Risks

List the highest-risk inconsistency problems.

E. Moderate and Minor Consistency Issues

List the non-critical but important alignment problems.

F. Correction Priority Plan

State what should be corrected first and how.

G. Consistency Logic Explanation

Explain the major consistency judgments and why they matter.

H. What Additional Information Would Improve Accuracy

If anything important remains unclear, list the exact missing inputs that would improve the review. When helpful, recommend uploading title/abstract, Methods and Results, figure list, table list, supplement references, or the full draft.

Formatting Expectations

  • Use the section headers exactly as above.
  • Keep the review concrete, not generic.
  • Explain issues in terms of internal alignment, version drift, interpretability, and credibility risk.
  • Do not treat all wording differences as equally important.
  • Do not produce a confident long consistency review when the manuscript components are still too incomplete.

Hard Rules

  1. Do not invent manuscript inconsistencies that have not been shown.
  2. Do not certify cross-section consistency when the relevant components are unavailable.
  3. Do not treat all wording variation as error; some differences may be acceptable summarization.
  4. Do not ignore numerical contradictions, endpoint drift, or figure/table mismatch when they are present.
  5. Do not reassure the user that the manuscript is internally aligned without enough evidence.
  6. Do not fabricate sample sizes, endpoints, results, figure numbering, supplement content, or validation status.
  7. Always classify consistency issues by severity.
  8. Always explain why a given inconsistency matters for manuscript credibility or reviewability.
  9. Always distinguish between true contradiction and uncertainty caused by missing manuscript material.
  10. If the input is insufficient, ask follow-up questions or recommend uploading the relevant manuscript components first.

What This Skill Should Not Do

This skill should not:

  • act like a generic proofreader,
  • guess consistency from a title or summary alone,
  • overflag harmless wording variation,
  • underflag numerical or structural contradictions,
  • or hide uncertainty when source material is incomplete.

Quality Standard

A strong output from this skill:

  • correctly identifies true cross-section inconsistencies,
  • distinguishes major risks from minor cleanup issues,
  • explains why they matter,
  • prioritizes corrections realistically,
  • and tells the user when better manuscript material is needed.

A weak output:

  • gives only vague alignment advice,
  • guesses at missing content,
  • confuses variation with contradiction,
  • or reassures the user without enough evidence.

© aipoch, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in awesome-med-research-skills/Academic Writing/consistency-checker-across-manuscript of aipoch/medical-research-skills.

  • SKILL.md
  • eval_report_consistency-checker-across-manuscript_result.json
  • references/clarification-first-rule.md
  • references/component-alignment-rules.md
  • references/conclusion-boundary-rules.md
  • references/figure-table-supplement-linkage-rules.md
  • references/hard-rules.md
  • references/logic-reporting-rule.md
  • references/severity-classification-rules.md
  • references/version-drift-rules.md

Open the folder on GitHubat commit 686e09d

Compare with similar skills

Consistency Checker Across Manuscript next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Consistency Checker Across Manuscript compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Consistency Checker Across Manuscript this skillaipoch/medical-research-skills1.9k—~2.9kAutomated safety check: PassMIT
Hypothesis Generationspacering-net/codeg3.9k14 repos~3.6kAutomated safety check: NotesMIT
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Nature Paper CardYuan1z0825/nature-skills47k2 repos~2.1kAutomated safety check: PassApache-2.0
Content Research Writerweapp-tailwindcss/weapp-tailwindcss1.9k25 repos~3.5kAutomated safety check: PassMIT
Last30daysmvanhorn/last30days-skill64k—~7.9kAutomated safety check: NotesMIT

Similar skills

  • Hypothesis Generation

    spacering-net/codeg

    Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.

    3.9k GitHub starsUsed in 14 repos~3.6k tokens
    Research & ScienceAuto-check: notes
  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Nature Paper Card

    Yuan1z0825/nature-skills

    Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.

    47k GitHub starsUsed in 2 repos~2.1k tokens
    Research & ScienceAuto-check passed
  • Content Research Writer

    weapp-tailwindcss/weapp-tailwindcss

    Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.

    1.9k GitHub starsUsed in 25 repos~3.5k tokens
    Research & ScienceAuto-check passed
  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.9k tokensUpdated yesterday
    Research & ScienceAuto-check: notes
  • Peer Review

    spacering-net/codeg

    Structured manuscript/grant review with checklist-based evaluation.

    3.9k GitHub starsUsed in 17 repos~5.9k tokens
    Research & ScienceAuto-check: notes

More from aipoch/medical-research-skills

All 578 skills in this repo
  • Academic Poster Generator

    aipoch/medical-research-skills

    Complete workflow for generating academic research posters from PDF literature; use when you need to extract paper content from PDFs and produce a LaTeX-based poster…

    1.9k GitHub stars~2.2k tokensUpdated 24 days ago
    Auto-check passed
  • Diagnostic Study Quality Assessment Quadas

    aipoch/medical-research-skills

    Analyzes clinical diagnostic accuracy studies for bias using the QUADAS-2 tool.

    1.9k GitHub stars~1.4k tokensUpdated 24 days ago
    Auto-check passed
  • Exploratory Data Analysis

    aipoch/medical-research-skills

    Perform comprehensive exploratory data analysis on scientific data files across 200+ file formats.

    1.9k GitHub stars~3.7k tokensUpdated 24 days ago
    Auto-check passed
  • Iso Certification

    aipoch/medical-research-skills

    A toolkit for preparing ISO 13485:2016 certification documentation for medical device QMS.

    1.9k GitHub stars~1.8k tokensUpdated 24 days ago
    Auto-check passed
  • Journal Skills

    aipoch/medical-research-skills

    Recommends target journals for manuscript submission by analyzing the paper topic/abstract and the journal distribution of similar PubMed literature; use when users ask for journal…

    1.9k GitHub stars~1.7k tokensUpdated 24 days ago
    Auto-check passed
  • Latex Posters

    aipoch/medical-research-skills

    Creates academic-poster writing packages for LaTeX using beamerposter, tikzposter, or baposter.

    1.9k GitHub stars~1.3k tokensUpdated 24 days ago
    Auto-check passed

Questions about Consistency Checker Across Manuscript

What does Consistency Checker Across Manuscript do?

Checks consistency across title, abstract, methods, results, figures, tables, and supplements to identify internal contradictions and version drift in biomedical manuscripts. Consistency Checker Across Manuscript is an agent skill from aipoch/medical-research-skills. Checks consistency across title, abstract, methods, results, figures, tables, and supplements to identify internal contradictions and version drift in biomedical manuscripts.

When should I use Consistency Checker Across Manuscript?

Consistency Checker Across Manuscript fits situations like: research & Science work in your project.

How do I install Consistency Checker Across Manuscript in Claude Code?

Run `npx skills add aipoch/medical-research-skills --skill consistency-checker-across-manuscript -a claude-code`. Or copy the skill folder (awesome-med-research-skills/Academic Writing/consistency-checker-across-manuscript in aipoch/medical-research-skills) into .claude/skills/consistency-checker-across-manuscript in your project. Claude Code loads it when a task matches its description.

How do I install Consistency Checker Across Manuscript in Codex?

Run `npx skills add aipoch/medical-research-skills --skill consistency-checker-across-manuscript -a codex`. Or copy the skill folder (awesome-med-research-skills/Academic Writing/consistency-checker-across-manuscript in aipoch/medical-research-skills) into .agents/skills/consistency-checker-across-manuscript in your project. Codex loads it when a task matches its description.

Can I use Consistency Checker Across Manuscript in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aipoch/medical-research-skills --skill consistency-checker-across-manuscript -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/consistency-checker-across-manuscript, .gemini/skills/consistency-checker-across-manuscript, .github/skills/consistency-checker-across-manuscript and .opencode/skills/consistency-checker-across-manuscript in your project.

What does Consistency Checker Across Manuscript need to run?

SKILL.md names no scripts, command-line tools or credentials: Consistency Checker Across Manuscript is instructions for the agent only.

Does Consistency Checker Across Manuscript access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Consistency Checker Across Manuscript safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Consistency Checker Across Manuscript use?

Consistency Checker Across Manuscript is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Consistency Checker Across Manuscript use?

About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Consistency Checker Across Manuscript?

Skills that share tags, products or a category with Consistency Checker Across Manuscript: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Consistency Checker Across Manuscript?

aipoch (a GitHub organization) maintains it in aipoch/medical-research-skills, which has 1,937 GitHub stars. The repository holds 578 skills in this directory. The repository was last updated on September 17, 2026.

Source: aipoch/medical-research-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.