skills/utility/stage/citation-verification/SKILL.md
Verification guide for citations added during rebuttal writing. Use when Stage 2 responses introduce new references, when the Area Chair asks about a cited paper, or when any citation in the rebuttal might have been AI-generated. Prevents the serious credibility damage of fabricated references in reviewer-facing documents.
npx skillsauth add runtsang/rebuttalstudio citation-verificationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
RebuttalStudio Utility — Stage 2 / Stage 4 Apply this skill whenever a Stage 2 draft or Stage 4 follow-up response introduces a new reference — especially when the reference was suggested by an LLM. A single fabricated citation in a rebuttal can undermine the entire response's credibility.
Verification principles and workflow for citations added during the rebuttal writing process.
Rebuttal citations are uniquely dangerous compared to paper citations:
Core rule: Never add a citation to a rebuttal response unless you have personally verified it exists via search.
Verify any citation that was:
Existing citations from the paper itself generally do not need re-verification — but do confirm the claim you are citing actually appears in that work.
Use a reliable academic search engine:
Recommended search order:
1. Google Scholar (scholar.google.com)
2. Semantic Scholar (semanticscholar.org)
3. arXiv (arxiv.org) — for preprints
4. ACL Anthology (aclanthology.org) — for NLP/ACL papers
5. OpenReview (openreview.net) — for ICLR/ICML papers
Search query pattern:
"[Paper title keywords]" [first author last name] [approximate year]
Verify the paper exists by confirming:
When citing a specific finding, do not trust your memory of the paper's conclusion.
Format for use in rebuttal prose (no BibTeX needed in most rebuttal portals):
[Author et al., Year, "Title", Venue]
e.g.: [Chen et al., 2023, "LoRA: Low-Rank Adaptation of Large Language Models", ICLR]
If after searching you cannot confirm the paper exists:
Option A — Drop the citation If the claim can stand without it, remove the reference.
Option B — Hedge the claim "Prior work on [topic] (e.g., [general area]) suggests…" without citing a specific paper.
Option C — Mark for human verification If working with an LLM and you want to flag it:
[CITATION NEEDED — verify before submission: "[paper title you were trying to cite]"]
Never submit a rebuttal with a citation you have not verified, even if it sounds plausible.
| Citation Source | Risk Level | Action | |----------------|-----------|--------| | LLM-suggested reference | Very high | Always verify before including | | Recalled from memory | Medium | Verify title and year | | Copied from reviewer comment | Medium | Verify existence; reviewer may be wrong | | Already in paper's reference list | Low | Confirm the claim is in that paper | | Found via search in last 24h | Low | Cross-check author/venue |
Adapted from Claude Scholar's citation-verification skill for the rebuttal context. Original: https://github.com/Galaxy-Dawn/claude-scholar/blob/main/skills/citation-verification/SKILL.md
data-ai
Remove AI-generated writing patterns from rebuttal prose to make it sound natural, direct, and authentically human-authored. Use when a Stage 2 refined draft or Stage 4 follow-up response reads too formulaic, robotic, or "GPT-like". Supports academic English.
testing
Condense rebuttal prose into fewer words without changing the original meaning. Use when a response block, paragraph, or selected passage is too long but all technical content, citations, and commitments must stay intact. Supports academic English.
development
Systematic review response strategy guide for RebuttalStudio. Use when developing response strategies for reviewer comments, deciding how to classify concerns, or choosing between Accept/Defend/Clarify/Experiment approaches at any stage of the rebuttal pipeline.
testing
Systematic quality check for a completed rebuttal document before submission. Use after Stage 3 document compilation or after Stage 5 final remarks writing to verify completeness, tone, factual accuracy, and structural integrity. Catches common rebuttal errors before they reach reviewers.