submission-integrity

Audit manuscripts for reference errors, self-overlap, and source similarity before journal submission.

Updated Oct 7, 2022
One-click install
npx skills add https://github.com/tamagusko/linux-cfg --skill submission-integrity-tamagusko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: submission-integrity
Source: https://github.com/tamagusko/linux-cfg/tree/main/dotfiles/claude/skills/submission-integrity
Command: npx skills add https://github.com/tamagusko/linux-cfg --skill submission-integrity-tamagusko

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Before a journal runs iThenticate or Turnitin on a submitted paper, authors have no way to screen their own manuscript for the issues those tools catch: broken or mismatched references, text recycled from their own prior papers, and passages sitting too close to cited sources. This Skill runs that pre-submission audit so problems are fixed while they are still cheap to fix. ## Core Features & Use Cases - Reference integrity verification: Checks that every citation resolves, metadata matches, in-text citations align with the bibliography, and cited sources actually support the claims made. - Self-overlap detection: Compares the manuscript against the author's published and in-progress papers using word-shingle matching to catch text recycling and redundant publication risks. - Source-overlap analysis: Compares against held reference PDFs and flags quoted-without-marks, structural tracking, and mosaic plagiarism patterns, with severity ratings and proposed rewrites. - Use Case: A researcher about to submit a paper asks for an originality check; the Skill verifies all references, finds a 40-word methods passage reused from a prior paper, and delivers a diff with a rewritten version. ## Quick Start Ask the assistant to run a pre-submission integrity audit on your manuscript file, checking references and overlap against your published papers folder.

Frequently Asked Questions about submission-integrity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my paper for self-plagiarism before submission?

Run a word-shingle overlap comparison of the manuscript against your published and in-progress papers. The audit reports every matching run of 12 or more words side by side, then a manual read catches reworded duplication that string matching misses.

How to verify references and citations in a manuscript?

Check that each entry's DOI resolves, metadata matches authors, year, title, and venue, and in-text citations align with the bibliography in both directions. Spot-verify that cited sources actually support the sentences citing them, marking unheld sources as unverifiable.

Can text overlap detection catch paraphrased plagiarism?

No. Shingle matching only finds verbatim or near-verbatim runs; reworded duplication is invisible to it by construction. A clean mechanical run narrows the human reading task for structural tracking and mosaic patterns but never ends it.

What file formats does the overlap script support?

The script extracts text from PDF files via pdftotext and reads plain text from .txt, .md, .tex, and .bbl files, stripping LaTeX commands and comments. Scanned PDFs that yield no text are reported as not compared.

What are the limitations of a pre-submission similarity check?

It cannot access the paywalled publisher corpus that iThenticate uses, so passages matching sources not held locally go undetected unless targeted web searches are run. It also cannot judge which of two parallel papers should keep an overlapping passage.