RW Citation Audit

Initiation

1. Read

   references/standalone.md

   ,

   references/method.md

   and

   references/standards.md

   .
2. Read the materials provided by the user in this session; if no materials are provided, only complete the parts allowed by the current evidence.
3. Retrieve

   references/atoms.jsonl

   when rule judgment is required; read

   references/cases.md

   when encountering similar tasks.
4. Read

   references/domain-guide.md

   when selecting methods or tools, and use

   assets/worksheet.md

   to organize deliverables.
5. Read

   references/acceptance.md

   .

   references/behavior-tests.json

   is only used for testing and not as factual information for user tasks.
6. When current literature, APIs, report specifications, and journal requirements may change, verify and record the date by accessing the official links in

   references/source-map.md

   .

Work Phases

1. Confirm the manuscript version, citation format, reference boundaries, and allowed metadata sources.
2. Establish a bidirectional correspondence table between in-text citations and references.
3. Verify author names, years, titles, sources, DOIs, and publication status.
4. Check disambiguation of authors with the same surname, same authors in the same year, and same first authors in the same year according to the specified format.
5. Check sorting, duplicates, missing fields, DOI specifications, and in-text citation formats.
6. Classify issues into BLOCK, REVIEW, and PASS, and transfer claim support issues to rw-claim-audit.

Operating Rules

• Source existence, source support for claims, and correct citation format are three separate issues to verify respectively.
• Citation format rules must come from the user-specified style guide, institutional requirements, or current rules of the target journal.
• Initials for authors with the same surname, letter suffixes for the same authors in the same year, and author expansions for the same first authors in the same year are handled according to the specified format.
• Each in-text citation should link back to a reference entry, and each item in the references should also indicate whether it is used in the main text.
• DOIs are standardized first before checking for duplicates; DOIs are not guessed based on titles.
• Crossref, ORCID, and publisher metadata can be cross-checked, but a single metadata source may be incomplete.
• Formal titles, author spellings, and journal names are not localized.
• Reference sorting and punctuation checks cannot replace author identity verification.
• Corporate authors, non-Latin names, and complex author groups that fail automatic parsing are sent to manual REVIEW.
• Author name conflicts cannot be marked as PASS until resolved.
• After manuscript changes, old citation audit results are marked as STALE.
• Citation verification only corrects obvious errors; it does not rewrite source titles for uniform appearance.

Output

• Bidirectional verification table for in-text citations and references.
• List of issues related to author disambiguation, years, DOIs, sorting, and formatting.
• PASS, REVIEW, BLOCK, and STALE statuses.

Stop Conditions

• No final PASS is given when there is no manuscript version, reference list, or specified citation format.
• Mark as REVIEW and do not generate fields when author or publication metadata cannot be verified.
• Do not treat citation audit as claim-to-source audit.
• Do not automatically modify the formal titles and author names of sources.

Resources Provided with the Skill

• scripts/citation_audit.py

  : Checks in-text citations, references, disambiguation of authors with the same surname, and duplicate DOIs.

• assets/citation-audit-template.md

  : Citation verification record template.

Standalone Operation

• By default, it does not read private workspaces, personal corpus directories, or preset research-labs.
• Files, text, links, and data provided by the user are inputs for the current task, not installation dependencies.
• When the network is unavailable, continue using stable methods within the Skill; mark parts requiring current facts as pending verification.
• It can connect with other research Skills in this package if they exist; when installed separately, directly return instructions for the next step without stopping the current task.

Source Discipline

• Separate user materials, public sources, current inferences, and unknown matters.
• Report specification checks only examine report transparency; they do not automatically prove design quality.
• Public source abstracts are stored within the Skill; when versions, fees, policies, APIs, or journal statuses are needed, return to official pages.
• Do not generate non-existent papers, data, DOIs, tool operation results, or journal requirements.