Use when creating or configuring Claude Code agents and their frontmatter.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how to verify references", "preventing fake citations", or needs guidance on citation accuracy. This skill supports ml-paper-writing by providing detailed verification principles and common error patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
A reference guide for citation verification in academic paper writing, providing verification principles and best practices.
Core Principle: Proactively verify every citation during the writing process using programmatic or canonical scholarly sources first: arXiv, DOI/CrossRef, Semantic Scholar, publisher landing pages, and Zotero metadata. Google Scholar is useful for manual discovery, but it is not the canonical verification authority.
Citation issues in academic papers seriously impact research integrity:
These issues can lead to:
Special risk with AI-assisted writing: AI-generated citations have approximately 40% error rate; every citation must be verified via WebSearch.
This skill provides verification principles based on canonical scholarly metadata and claim-level checking:
Core idea: Verify immediately when adding a citation, rather than checking after writing is complete.
Preferred authority order:
Verification steps:
Information that must match:
Key principle: When citing a specific claim, you must confirm the claim actually appears in the paper.
Need a citation during writing
↓
Find DOI / arXiv ID / publisher page / verified Zotero item
↓
Verify metadata with CrossRef / arXiv / Semantic Scholar / publisher / Zotero
↓
Confirm paper details
↓
Get BibTeX
↓
(If citing a specific claim) Verify the claim
↓
Add to bibliography
Key point: Verification is part of the writing process, not a separate post-processing step.
The verification principles of this skill are integrated into the Citation Workflow of the ml-paper-writing skill.
Auto-trigger: Citation verification is automatically executed when writing papers with the ml-paper-writing skill.
Manual reference: Refer to this skill when you need detailed verification principles.
Scenario: Need to cite the Transformer paper
Step 1: WebSearch lookup
Query: "Attention is All You Need Vaswani 2017"
Result: Found multiple sources for the paper
Step 2: Google Scholar verification
Query: "site:scholar.google.com Attention is All You Need Vaswani"
Result: ✅ Paper exists, 50,000+ citations, NeurIPS 2017
Step 3: Confirm details
- Title: "Attention is All You Need"
- Authors: Vaswani, Ashish; Shazeer, Noam; Parmar, Niki; ...
- Year: 2017
- Venue: NeurIPS (NIPS)
Step 4: Get BibTeX
- Click "Cite" on Google Scholar
- Select BibTeX format
- Copy BibTeX entry
Step 5: Add to bibliography
- Paste into .bib file
- Use \cite{vaswani2017attention} in the paper
If the paper cannot be verified through canonical sources:
[CITATION NEEDED] markerIf information doesn't match:
[CITATION NEEDED] to mark explicitly❌ Wrong approach:
✅ Correct approach:
Core Principle: Proactively verify every citation during the writing process using WebSearch and Google Scholar.
Key Steps:
Failure handling: When verification fails, mark as [CITATION NEEDED] and clearly notify the user.
Integration: The principles of this skill are integrated into the ml-paper-writing skill for automatic verification.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Use when creating or configuring Claude Code agents and their frontmatter.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use only when creating new registrable ML components that require Factory or Registry patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "debug this", "fix this error", "investigate this bug", "troubleshoot this issue", "find the problem", "something is broken", "this isn't working", "why is this failing", or reports errors/exceptions/bugs. Provides systematic debugging workflow and common error patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for everyday coding tasks that involve writing or modifying source code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.