Citation Verification Guide
Galaxy-Dawn/claude-scholar
Reference guidance for checking every citation in academic writing against canonical sources such as DOI, arXiv, CrossRef and Semantic Scholar, to catch fake or wrong references.
Assess and promote corpus slices toward citation readiness. An agent skill from scholay/skills.
Install Evidence Review
$ npx skills add scholay/skills --skill evidence-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install scholay/skills evidence-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/scholay/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/evidence-review .claude/skills/evidence-review && rm -rf skills-srcUse ~/.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/
Install the "evidence-review" agent skill from https://github.com/scholay/skills/tree/main/evidence-review into .claude/skills/evidence-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evidence-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/scholay/skills/tree/main/evidence-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add scholay/skills --skill evidence-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install scholay/skills evidence-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scholay/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/evidence-review .agents/skills/evidence-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "evidence-review" agent skill from https://github.com/scholay/skills/tree/main/evidence-review into .agents/skills/evidence-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evidence-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add scholay/skills --skill evidence-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install scholay/skills evidence-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scholay/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/evidence-review .cursor/skills/evidence-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "evidence-review" agent skill from https://github.com/scholay/skills/tree/main/evidence-review into .cursor/skills/evidence-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evidence-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/scholay/skills.git --path evidence-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add scholay/skills --skill evidence-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install scholay/skills evidence-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scholay/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/evidence-review .gemini/skills/evidence-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "evidence-review" agent skill from https://github.com/scholay/skills/tree/main/evidence-review into .gemini/skills/evidence-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evidence-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install scholay/skills evidence-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add scholay/skills --skill evidence-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/scholay/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/evidence-review .github/skills/evidence-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "evidence-review" agent skill from https://github.com/scholay/skills/tree/main/evidence-review into .github/skills/evidence-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evidence-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add scholay/skills --skill evidence-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install scholay/skills evidence-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scholay/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/evidence-review .opencode/skills/evidence-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "evidence-review" agent skill from https://github.com/scholay/skills/tree/main/evidence-review into .opencode/skills/evidence-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "evidence-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
evidence-review- GitHub stars
- 141
- Token cost
- ~1.1k tokens
- SKILL.md length
- 550 words
- Files
- 2 (incl. references)
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Assess and promote corpus slices toward citation readiness. An agent skill from scholay/skills.
- Works in 4 steps: Prioritize what to review → Per-slice review procedure → Maintain an evidence matrix → …
- Deciding whether a piece of evidence can be cited
- SKILL.md covers The core problem, The citation readiness ladder, Workflow and Rules, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Evidence Review is an agent skill from scholay/skills. Assess and promote corpus slices toward citation readiness. Use when deciding whether a piece of evidence can be cited, upgrading machine-translated layers to reviewed translations, building evidence matrices for writing, or prioritizing which sources to review first.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/citation-criteria.md`).
It sits in Research & Science, covering Fact-checking and source verification, Translation and Citation management. The repository describes itself as: Open academic AI skills maintained by Scholay. The licence is MIT.
When your agent uses it
- Deciding whether a piece of evidence can be cited
- Upgrading machine-translated layers to reviewed translations
- Building evidence matrices for writing
- Prioritizing which sources to review first
Example prompts
- “/evidence-review”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cd61bd9. 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
Evidence Review loads about 1.1k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 71 tokens; SKILL.md has 550 words of instructions outside code blocks.
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 scholay/skills at commit cd61bd9, republished under its MIT licence (© scholay). 550 words, ~1,064 tokens.
Download SKILL.mdSave it as
.claude/skills/evidence-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- evidence-review
- description
- Assess and promote corpus slices toward citation readiness. Use when deciding whether a piece of evidence can be cited, upgrading machine-translated layers to reviewed translations, building evidence matrices for writing, or prioritizing which sources to review first.
Evidence Review
The core problem
Most corpus slices are created by automated pipelines: OCR, machine translation, auto-generated descriptions. They are useful for browsing, but not safe to cite. The gap between "we have 10,000 slices" and "we can write the paper" is evidence review — the deliberate process of deciding which slices are trustworthy enough to quote and cite.
Without a clear ladder between "raw" and "citation-ready," researchers either over-trust machine output or spend time reviewing everything equally. Neither is efficient.
The citation readiness ladder
| Level | Status | What it means |
|---|---|---|
| 0 | draft | Auto-generated, not yet looked at by a human |
| 1 | checked | Source text verified against the original document |
| 2 | reviewed | Working translation confirmed accurate; can be paraphrased safely |
| 3 | quote_ready | Can be quoted or cited directly; citekey and page locator confirmed |
Only level 3 slices should appear as direct citations in writing. Level 2 is sufficient for paraphrase and synthesis.
The key insight: levels 0 and 1 are about accuracy of the source text. Levels 2 and 3 are about the translation/working layer. They are separate judgments.
Workflow
1. Prioritize what to review
Don't review everything. Identify which slices are thesis-critical first:
- Slices already referenced in your writing or notes
- Slices from your highest-value sources
- Slices that answer your core research questions directly
For each priority cluster, look at quality scores from corpus building (P1 pages need review before any other use; P2 should be sampled).
2. Per-slice review procedure
For each slice you're reviewing:
- Open the original source page alongside the slice card.
- Verify that the source text (original excerpt or OCR text) accurately represents the page. Correct OCR errors if found.
- Set
verification_status: checkedwhen source text is confirmed. - Review the working translation: does it accurately convey the source meaning? Correct or rewrite as needed.
- Set
translation_status: reviewedwhen the working layer is trusted. - If this slice is suitable for direct quotation or citation:
- Confirm the citekey exists in your bibliography
- Confirm the page locator is correct
- Set
quote_ready: true
Show full SKILL.md (212 more words)Show less
3. Maintain an evidence matrix
For each chapter or section you're writing, keep a simple matrix:
| Slice ID | Chapter | Section | Role | Status | Notes |
|---|---|---|---|---|---|
| SLC-0001-T003 | Ch2 | 2.1 | supports claim about X | reviewed | paraphrase only |
| SLC-0007-T012 | Ch3 | 3.2 | direct quotation | quote_ready | cite p.47 |
This makes the link between your argument and your evidence explicit and checkable.
4. Run the integrity check before writing
Before each writing session, verify:
- Every slice you plan to cite has at least
verification_status: checked - Every slice you plan to quote directly has
quote_ready: true - Every citekey in your evidence matrix resolves in your bibliography
Rules
- Do not promote a slice to
quote_readybased on quality scores alone. Human review of both source text and translation is required. - Do not cite from
machine_draftoragent_drafttranslation layers directly. These are working materials, not citation materials. - Separate source text accuracy from translation accuracy — they are different judgments, made at different stages.
- A slice at
reviewedlevel is safe to paraphrase. A slice atquote_readylevel is safe to quote. - When you first use a slice in writing, add it to the evidence matrix immediately.
- OCR-assisted image descriptions (
ocr_assisted_draft) are not citation-ready visual evidence.
References
- Read
references/citation-criteria.mdfor the full checklist of what each ladder level requires for text and image slices.
© scholay, 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 1 other file (references) in evidence-review of scholay/skills.
- SKILL.md
- references/citation-criteria.md
Open the folder on GitHubat commit cd61bd9
Compare with similar skills
Evidence Review 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Evidence Review this skillscholay/skills | 141 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Citation Verification GuideGalaxy-Dawn/claude-scholar | 5.7k | 2 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Article Fact Checkerdigoal/blog | 8.6k | — | ~939 | Automated safety check: Pass | GPL-2.0 | |
| Citation VerificationLight0305/Light-skills | 640 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Zotero Literature Visualizerxuezheng627/zotero-literature-visualizer | 104 | — | ~2k | Automated safety check: Pass | MIT | |
| Grounded CitationsNousResearch/hermes-agent | 253k | — | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
Article Fact Checker
digoal/blog
三层审查模型,逐段逐句验证文章真伪、证据链与逻辑结构。Use when the user asks to fact-check, verify, audit, or evaluate the credibility of an article, essay, report, opinion piece, social-media post, or any written claim —…
Citation Verification
Light0305/Light-skills
Verifies that every reference in a manuscript is real, correctly identified and actually supports its claim, and produces a citation registry for typesetting.
Zotero Literature Visualizer
xuezheng627/zotero-literature-visualizer
Build evidence-aware bilingual literature reviews and interactive dashboards from a local Zotero library or a new topic search.
Grounded Citations
NousResearch/hermes-agent
Attaches a numbered, URL-backed citation to every outside fact in an answer or document, rejecting quotes that aren't real.
Paper Skill
cLin-c/paper-skill
End-to-end, Chinese-first academic research and publication workflow for reading papers, literature reviews, research framing, manuscript planning and writing, Chinese-English translation, LaTeX…
More from scholay/skills
Corpus Building
scholay/skills
Extract, structure, and quality-check evidence from registered source objects.
Literature Discovery
scholay/skills
Systematically discover and shortlist academic literature for a research project.
Research Writing
scholay/skills
Draft and maintain academic papers from verified corpus evidence, manage bibliography, and produce output in any target format.
Source Intake
scholay/skills
Organize, classify, and register raw research materials into a stable, trackable source layer.
Related
Categories
Questions about Evidence Review
What does Evidence Review do?
Assess and promote corpus slices toward citation readiness. An agent skill from scholay/skills. Evidence Review is an agent skill from scholay/skills. Assess and promote corpus slices toward citation readiness.
When should I use Evidence Review?
Evidence Review fits situations like: deciding whether a piece of evidence can be cited; upgrading machine-translated layers to reviewed translations; building evidence matrices for writing; prioritizing which sources to review first.
How do I install Evidence Review in Claude Code?
Run `npx skills add scholay/skills --skill evidence-review -a claude-code`. Or copy the skill folder (evidence-review in scholay/skills) into .claude/skills/evidence-review in your project. Claude Code loads it when a task matches its description.
How do I install Evidence Review in Codex?
Run `npx skills add scholay/skills --skill evidence-review -a codex`. Or copy the skill folder (evidence-review in scholay/skills) into .agents/skills/evidence-review in your project. Codex loads it when a task matches its description.
Can I use Evidence Review 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 scholay/skills --skill evidence-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/evidence-review, .gemini/skills/evidence-review, .github/skills/evidence-review and .opencode/skills/evidence-review in your project.
What does Evidence Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Evidence Review is instructions for the agent only.
Does Evidence Review 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 Evidence Review 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 Evidence Review use?
Evidence Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Evidence Review use?
About 1.1k tokens (SKILL.md is roughly 4.3k 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 905 tokens, read only when the agent opens those files.
What are the alternatives to Evidence Review?
Skills that share tags, products or a category with Evidence Review: Citation Verification Guide (Galaxy-Dawn/claude-scholar, 5.7k stars), Article Fact Checker (digoal/blog, 8.6k stars), Citation Verification (Light0305/Light-skills, 640 stars) and Zotero Literature Visualizer (xuezheng627/zotero-literature-visualizer, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Evidence Review?
scholay (a GitHub user) maintains it in scholay/skills, which has 141 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on June 17, 2026.
Source: scholay/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.