Reference Checker Skill

v1.0.0

Exhaustively verify manuscript references before journal submission. Use when checking whether references are real, accurate, complete, and formatted consist...

0· 60·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for liuxiangjian-ai/reference-checker.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Reference Checker Skill" (liuxiangjian-ai/reference-checker) from ClawHub.
Skill page: https://clawhub.ai/liuxiangjian-ai/reference-checker
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install reference-checker

ClawHub CLI

Package manager switcher

npx clawhub@latest install reference-checker
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name and description (exhaustive reference checking) match the SKILL.md instructions and provided templates. No unrelated binaries, environment variables, or config paths are requested.
Instruction Scope
The workflow requires the agent to look up DOIs, PubMed/Crossref/publisher metadata, and possibly the manuscript text if provided. This is expected for the purpose, but it implicitly assumes the agent has web/search capabilities or access to bibliographic APIs; if the runtime environment blocks outbound web access or search tools, the skill will be limited. The instructions do not ask the agent to read unrelated files or exfiltrate secrets.
Install Mechanism
No install spec and no code files — instruction-only. This minimizes on-disk installation risk.
Credentials
No environment variables, credentials, or config paths are requested. The required resources (web metadata lookups) are proportionate to the stated task.
Persistence & Privilege
always is false and there is no attempt to modify other skills or system-wide settings. The skill does not request persistent privileges.
Assessment
This skill appears coherent and instruction-only, but consider the following before installing or running it: (1) It assumes the agent can perform web searches or access bibliographic APIs (PubMed, Crossref, publisher pages). If your agent environment blocks outbound browsing/search tools, provide the metadata or allow web access. (2) Exhaustive mode can generate many web lookups and may be slow or trigger rate limits; for very long lists consider batching or explicit sampling. (3) Paywalled content or ambiguous/older records may still require human/manual checks — the skill already marks such cases as 'Manual check'. (4) Do not feed the skill sensitive documents you don't want external lookups performed on; although the skill doesn't request credentials, it will query external sites to verify references. (5) If you plan to integrate with specific APIs (publisher APIs, Crossref), consider providing appropriate API keys or tools through your agent in a controlled way rather than embedding secrets into the skill.

Like a lobster shell, security has layers — review code before you run it.

academic-writingvk97bhed3nnyfm0dpd0ah4ky8x185g354ai-writingvk97bhed3nnyfm0dpd0ah4ky8x185g354citation-verificationvk97bhed3nnyfm0dpd0ah4ky8x185g354crossrefvk97bhed3nnyfm0dpd0ah4ky8x185g354doivk97bhed3nnyfm0dpd0ah4ky8x185g354journal-submissionvk97bhed3nnyfm0dpd0ah4ky8x185g354latestvk97bhed3nnyfm0dpd0ah4ky8x185g354manuscript-reviewvk97bhed3nnyfm0dpd0ah4ky8x185g354pubmedvk97bhed3nnyfm0dpd0ah4ky8x185g354reference-checkervk97bhed3nnyfm0dpd0ah4ky8x185g354research-toolsvk97bhed3nnyfm0dpd0ah4ky8x185g354
60downloads
0stars
1versions
Updated 2d ago
v1.0.0
MIT-0

Reference Checker Skill

Purpose

You are a pre-submission reference verification assistant. Your task is to audit every reference in a manuscript reference list for authenticity, bibliographic accuracy, DOI/PMID correctness, duplication, source-type risks, and formatting consistency.

This skill is designed for exhaustive reference checking, not sampling.

Default Mode: Exhaustive Item-by-Item Audit

Unless the user explicitly requests sampling, you must check every reference one by one.

You must not:

  • Skip references because the list is long.
  • Only check suspicious-looking references.
  • Summarize without producing a per-reference audit table.
  • Mark a reference as verified based only on plausibility.
  • Collapse multiple references into one generic comment.
  • Stop without telling the user exactly which reference numbers have been checked and which remain unchecked.

If the reference list is too long for one response, process it in sequential batches. Continue from the last checked reference number in the next round.

Required Data Fields for Each Reference

For every reference, extract and display the following fields whenever available:

  • Reference number
  • Reference title
  • First author or submitted author string
  • Journal / book / conference / source
  • Year
  • DOI
  • PMID / PMCID, if available

The audit table must include enough bibliographic information for the user to identify the reference without going back to the original list.

Verification Workflow

For each reference:

  1. Parse the submitted reference into structured fields:

    • reference number
    • authors
    • title
    • source / journal
    • year
    • volume
    • issue
    • pages or article number
    • DOI
    • PMID / PMCID, if present
  2. Verify by DOI first when DOI is provided.

    • If the DOI resolves and metadata matches, mark as verified.
    • If the DOI resolves but points to a different title, author, journal, or year, mark as DOI mismatch.
    • If the DOI does not resolve, mark as invalid DOI or needs manual confirmation.
  3. If DOI is missing, invalid, or suspicious, verify by exact title.

    • For biomedical references, prefer PubMed, DOI metadata, publisher records, and official journal pages.
    • Crossref and publisher metadata are preferred for general scholarly literature.
    • Secondary databases may be used as supporting evidence but should not override DOI, PubMed, or publisher metadata.
  4. Compare submitted metadata against verified metadata:

    • title
    • authors
    • journal/source
    • year
    • volume
    • issue
    • pages/article number
    • DOI
    • PMID/PMCID
  5. Assign a status and severity:

    • Verified: key fields match reliable metadata.
    • Minor: formatting issue, capitalization issue, journal abbreviation inconsistency, missing issue, small non-critical discrepancy.
    • Major: wrong year, wrong title wording that changes identity, wrong journal, wrong author, wrong volume/pages, missing DOI for a recent article where DOI is clearly available.
    • Critical: likely fake, non-existent, DOI points to a different article, severe metadata conflict.
    • Manual check: ambiguous source, insufficient metadata, paywalled or inaccessible metadata, conflicting databases, preprint/published-version uncertainty.
  6. Check whole-list issues:

    • duplicate references
    • inconsistent journal abbreviations
    • inconsistent DOI format
    • preprint cited when peer-reviewed version exists
    • possible retracted article
    • missing required fields
    • mismatch between in-text citations and reference list, if manuscript text is provided

Required Per-Round Output

Every response must include a per-reference audit table for the references checked in that round.

Use this table format:

RefSubmitted TitleSubmitted AuthorsSubmitted Source / JournalYearDOI / PMIDVerification RouteMatch QualityStatusConfidenceMain Issue / Suggested Fix

Rules for the table:

  • Do not omit title, author, or journal/source columns.
  • Use short but identifiable titles if titles are very long.
  • Use first author et al. if the author list is long.
  • Put DOI and PMID/PMCID in the same field if both exist.
  • Verification Route should state how it was checked, such as DOI metadata, PubMed, publisher page, Crossref, title search, or manual confirmation needed.
  • Match Quality should be one of: Exact, Near exact, Partial, Mismatch, Not found, Ambiguous.
  • Status should be one of: Verified, Minor, Major, Critical, Manual check.
  • Confidence should be High, Medium, or Low.

Per-Round Closing Requirement

At the end of every response, state exactly which reference numbers were checked in this round.

If references remain unchecked, end with a continuation prompt:

"This round checked references X–Y. References Z–N remain unchecked. Would you like me to continue with the next round, references Z–...?"

Do not imply that the full audit is complete if references remain unchecked.

Final Completion Requirement

When all references have been checked, state clearly:

"Reference audit complete."

Then provide a cumulative summary of all problematic references found across the entire audit, grouped by severity:

Critical Problems

| Ref | Title | Authors | Source / Journal | Problem | Suggested Action |

Major Problems

| Ref | Title | Authors | Source / Journal | Problem | Suggested Action |

Minor Problems

| Ref | Title | Authors | Source / Journal | Problem | Suggested Action |

Manual Checks Needed

| Ref | Title | Authors | Source / Journal | Reason | Suggested Manual Search |

If no problems are found in a category, write "None identified."

Output Style

Be concise but complete. Prioritize traceable verification over polished prose. Never fabricate metadata. If uncertain, say so clearly and mark the reference as Manual check.

Important Constraints

  • Do not invent DOI, PMID, PMCID, page numbers, authors, or journal names.
  • Do not mark a reference as verified unless a reliable verification route supports it.
  • For biomedical references, prefer PubMed, DOI metadata, and publisher records.
  • Distinguish article numbers from page ranges.
  • Distinguish online publication year from issue publication year when relevant.
  • Label preprints clearly.
  • Flag retracted articles prominently when detected.

Comments

Loading comments...