citation-verification
Skill4 starsChanged 40 days agoMITView on GitHub
Verify citation metadata and support for manuscript claims during drafting or pre-submission; never invent references.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- shkodnik1917/claude-brainlabtheir own version, first seen Nov 8, 2026
- Vepricov/claude-brainlabtheir own version, first seen Nov 1, 2026
- GoogleCloudPlatform/LifeSciencestheir own version, first seen Oct 13, 2026
- terravic/pde-agent-plugintheir own version, first seen Oct 11, 2026
- Niko-mzz/Doctor-Ge-SCI-paper-Writingtheir own version, first seen Oct 8, 2026
- neelshah4/claude-citation-verificationtheir own version, first seen Sep 24, 2026
Used with
Projects with it also use results-report, daily-coding and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Galaxy-DawnSkillresults-report
This skill should be used when the user asks to "write an experiment report", "summarize experimental results", "do experiment retrospection", "write a results report", "写实验总结报告", "写实验复盘", or mentions turning completed experiment artifacts into a structured, decision-oriented research report. It assumes strict analysis should come from `results-analysis` first.
Also in 3 projects that use this
Clay-HHKSkilldaily-coding
Daily coding assistant that auto-triggers when writing/modifying code, providing a core checklist.
Also in 3 projects that use this
Clay-HHKSkillkaggle-learner
This skill should be used when the user asks to "learn from Kaggle", "study Kaggle solutions", "analyze Kaggle competitions", or mentions Kaggle competition URLs. Provides access to extracted knowledge from winning Kaggle solutions across NLP, CV, time series, tabular, and multimodal domains.
Also in 3 projects that use this
kharlamenkodevSkillbug-detective
Also in 3 projects that use this
MicrosoftSkillweb-design-reviewer
This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level.
Also in 4 projects that use this
AnthropicSkillcommand-development
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
Also in 3 projects that use this
- +2 more from Clay-HHK
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- Galaxy-Dawn/claude-scholar★ 5.9ksame name
- GoogleCloudPlatform/LifeSciences★ 58same name
- shkodnik1917/claude-brainlab★ 36same name
- Vepricov/claude-brainlab★ 35same name
- koach08/claude-code-skills★ 4same name
- Niko-mzz/Doctor-Ge-SCI-paper-Writing★ 4same name
- AllanWessels/Bratan★ 2same name
- Clay-HHK/claude-skills★ 1same name
- earthskyisbig/auction-law★ 1same name
- neelshah4/claude-citation-verification★ 0same name
1 more not listed
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 repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- academic-humanizerSkill
- claim-numerics-auditSkill
- cover-letterSkill
- experiment-planSkill
- experiment-runnerSkill
- journal-scoutSkill
- paper-auditSkill
- paper-illustrationSkill
- paper-planSkill
- paper-writeSkill
- research-data-auditSkill
- research-ideationSkill
- research-publicationSkill
- research-quality-gateSkill
- research-refineSkill
- result-to-claimSkill
- scientific-figure-makingSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Verify each reference as both a bibliographic record and evidence for the sentence that cites it.
- Very specific: line 10
Read the manuscript, bibliography, and any existing Evidence ID records.
- Distinctive: line 19
Prefer the canonical DOI/publisher record for final metadata.
- Distinctive: line 21
Keep discovery, bibliographic verification, lawful full-text acquisition, local parsing, and note storage as distinct provenance steps.
- Distinctive: line 22
Do not require a particular search engine, citation count, or fixed author-year tolerance.
- Distinctive: line 23
Do not edit prose, BibTeX, or claims unless the user separately asks for the correction.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Citation Verification
Verify each reference as both a bibliographic record and evidence for the sentence that cites it.
- Read the manuscript, bibliography, and any existing
Evidence IDrecords. Build a list of unique citation keys and each location where a specific scientific claim relies on one. - Resolve metadata through primary or authoritative scholarly records (for example DOI registration, publisher, conference proceedings, arXiv for its own version, or Research Core). Check title, authors, venue, year, identifier, and the cited version.
- For a claim-dependent citation, inspect the source itself and record the supporting section, table, figure, or page when available. Metadata alone does not verify that the source supports a claim.
- Mark every entry
verified,metadata-only,claim-not-supported,unresolved,conflicted, orreplace/remove. Never infer missing metadata or fabricate a replacement citation. - For consequential sources, preserve the canonical identifier and version, retrieval date/route, exact support location, and local artifact/hash when one exists. Obsidian or another note system may link the record, but it does not replace the original source or verification status.
- Record results in
docs/11_pre_submission_audit.mdunder “引文核验”; preserve uncertain entries for author decision.
Rules
- Prefer the canonical DOI/publisher record for final metadata; record preprint-versus-publication differences explicitly.
- A literature search result, abstract-only record, or citation count can discover a source but cannot substantiate a detailed technical claim.
- Keep discovery, bibliographic verification, lawful full-text acquisition, local parsing, and note storage as distinct provenance steps. Report a missing capability rather than silently changing the evidence route.
- Do not require a particular search engine, citation count, or fixed author-year tolerance.
- Do not edit prose, BibTeX, or claims unless the user separately asks for the correction.
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
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.

