validate_paper_links — paper link validation techniques validate_paper_links, claudsidian, community, paper link validation techniques, ide skills, install validate_paper_links, validate_paper_links for researchers, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Ideal for Research Agents requiring accurate citation and reference validation in academic papers. validate_paper_links is a skill that validates paper links in notes against actual paper references and citations to prevent errors and inconsistencies.

Features

Validates [[Paper Title]] links against actual paper references
Prevents links to papers not referenced in the current paper (hallucination)
Checks for incorrect paper titles or formatting
Filters out links to low-influence papers (cited once, not foundational)
Replaces colon (:) with hyphen (-) in file names to prevent broken links

# Core Topics

D0miH D0miH
[0]
[0]
Updated: 3/8/2026

Agent Capability Analysis

The validate_paper_links skill by D0miH is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance. Optimized for paper link validation techniques, install validate_paper_links, validate_paper_links for researchers.

Ideal Agent Persona

Ideal for Research Agents requiring accurate citation and reference validation in academic papers.

Core Value

Empowers agents to verify paper links against actual references and citation patterns, preventing hallucinations and ensuring correct titles and formatting using protocols like citation analysis and reference checking.

Capabilities Granted for validate_paper_links

Validating paper links in research notes
Preventing incorrect title formatting in citations
Identifying low-influence papers with minimal citations

! Prerequisites & Limits

  • Requires access to paper references and citation data
  • Limited to papers with available citation patterns
  • May not handle broken file names without additional processing
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

validate_paper_links

Discover how validate_paper_links prevents hallucinations, incorrect titles, and broken file names in paper notes. Learn how to set up this AI agent skill...

SKILL.md
Readonly

Validate all [[Paper Title]] links in a paper note against the actual paper's references and citation patterns.

Goal: Prevent:

  1. Links to papers NOT referenced in the current paper (hallucination)
  2. Links to papers with incorrect titles or formatting
  3. Links to low-influence papers (cited once, not foundational)
  4. Broken file names (: not exchanged to -)

CRITICAL RULES

A link should exist only if:

  1. ✅ The paper IS referenced in the current paper's bibliography/references
  2. ✅ The paper is INFLUENTIAL (cited ≥2 times OR explicitly foundational/cited in intro/abstract)
  3. ✅ Title is in exact Title Case matching the reference
  4. ✅ File name properly formats : as - (e.g., Attention - Is All You Need)

A link should be removed if:

  • ❌ Paper is NOT in the current paper's references
  • ❌ Paper is cited only once in methods/results (low influence)
  • ❌ Title formatting is incorrect
  • ❌ File name violates naming convention

WORKFLOW

0. Read last-run timestamp

Read .claude/vault_maintanance.md and note the validate_paper_links: timestamp.

Default: incremental scan — only validate papers in Reading/ modified after the validate_paper_links: timestamp. Use find Reading/ -newer <reference_file> to identify changed paper notes. To use a reference file: touch -t YYYYMMDDHHMI /tmp/validate_ref && find Reading/ -newer /tmp/validate_ref

  • If no papers were modified: skip and report "All paper links already validated."
  • Only run a full rescan if the user explicitly requests it or no timestamp exists yet.

1. Get paper and note details

Read the paper note and extract:

  • Paper URL: From frontmatter (arXiv HTML URL preferred)
  • Paper title: From frontmatter or file name
  • Authors: From frontmatter (if available)
  • Year: From frontmatter (if available)

2. Fetch references section from arXiv HTML

Access paper:

  • Use paper URL from frontmatter (typically https://arxiv.org/html/[paper-id]v[version])
  • Use WebFetch with prompt focused only on references section
  • Skip all paper content (abstract, introduction, methods, results, etc.)
  • Extract only the bibliography/references section

Extract citation data:

  • Parse reference list to get: titles, authors, years
  • Build structured reference list from bibliography section
  • Reference section is clearly marked on arXiv HTML pages

WebFetch optimization:

  • Prompt: "Extract ONLY the bibliography/references section. Ignore all other paper content (abstract, introduction, methods, results). Return reference titles, authors, and years."
  • This signals to skip 90% of paper content and focus only on references
  • Saves tokens by not parsing paper text

Why arXiv HTML:

  • ✅ Direct access to paper bibliography
  • ✅ Pre-formatted references (easy to extract)
  • ✅ No API rate limiting or authentication
  • ✅ Reliable and consistent structure across papers
  • ✅ No JavaScript rendering issues
  • ✅ Can optimize WebFetch to skip content (token savings)

3. Read paper note

  • Open paper note from Reading/[filename].md
  • Extract all [[Paper Title]] links from "🔗 Connections to Other Work" section
  • Build link list with current formatting

For each [[Paper Title]] in the note:

Check 1: Reference exists?

  • Does this paper appear in the current paper's bibliography?
  • If NO → FLAG: "Not referenced in paper" (candidate for removal)
  • If YES → PASS

Check 2: Influence level

  • Count how many times the paper is cited in the current paper's text
  • Referenced paper with ≥2 citations in this paper = influential ✓
  • Referenced paper cited once but foundational (cited in abstract/intro)? = influential ✓
  • Referenced paper cited only once in methods/results (low-impact section)? = LOW influence (candidate for removal)
  • If influence is borderline → ask user for judgment

Check 3: Title formatting

  • Compare link title against reference list title
  • Is it Title Case?
  • Are colons : present in reference but - in link?
  • Are special characters consistent?
  • If mismatch → FLAG: "Title mismatch" or "Formatting error"

Check 4: File name validity

  • Expected file name: exact title with :-
  • Is current link pointing to correct file name?
  • Example: [[Attention - Is All You Need]] should match file Attention - Is All You Need.md
  • If mismatch → FLAG: "File name doesn't match link"

5. Generate validation report

Group findings by severity:

🔴 CRITICAL (remove immediately):

  • Papers not in references
  • Papers cited only once in low-importance sections

🟡 NEEDS FIXING:

  • Title case errors
  • File name formatting errors (: not converted to -)

🟢 OK:

  • Papers properly referenced
  • Properly formatted
  • Appropriately influential

❓ NEEDS USER JUDGMENT:

  • Papers cited ~2 times (borderline influence)
  • Foundational papers cited rarely but in key sections

6. Apply fixes

With user approval:

  • Remove links: Delete [[Paper Title]] lines from "🔗 Connections to Other Work"
  • Fix titles: Correct Title Case and formatting to match references
  • Fix file names: Ensure :- conversion
  • Update note: Save corrected paper note
  • Verify: Re-scan to confirm all links now valid

7. Update vault_maintanance.md

After completing validation (regardless of whether fixes were applied):

  • Run date via Bash to get the current system time
  • Read .claude/vault_maintanance.md
  • Update validate_paper_links: line to current date and time in format DD-MM-YYYY HH:MM
  • Reset papers_since_validate_links: to 0
  • Write the updated file

Example update:

validate_paper_links: 10-02-2026 14:35

TOKEN EFFICIENCY

Optimizations:

  • arXiv HTML for direct bibliography access (single WebFetch call)
  • References-only extraction via targeted WebFetch prompt
  • Skip all paper content (abstract, intro, methods, results)
  • Bibliography section clearly marked and easy to extract
  • No API calls, no rate limiting, no authentication needed
  • Direct title + author list from bibliography
  • Build simple title→reference mapping

Why this is efficient:

  • 1 WebFetch call to arXiv HTML (direct paper access via frontmatter URL)
  • Targeted prompt skips 90% of paper content (saves major tokens)
  • Bibliography section is well-formatted and clearly delimited
  • No API dependencies or rate limiting concerns
  • Minimal parsing needed (just extract reference titles)
  • No ambiguity in reference data

Workflow:

  1. Read paper note frontmatter for arXiv HTML URL
  2. WebFetch the arXiv HTML page with prompt: "Extract ONLY bibliography/references section. Skip all other content."
  3. Extract bibliography/references section
  4. Build reference list from bibliography
  5. Validate links against reference list

Avoid:

  • Semantic Scholar (JavaScript rendering, rate limiting issues)
  • PDF parsing
  • Regex patterns for extraction (bibliography is already structured)
  • Processing full paper text (use targeted prompt instead)

Expected cost: ~100-150 tokens per paper (1 optimized WebFetch call + validation)


OUTPUT RULES

  • Grouped by severity (CRITICAL → needs fixing → OK)
  • File name / Link text / Issue / Suggested fix
  • No prose, bullets only
  • Example:
🔴 CRITICAL (remove):
- [[Paper Not In References]] - Not in bibliography → REMOVE

🟡 NEEDS FIXING:
- [[attention is all you need]] - Title case error → Fix to [[Attention Is All You Need]]
- [[My Paper: A Study]] - File name formatting → Should be [[My Paper - A Study]]

🟢 OK (keep):
- [[Transformers are All You Need]] ✓

SELF-CHECK

✅ Did I fetch the arXiv HTML page from the frontmatter URL? ✅ Did I extract all references from the bibliography section? ✅ Did I extract reference metadata (title, authors, year)? ✅ Did I check each link against the bibliography references? ✅ Did I assess influence (citation count/context in paper)? ✅ Did I validate Title Case formatting against bibliography titles? ✅ Did I check file name convention (: → -)? ✅ Did I group findings by severity? ✅ Did I get user approval before removing links? ✅ Did I verify all remaining links are valid? ✅ Did I update vault_maintanance.md with current timestamp?

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is validate_paper_links?

Ideal for Research Agents requiring accurate citation and reference validation in academic papers. validate_paper_links is a skill that validates paper links in notes against actual paper references and citations to prevent errors and inconsistencies.

How do I install validate_paper_links?

Run the command: npx killer-skills add D0miH/claudsidian. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for validate_paper_links?

Key use cases include: Validating paper links in research notes, Preventing incorrect title formatting in citations, Identifying low-influence papers with minimal citations.

Which IDEs are compatible with validate_paper_links?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for validate_paper_links?

Requires access to paper references and citation data. Limited to papers with available citation patterns. May not handle broken file names without additional processing.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add D0miH/claudsidian. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use validate_paper_links immediately in the current project.

Related Skills

Looking for an alternative to validate_paper_links or another community skill for your workflow? Explore these related open-source skills.

View All

widget-generator

Logo of f
f

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete privacy.

149.6k
0
AI

flags

Logo of vercel
vercel

flags is a Next.js feature management skill that enables developers to efficiently add or modify framework feature flags, streamlining React application development.

138.4k
0
Browser

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
AI

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
AI