agentleFS
Sign inStart free
PerryLinkPerryLink/dsh-research-skills/skills/citation-audit/SKILL.md

citation-audit

Skill0 starsChanged 5 days agoApache-2.0View on GitHub

Verify that every citation exists, that its metadata is right, that it is not retracted, and export it in the required style.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use figure-spec, comm-lit-review-claude-single and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • raja21068Skill

    figure-spec

    Generate deterministic publication-quality architecture, workflow, and pipeline diagrams from structured JSON (FigureSpec) into editable SVG. Use when user says \"架构图\", \"workflow 图\", \"pipeline 图\", \"确定性矢量图\", \"figure spec\", \"draw architecture\", or needs precise, editable, publication-ready vector diagrams. Preferred over AI illustration for formal architecture/workflow figures.

    Also in 4 projects that use this

  • raja21068Skill

    comm-lit-review-claude-single

    Communications-domain literature review with Claude-style knowledge-base-first retrieval. Use when the task is about communications, wireless, networking, satellite/NTN, Wi-Fi, cellular, transport protocols, congestion control, routing, scheduling, MAC/PHY, rate adaptation, channel estimation, beamforming, or communication-system research and the user wants papers, related work, a survey, or a landscape summary. Search Zotero, Obsidian, and local paper folders first when available, then search IEEE Xplore, ScienceDirect, ACM Digital Library, and broader web in that order.

    Also in 3 projects that use this

  • rongaredeSkill

    semantic-scholar

    使用 Semantic Scholar API 检索和验证学术论文。支持并发多关键词搜索、批量 ID/DOI 查询、引用分析、批量补全摘要、统一 Markdown 导出。覆盖 2.14 亿+ 学术论文，无需 API Key 即可使用。触发词：论文检索、论文验证、Semantic Scholar、S2 搜索、查论文、补全摘要、导出MD

    Also in 4 projects that use this

  • Yusong-EnceladusSkill

    feishu-notify

    Send notifications to Feishu/Lark. Internal utility used by other skills, or manually via /feishu-notify. Supports push-only (webhook) and interactive (bidirectional) modes. Use when user says \"发飞书\", \"notify feishu\", or other skills need to send status updates.

    Also in 3 projects that use this

  • +8 more from raja21068

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run retraction_watch on the resolved DOIs.

    line 19
  2. Very specific:

    Use cite_fix for a corrected BibTeX entry — text only, never edit the file silently.

    line 20
  3. Distinctive:

    Do not "fix" a DOI by guessing a nearby one.

    line 33
  4. Distinctive:

    Do not treat a network failure as a clean citation.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Citation audit

Rules

  • not_found is a skipped check, never proof of fabrication.
  • Metadata checks are field-by-field: DOI, title, authors, year, venue, pages.
  • Retraction status is a separate lookup, not a guess from the title.

Steps

  1. For each reference run cite_verify with doi / pmid / arxiv / bibtex.
  2. Batch with cite_batch when the list is long; read every status, lookupError, duplicate.
  3. Run retraction_watch on the resolved DOIs; clear means no registered notice, not "valid".
  4. Use cite_fix for a corrected BibTeX entry — text only, never edit the file silently.
  5. Export with cite_export (gbt7714-numeric, apa, ieee, vancouver, bibtex, ris, csl-json); report missing[] fields.
  6. Store the provider answers as REP evidence; cite the evidence ids in the audit summary.

Output

  • Per-reference verdict with the failing field.
  • Retraction status per DOI with the lookup date.
  • Export text + missing fields.
  • A count of verified / warn / unchecked / not-found.

Never

  • Do not "fix" a DOI by guessing a nearby one.
  • Do not treat a network failure as a clean citation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free