Citation Management
neflibata-feng/MyArxiv-Agent
Comprehensive citation management for academic research. An agent skill from neflibata-feng/MyArxiv-Agent.
Set up this repository's BibTeX Verifier and check a user's .bib file, then explain citation matches, warnings, missing records, and API failures.
Install Verify Bibtex
$ npx skills add Altman-conquer/bibtex-verifier --skill verify-bibtex -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Altman-conquer/bibtex-verifier verify-bibtex --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Altman-conquer/bibtex-verifier.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/verify-bibtex .claude/skills/verify-bibtex && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "verify-bibtex" agent skill from https://github.com/Altman-conquer/bibtex-verifier/tree/main/.agents/skills/verify-bibtex into .claude/skills/verify-bibtex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-bibtex", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Altman-conquer/bibtex-verifier/tree/main/.agents/skills/verify-bibtexType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Altman-conquer/bibtex-verifier --skill verify-bibtex -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Altman-conquer/bibtex-verifier verify-bibtex --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Altman-conquer/bibtex-verifier.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/verify-bibtex .agents/skills/verify-bibtex && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verify-bibtex" agent skill from https://github.com/Altman-conquer/bibtex-verifier/tree/main/.agents/skills/verify-bibtex into .agents/skills/verify-bibtex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-bibtex", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Altman-conquer/bibtex-verifier --skill verify-bibtex -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Altman-conquer/bibtex-verifier verify-bibtex --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Altman-conquer/bibtex-verifier.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/verify-bibtex .cursor/skills/verify-bibtex && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "verify-bibtex" agent skill from https://github.com/Altman-conquer/bibtex-verifier/tree/main/.agents/skills/verify-bibtex into .cursor/skills/verify-bibtex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-bibtex", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Altman-conquer/bibtex-verifier.git --path .agents/skills/verify-bibtex--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Altman-conquer/bibtex-verifier --skill verify-bibtex -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Altman-conquer/bibtex-verifier verify-bibtex --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Altman-conquer/bibtex-verifier.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/verify-bibtex .gemini/skills/verify-bibtex && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "verify-bibtex" agent skill from https://github.com/Altman-conquer/bibtex-verifier/tree/main/.agents/skills/verify-bibtex into .gemini/skills/verify-bibtex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-bibtex", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Altman-conquer/bibtex-verifier verify-bibtexInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Altman-conquer/bibtex-verifier --skill verify-bibtex -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Altman-conquer/bibtex-verifier.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/verify-bibtex .github/skills/verify-bibtex && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "verify-bibtex" agent skill from https://github.com/Altman-conquer/bibtex-verifier/tree/main/.agents/skills/verify-bibtex into .github/skills/verify-bibtex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-bibtex", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Altman-conquer/bibtex-verifier --skill verify-bibtex -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Altman-conquer/bibtex-verifier verify-bibtex --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Altman-conquer/bibtex-verifier.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/verify-bibtex .opencode/skills/verify-bibtex && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "verify-bibtex" agent skill from https://github.com/Altman-conquer/bibtex-verifier/tree/main/.agents/skills/verify-bibtex into .opencode/skills/verify-bibtex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-bibtex", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
verify-bibtex- GitHub stars
- 121
- Token cost
- ~655 tokens
- SKILL.md length
- 360 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Set up this repository's BibTeX Verifier and check a user's .bib file, then explain citation matches, warnings, missing records, and API failures.
- Works in 5 steps: Ensure Python 3.9+ is available. Use an… → Check whether OPENALEX_API_KEY is… → Run bibverify /path/to/references.bib… → …
- Asked to verify references with this GitHub project
- Calls python; needs OPENALEX_API_KEY
- Tasks that involve Citation management
What it does
Verify Bibtex is an agent skill from Altman-conquer/bibtex-verifier. Set up this repository's BibTeX Verifier and check a user's .bib file, then explain citation matches, warnings, missing records, and API failures. Use when asked to verify references with this GitHub project.
Its SKILL.md is about 660 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Citation management. It works with LaTeX and GitHub. The repository describes itself as: Verify BibTeX references against OpenAlex & CrossRef to detect errors and AI hallucinations. The licence is MIT.
When your agent uses it
- Asked to verify references with this GitHub project
- Tasks that involve Citation management
Example prompts
- “s BibTeX Verifier and check a user”
- “/verify-bibtex”
Requirements
- Python 3
- A credential in OPENALEX_API_KEY
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Ensure Python 3.9+ is available. Use an existing working environment or create an isolated virtual environment and install this checkout…
- Check whether OPENALEX_API_KEY is already available without printing its value. If absent, ask the user to configure their own OpenAlex…
- Run bibverify /path/to/references.bib --json. The command writes a Markdown report and a JSON report next to the input by default. An exit…
- Tell the user the counts for OK, WARNING, ERROR, NOT_FOUND, and UNVERIFIED, with links or paths to the reports. For each non-OK entry…
- Review unresolved items against identifiers already present in their BibTeX (doi, eprint, arXiv IDs in journal or url, and publisher…
What it can do on your machine
Read from SKILL.md and the folder at commit 5b4961e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
OPENALEX_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Verify Bibtex loads about 655 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 360 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Altman-conquer/bibtex-verifier at commit 5b4961e, republished under its MIT licence (© Altman-conquer). 360 words, ~655 tokens.
Download SKILL.mdSave it as
.claude/skills/verify-bibtex/SKILL.md (or your agent's skills folder).- name
- verify-bibtex
- description
- Set up this repository's BibTeX Verifier and check a user's .bib file, then explain citation matches, warnings, missing records, and API failures. Use when asked to verify references with this GitHub project.
Verify BibTeX
Use the checked-out source of this repository; a published package may lag behind it. If the user supplied only the GitHub URL, obtain the repository and locate the .bib file or pasted BibTeX they want checked. Ask for the bibliography if it was not provided. Do not change the user's .bib file unless asked.
- Ensure Python 3.9+ is available. Use an existing working environment or create an isolated virtual environment and install this checkout with
python -m pip install -e .from the repository root. Run itsbibverifyentry point, not an older globally installed copy. - Check whether
OPENALEX_API_KEYis already available without printing its value. If absent, ask the user to configure their own OpenAlex key. Use a secret-input mechanism or a process environment variable; do not put a key in the repository, command text, logs, report, or chat response. Never assume this repository includes a shared key. Anonymous lookup is possible, but rate limits can leave entriesUNVERIFIED. - Run
bibverify /path/to/references.bib --json. The command writes a Markdown report and a JSON report next to the input by default. An exit code of 1 can mean reportedERROR,NOT_FOUND, orUNVERIFIED; inspect the generated JSON before treating the run as a failure. - Tell the user the counts for
OK,WARNING,ERROR,NOT_FOUND, andUNVERIFIED, with links or paths to the reports. For each non-OK entry, give its citation key, specific field discrepancy, matched source and identifier when available, and a concrete next check. Do not call a citation fabricated solely because it isNOT_FOUNDorERROR. - Review unresolved items against identifiers already present in their BibTeX (
doi,eprint, arXiv IDs injournalorurl, and publisher links). The CLI currently prioritizes explicit DOI lookup and OpenAlex title search; an arXiv ID embedded elsewhere can explainNOT_FOUND. Distinguish a database coverage gap, a web/product citation outside scholarly indexes, a conflicting identifier, and an API failure. Mark conclusions that could not be independently verified.
Show full SKILL.md (31 more words)Show less
Keep the report evidence-based. WARNING often reflects preprint versus publication metadata or author-list conventions; UNVERIFIED means the lookup did not complete. Do not silently lower matching thresholds to make warnings disappear.
© Altman-conquer, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/verify-bibtex of Altman-conquer/bibtex-verifier.
Open the folder on GitHubat commit 5b4961e
Compare with similar skills
Verify Bibtex next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Verify Bibtex this skillAltman-conquer/bibtex-verifier | 121 | — | ~655 | Automated safety check: Pass | MIT | |
| Citation Managementneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~8.1k | Automated safety check: Notes | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Literature Review AgentAr9av/PaperOrchestra | 677 | 2 repos | ~5.2k | Automated safety check: Pass | Custom licence | |
| Academic Searchustc-ai4science/academic-search | 666 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Collaborating With Claudeappautomaton/latex-arxiv-SKILL | 457 | 1 repos | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Literature Review Agent
Ar9av/PaperOrchestra
Step 3 of the PaperOrchestra pipeline (arXiv:2604.05018). An agent skill from Ar9av/PaperOrchestra.
Academic Search
ustc-ai4science/academic-search
A skill your agent uses when the user asks to search or review academic papers, retrieve scholarly metadata or citation counts, validate or deduplicate scholarly records, find an author's…
Collaborating With Claude
appautomaton/latex-arxiv-SKILL
Use the Claude Code CLI to consult Claude and delegate coding tasks for prototyping, debugging, and code review.
Arxiv MCP Server
blazickjp/arxiv-mcp-server
A skill your agent uses when finding, comparing, reading, or monitoring arXiv papers, including requests for abstracts, citation graphs, original LaTeX, section-level technical details, or…
Related
Categories
Questions about Verify Bibtex
What does Verify Bibtex do?
Set up this repository's BibTeX Verifier and check a user's .bib file, then explain citation matches, warnings, missing records, and API failures. Verify Bibtex is an agent skill from Altman-conquer/bibtex-verifier.bib file, then explain citation matches, warnings, missing records, and API failures.
When should I use Verify Bibtex?
Verify Bibtex fits situations like: asked to verify references with this GitHub project; tasks that involve Citation management.
How do I install Verify Bibtex in Claude Code?
Run `npx skills add Altman-conquer/bibtex-verifier --skill verify-bibtex -a claude-code`. Or copy the skill folder (.agents/skills/verify-bibtex in Altman-conquer/bibtex-verifier) into .claude/skills/verify-bibtex in your project. Claude Code loads it when a task matches its description.
How do I install Verify Bibtex in Codex?
Run `npx skills add Altman-conquer/bibtex-verifier --skill verify-bibtex -a codex`. Or copy the skill folder (.agents/skills/verify-bibtex in Altman-conquer/bibtex-verifier) into .agents/skills/verify-bibtex in your project. Codex loads it when a task matches its description.
Can I use Verify Bibtex in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Altman-conquer/bibtex-verifier --skill verify-bibtex -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-bibtex, .gemini/skills/verify-bibtex, .github/skills/verify-bibtex and .opencode/skills/verify-bibtex in your project.
What does Verify Bibtex need to run?
Going by SKILL.md and its folder, Verify Bibtex needs the command-line tools its instructions call (python) and credentials named OPENALEX_API_KEY. Our summary lists: Python 3; A credential in OPENALEX_API_KEY.
Does Verify Bibtex access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Verify Bibtex safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Verify Bibtex use?
Verify Bibtex is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Verify Bibtex use?
About 655 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Verify Bibtex?
Skills that share tags, products or a category with Verify Bibtex: Citation Management (neflibata-feng/MyArxiv-Agent, 126 stars), Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars), Literature Review Agent (Ar9av/PaperOrchestra, 677 stars) and Academic Search (ustc-ai4science/academic-search, 666 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verify Bibtex?
Altman-conquer (a GitHub user) maintains it in Altman-conquer/bibtex-verifier, which has 121 GitHub stars. The repository was last updated on September 29, 2026.
Source: Altman-conquer/bibtex-verifier on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.