跳到正文
cccskills
免费在 GitHub 公开

rseng-citation-hygiene

Covers verifying that every citation is real, correct and current: checking references in manuscripts, READMEs, references files and code metadata against Crossref and OpenAlex, screening cited DOIs against the Retraction Watch database, catching fabricated or mis-attributed citations (a documented AI failure mode), and keeping bibliographies and CITATION.cff files resolvable. Use PROACTIVELY before any bibliography, reference list or citation metadata is finalized or published, whenever the agent itself has produced citations, and when the user asks to check references, mentions broken DOIs, retracted papers or citation verification, or prepares a manuscript, README or software paper with references. (Making your own software citable is rseng-citation-metadata.)

中文简介正在准备中。当前显示原文说明。

fdiblen/rseng-agent-skills星标 24(GitHub 24 + cccskills 0)
集成工具GitLab

实测评分 未实测

查看安装方法

包含的文件(2)

  • SKILL.md6.0 KB
  • references.md519 B

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Citation hygiene

A citation is a checkable claim: this work exists, says what I say it says, and stands unretracted. All three parts fail routinely - and AI assistance has made the first failure mode systematic: language models fabricate plausible references with confident DOIs. An agent that produces or touches citations therefore has a special duty here, stated plainly: VERIFY EVERY CITATION YOU GENERATE against an authoritative source before handing it to the user, and say which were verified. No unverified reference should survive to a published artifact. rseng-citation-metadata covers making YOUR software citable; this skill covers the references you cite.

Verify existence and metadata (Crossref, OpenAlex)

For each reference with a DOI:

  • Resolve it: curl -sI https://doi.org/<DOI> - a failing DOI is either a typo or a fabrication; both are findings.
  • Fetch the registered metadata and compare with the citation as written: https://api.crossref.org/works/<DOI> (or the OpenAlex record at https://api.openalex.org/works/doi:<DOI> - open, keyless APIs). Title, authors, venue and year must match; a DOI that resolves to a DIFFERENT paper than the citation claims is the classic fabrication signature and worse than a dead link.
  • References without DOIs: search Crossref/OpenAlex by title and authors; if nothing plausible exists, flag it - books and grey literature can be legitimate, but only a human can vouch for them.
  • Batch the work: extract all references (BibTeX, CSL JSON, CITATION.cff references, markdown bibliographies), verify each, and report a table: verified / metadata-mismatch / unresolvable / no-DOI-needs-human.

Screen for retractions (Retraction Watch)

The Retraction Watch database is public, CC-BY, updated every working day, and Crossref-distributed - screening is one step:

  • Per DOI: query Crossref and inspect message.updated-by, keeping entries whose type is retraction, correction or expression_of_concern. Mind the direction: update-to points the opposite way, from a notice to the work it corrects, so querying it against a retracted paper returns nothing and the paper reads as clean. Or check against the full CSV (public git repository at gitlab.com/crossref/retraction-watch-data).
  • Screen at these moments: finalizing a bibliography, submitting a manuscript (rseng-research-integrity runs the fuller pre-submission battery), and citing a paper as the FOUNDATION of a method - building on a retracted result is the costliest citation failure.
  • A retraction hit is information, not automatic removal: report it with the retraction reason and let the author decide - citing retracted work knowingly (e.g. to discuss the retraction) is legitimate; citing it unknowingly is the failure.

Where citations hide in code projects

Manuscripts are not the only bibliography. Check:

  • CITATION.cff references and preferred-citation entries (rseng-citation-metadata), codemeta.json referencePublication.
  • README "please cite" blocks and papers listed in docs.
  • Algorithm-source comments ("implements the method of Smith 2019") - a wrong citation here misdirects future maintainers.
  • Dependency citation duties: software the project builds on that requests citation (rseng-software-reuse's cite-what-you-adopt) - verify those entries like any other.

Currency and completeness

  • Prefer the DOI form of a reference; preprint-vs-published drift is common - when a cited preprint has a published version, OpenAlex links the two; offer the update while preserving intent (sometimes the preprint IS the cited artifact - rseng-open-science-practices).
  • Keep bibliographies regenerable: store references as structured data (BibTeX/CSL/CFF) and render from it (rseng-documentation); hand-maintained duplicated reference lists drift apart.
  • Wire a lightweight check into CI where the project's references are load-bearing (rseng-ci-cd): DOI resolution plus retraction screen on the reference files - the citation analogue of a link checker.

Working with this skill

This skill is source-independent: its authority is the Crossref, OpenAlex and Retraction Watch services linked below. It is the verification counterpart to rseng-citation-metadata and feeds rseng-research-integrity's pre-submission checks.

Learn more (verified):

<!-- related-skills:begin -->

Related skills

Check whether any of these applies before moving on:

  • rseng-ci-cd - reference resolution checks in CI
  • rseng-citation-metadata - making own software citable
  • rseng-discovery - verifying surveyed literature leads
  • rseng-fact-checking - verifying non-citation claims
  • rseng-open-science-practices - preprint-to-published version links
  • rseng-research-integrity - pre-submission verification battery
<!-- related-skills:end -->

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Covers operating AI coding agents securely: auditing whether the agent runs sandboxed, permission and dangerous-command configuration, containerized environments, secrets kept out of context, network egress and token privileges, prompt-injection risk, and the privacy of agent use itself. Use PROACTIVELY when permission gating is broadly disabled (skip-permissions modes), when secrets are visible to the agent's shell, or when the agent processes untrusted code, issues or web content; when a project holds personal or confidential data while a cloud agent is active (what leaves the machine, retention, training use), or when the user asks how to run coding agents safely or privately. (Supply-chain security: rseng-security; disclosing agent contributions: rseng-ai-declaration.)

中文简介正在准备中。当前显示原文说明。

fdiblen/rseng-agent-skills242026年9月23日 更新

Covers declaring AI involvement with the AI Declaration Format (https://ai-declaration.org): creating and maintaining an aidecl.yaml that records which AI tools and agents were used, what each contributed, when and how much, plus the README disclosure footnote, JSON/JSON-LD export and CI validation. Machine-readable disclosure is the practice; this format is one implementation. Use PROACTIVELY when an AI assistant or agent creates or modifies a project's content - generate aidecl.yaml if missing, update it after AI-assisted changes. Also use when the user asks about AI transparency, provenance, disclosure or EU AI Act disclosure, wants to state that NO AI was used, or mentions aidecl. For concealment requests see rseng-honesty; for the human review duty see rseng-human-verification.

中文简介正在准备中。当前显示原文说明。

fdiblen/rseng-agent-skills242026年9月23日 更新

Covers long-term archiving of research software and data: Software Heritage save requests and SWHID persistent identifiers, Zenodo deposits with versioned DOIs and forge integration, choosing domain and institutional repositories, deciding what to archive (code, data, environments, documentation) and when, and archiving at project retirement. Use when the user wants software or data preserved beyond the life of a forge account, grant or lab, mentions Software Heritage, SWHIDs, Zenodo deposits or archiving, retires or hands over a project, prepares artifacts that must stay resolvable for a paper, or when funder policy requires long-term preservation. (Cutting the release itself is rseng-publishing-releasing; day-to-day data storage and repository choice is rseng-data-management.)

中文简介正在准备中。当前显示原文说明。

fdiblen/rseng-agent-skills242026年9月23日 更新

Covers processing research data that outgrows one machine's memory: out-of-core and chunked computation, Dask for scaling the scientific Python stack, Spark for distributed tabular pipelines, lazy evaluation, partitioning strategies, idempotent and restartable batch jobs, and knowing when NOT to distribute. Use when datasets no longer fit in memory, when the user mentions Dask, Spark, out-of-core or larger-than-memory data, when a pandas/NumPy workflow hits memory limits, or when designing batch pipelines over many files. (Cluster job submission and job arrays are rseng-hpc-computing; pipeline orchestration engines are rseng-workflows; profile first with rseng-performance-profiling.)

中文简介正在准备中。当前显示原文说明。

fdiblen/rseng-agent-skills242026年9月23日 更新

Covers continuous integration and delivery for research software: CI/CD concepts, automating builds and tests with GitHub Actions and GitLab CI/CD, and wiring an organization's GitLab CI infrastructure to a GitHub-hosted project. Use when the user asks to set up CI, write a pipeline or workflow file (.github/workflows, .gitlab-ci.yml), add automated builds/tests on push or pull request, publish a package or deploy docs when a tag or release is cut, cache dependencies to speed up CI runs, choose between GitHub Actions and GitLab CI, use self-hosted or GPU runners, mirror a repo, or report external CI status back to GitHub. For what to test and shrinking a test matrix see rseng-testing; for linter and pre-commit policy see rseng-code-quality.

中文简介正在准备中。当前显示原文说明。

fdiblen/rseng-agent-skills242026年9月23日 更新

Covers making research software citable and contributors credited: writing CITATION.cff, describing software with CodeMeta (codemeta.json), minting DOIs and ORCIDs, and tracking contributors of every kind. Use when the user asks how to make software citable, add CITATION.cff or codemeta.json, obtain a DOI, ensure contributors get credit, or mentions CFF, CodeMeta, ORCID, CRediT or persistent identifiers. Use PROACTIVELY when generated code draws on a publication, website or existing code (credit it at the code site and in the references), at release preparation, and when citation files are edited. (Verifying references you cite: rseng-citation-hygiene; versioning schemes and the DOI-minting release: rseng-publishing-releasing.)

中文简介正在准备中。当前显示原文说明。

fdiblen/rseng-agent-skills242026年9月23日 更新

查看 fdiblen 的全部技能

报告此技能的问题