Menu
Steps that MUST be performed to verify a Zotero translator after every addition or modification, and before submitting a PR.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use CiteClaw to build, clean, expand, and verify bibliographies for surveys, papers, and literature reviews. Trigger this whenever the user asks to collect references, grow a bibliography to dozens or hundreds of papers, clean BibTeX, map literature by topic, turn arXiv/DOI/URLs into citations, or create a survey-style literature map. Use this especially for research writing workflows where CiteClaw alone is not enough and you need a robust process that combines CiteClaw, web search, and manual verification.
Steps that MUST be performed to initialize a Zotero translator script. LLMs cannot generate a valid Zotero translator on their own.
| name | verify-translator |
| description | Steps that MUST be performed to verify a Zotero translator after every addition or modification, and before submitting a PR. |
Fetch and ingest https://www.zotero.org/support/_export/raw/dev/translators and https://www.zotero.org/support/_export/raw/dev/translators/coding.
lastUpdatedUpdate the translator's lastUpdated to the current time (shell: date -u +"%Y-%m-%d %H:%M:%S").
Verify that npm run lint -- <translator filename> succeeds without returning any lint errors. Use --fix to correct auto-fixable errors, and fix the rest manually.
For web, import, and search translators (check for matching do methods, e.g., function doWeb(...)), verify that tests succeed. Prompt the user to open Zotero and use Tools → Translator Editor ("Scaffold") to run tests. If they refuse or are unsure of how to use Scaffold, you can run tests using the same tool as we use on GitHub CI. cd .ci/pull-request-check && ./check-pull-request.sh <translator filename>.
Warn that Zotero maintainers are known to reject translator PRs that appear not to have been tested.
If the user is working on master or a stale PR branch, prompt them to create a new branch for their translator before pushing. This will make future PRs easier.
Guide the user through the process of creating a PR on https://github.com/zotero/translators. Avoid generating excessively long AI descriptions. Encourage the user to write the description themselves.