agentleFS
LiaScriptLiaScript/skills/skills/reference-checker/SKILL.md

reference-checker

Skill0 starsChanged 9 days agoMITView on GitHub

Verifies scientific literature references for accuracy and produces a structured report. Always use when the user wants to check, verify, or validate bibliographic entries, citations, references, DOIs or a BibTeX (.bib) file — including individual ones, and including whether a cited paper was retracted or a reference may be AI-generated. Always outputs a complete reference verification report with per-entry ratings (three-tier: ✅ correct / ⚠️ warning / 🚨 critical error) and a summary table. Also use for: 'check my references', 'verify citations', 'are my sources correct?', 'Stimmen die Angaben?', 'Sind die Quellen korrekt?', 'Bitte Referenzen checken', or similar verification requests. Output language always matches the user's input language.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Jay-Chen79/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search the web for every entry without a convincing record (books, theses, reports, patents, proceedings without DOI) and to confirm …

    line 47
  2. Distinctive:

    Always respond in the same language as the user's request (English, German, or other).

    line 66
  3. Distinctive:

    Non-standard format: Only a URL provided (e.g., institutional repository), no complete citation style

    line 79
  4. Distinctive:

    Not verifiable / possibly hallucinated: No match despite extensive search.

    line 85
  5. Distinctive:

    If the input was a BibTeX file, add a section with the corrected entries ready to paste (and which keys to remove).

    line 155
  6. Distinctive:

    If multiple references have 🚨 status, append a notice block at the end of the table:

    line 157
  7. Distinctive:

    Patents and reports: follow their own citation standards: inventor, applicant, patent number, country, date.

    line 197

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Reference Checker

This skill systematically verifies scientific literature references using web search and always outputs results in a consistent, three-tier format.


Workflow

1. Extract References

Extract and number all references to be checked from the user's input.

2. Look Up the Records

First run the lookup script on all references at once (from the skill folder; Python standard library, needs internet):

python3 scripts/lookup.py refs.bib          # BibTeX file
python3 scripts/lookup.py refs.txt          # one reference per line or paragraph
python3 scripts/lookup.py --doi 10.1038/nature14539

For every entry it prints the Crossref record behind a given DOI (with a title match score), the best Crossref and OpenAlex matches for the full reference, print vs. online year, volume, issue, pages / article number, and retractions, corrections and expressions of concern (Crossref updated-by from Retraction Watch, OpenAlex is_retracted). Read it as evidence:

  • a DOI whose record has a title match below about 0.6 belongs to a different work;
  • a real journal + volume + page/article number that the records assign to a different paper is the classic pattern of a fabricated reference;
  • Crossref also lists later copies (posted-content, reprints, book chapters) — compare with the version of record; conference papers (e.g. NeurIPS) often have no DOI and appear in OpenAlex.

3. Web Search Where the Records Are Not Enough

Search the web for every entry without a convincing record (books, theses, reports, patents, proceedings without DOI) and to confirm anything doubtful. Search strategy:

  • Primary: Title + journal + year
  • Secondary: Authors + title (if no results)
  • Tertiary: Search DOI directly (if provided)
  • Quaternary: Patent databases / institutional repositories (for patents, reports, theses)

Verify the following:

  • Authors: Full names, order, correct spelling; for "et al." check at least the first author
  • Title: Exact wording
  • Journal / Source: Correct name
  • Year: Publication year (note online-first vs. print publication date)
  • Volume: Number
  • Page or article number: First page or article number (e.g., 123603)
  • Document type: Article, patent, dissertation, report, conference paper, etc.
  • DOI: Retrieve and validate
  • URL: Retrieve direct URL to the publication

4. Output Language

Always respond in the same language as the user's request (English, German, or other).


Three-Tier Rating System

✅ — CORRECT

The reference is complete and all verified details match. Minor formatting differences (e.g., spacing, abbreviations) do not count as errors.

⚠️ — WARNING

The reference exists and is findable, but has issues that should be fixed before submission. Typical ⚠️ cases:

  • Year error: Online-first year ≠ print year (e.g., online 2014, printed 2015)
  • Incomplete details: Missing authors, missing volume/page numbers, missing patent numbers
  • Non-standard format: Only a URL provided (e.g., institutional repository), no complete citation style
  • Minor errors: Slight typos in author names, wrong initials, slightly different title
  • Missing document type: Dissertation/patent/report not identified as such

🚨 — CRITICAL ERROR

Severe errors that compromise the integrity of the reference. Typical 🚨 cases:

  • Not verifiable / possibly hallucinated: No match despite extensive search; plausible-sounding details with no real counterpart — often a sign of AI-generated false citations
  • Wrong journal: Article exists but was published in a different journal
  • Wrong authors: Completely different author group
  • Wrong page numbers/article numbers: Significant deviation from actual details
  • Wrong first author
  • Retracted: the record has a retraction (updated-by type retraction, or is_retracted). Always 🚨, also when every detail is correct; if the text discusses the paper as a retracted study, say how to cite it (mark it as retracted, add the retraction notice).
  • DOI belongs to a different work: the given DOI resolves to another paper. Give the correct DOI.

Output Format (ALWAYS follow)

Report Title

## Reference Verification Report

(English) or

## Referenzprüfungsbericht

(German)


Per Reference: Individual Rating

### [N] ✅ — CORRECT
[Brief confirmation]. DOI: ... URL: ...

### [N] ⚠️ — [ERROR DESCRIPTION IN UPPERCASE]
[Explanation of the problem and correct details].
DOI: ... URL: ...

### [N] 🚨 — [ERROR DESCRIPTION IN UPPERCASE]
[Explanation; explicitly flag hallucination suspicion if applicable].
Correct details (if a similar paper was found):
DOI: ... URL: ...

Note on hallucination suspicion (🚨): If a reference cannot be found despite multiple searches and the title, journal, volume, and pages are plausible but unverifiable, always include the warning: "This appears to be a hallucinated/AI-generated reference. Do not use without verification." (or in German: "Diese Referenz scheint halluziniert/KI-generiert zu sein. Nicht ohne Überprüfung verwenden.")


Summary Table

Always append a table at the end of the report. Columns: Number | Status emoji | Main issue.

English:

## Summary Table

| # | Status | Issue |
|---|--------|-------|
| [1] | ✅ | Correct |
| [2] | ⚠️ | [Brief description] |
| [3] | 🚨 | [Brief description] |

German:

## Zusammenfassende Tabelle

| Nr. | Status | Problem |
|-----|--------|---------|
| [1] | ✅ | Korrekt |
| [2] | ⚠️ | [Kurzbeschreibung] |
| [3] | 🚨 | [Kurzbeschreibung] |

If the input was a BibTeX file, add a section with the corrected entries ready to paste (and which keys to remove).

If multiple references have 🚨 status, append a notice block at the end of the table:

> **Key concern:** References [X], [Y], [Z] bear the hallmarks of AI-generated (hallucinated)
> citations. These should be replaced with verified sources or removed before submission.

(or German equivalent)


Complete Error Category Reference

CategorySymbolTypical Cases
Correct✅All details verified
Year error⚠️Online-first vs. print year
Incomplete⚠️Missing authors, volume, pages
Non-standard⚠️URL only, no complete citation style
Typo⚠️Minor deviations in names/title
Wrong document type⚠️Patent/dissertation not identified
Wrong journal🚨Paper exists but published elsewhere
Wrong authors🚨Completely different author group
Wrong pages/article no.🚨Significant deviation
Not verifiable🚨No match; hallucination suspected
Wrong first author🚨First author does not match
Retracted🚨Retraction notice in Crossref / OpenAlex (corrections and expressions of concern: mention, ⚠️)
Wrong DOI🚨DOI resolves to a different work

Rules

  1. Always look up — run scripts/lookup.py, then search the web where needed; never assess a reference from memory, even for well-known classics.
  2. Always include DOI and URL — even for ✅ references.
  3. Never skip a reference — every entry appears in the report.
  4. Summary table is mandatory — it closes every report.
  5. Keep language consistent — English or German depending on the request, maintained throughout.
  6. For ambiguous matches try at least 3 different search strategies before assigning 🚨.
  7. Distinguish page numbers vs. article numbers correctly.
  8. Check online-first vs. print carefully — the correct citation year is the print publication year unless explicitly stated otherwise.
  9. Patents and reports follow their own citation standards: inventor, applicant, patent number, country, date.
  10. Recognize hallucination patterns: Plausible title + real journal + unverifiable pages/numbers = strong indicator of AI-generated false citation → always warn explicitly.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.