Agent skill

Bib Parse

by flonat in flonat/flonat-research

Extract citations from a PDF and generate a validated .bib file.

MITAuto-check passedResearch & Science

Install Bib Parse

skills CLI
$ npx skills add flonat/flonat-research --skill bib-parse -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install flonat/flonat-research bib-parse --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/bib-parse .claude/skills/bib-parse && rm -rf skills-src

Use ~/.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/

Facts

Skill name
bib-parse
GitHub stars
145
Token cost
~3.8k tokens
SKILL.md length
1,701 words
Files
1
Skills in repo
83
Repo updated
First seen
Licence
MIT

At a glance

Extract citations from a PDF and generate a validated .bib file.

  • Works in 4 steps: Read → Enrich → Construct → …
  • The user asks to extract citations from a PDF and generate a validated .bib file
  • SKILL.md covers When to Use, When NOT to Use, Input and Output, plus 7 more sections
  • Calls uv

What it does

Bib Parse is an agent skill from flonat/flonat-research. Extract citations from a PDF and generate a validated .bib file. Use when the user asks to extract citations from a PDF and generate a validated .bib file. Reads the PDF, identifies referenced works, constructs BibTeX entries, and verifies metadata.

Its SKILL.md is about 3.8k 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 and PDF. It works with LaTeX. The repository describes itself as: Shareable Claude Code + Codex infrastructure for PhD researchers — skills, agents, hooks, and rules for academic workflows. The licence is MIT.

When your agent uses it

  • The user asks to extract citations from a PDF and generate a validated .bib file
  • Tasks that involve Citation management
  • Tasks that involve PDF

Example prompts

  • “/bib-parse”

Requirements

  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Bash(mkdir*), Bash(ls*), Bash(uv*), WebFetch, WebSearch, Skill(split-pdf), Bash(paperpile*)

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Read
  2. Enrich
  3. Construct
  4. Validate

What it can do on your machine

Read from SKILL.md and the folder at commit da27600. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Write
    • Bash(mkdir*)
    • Bash(ls*)
    • Bash(uv*)
    • WebFetch
    • WebSearch
    • Skill(split-pdf)

    …and 1 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • uv

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Bib Parse loads about 3.8k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 1,701 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~3.8k

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 flonat/flonat-research at commit da27600, republished under its MIT licence (© flonat). 1,701 words, ~3,774 tokens.

Download SKILL.mdSave it as .claude/skills/bib-parse/SKILL.md (or your agent's skills folder).
name
bib-parse
description
Extract citations from a PDF and generate a validated .bib file. Use when the user asks to extract citations from a PDF and generate a validated .bib file. Reads the PDF, identifies referenced works, constructs BibTeX entries, and verifies metadata.
allowed-tools
Read, Glob, Grep, Write, Bash(mkdir*), Bash(ls*), Bash(uv*), WebFetch, WebSearch, Skill(split-pdf), Bash(paperpile*)
argument-hint
<path-to-pdf>
skill-dependencies
split-pdf

Bibliography Parser — PDF to .bib

LIBRARY-FIRST RULE: ALWAYS check Paperpile membership by DOI (paperpile lookup-by-doi) for each parsed reference BEFORE generating new BibTeX entries. Topic/title search-library is a lossy discovery aid, NOT a membership test — never tag a reference NEW off a title-search miss. Reuse existing library entries instead of constructing from scratch. Enforced in Phase 2.3 per shared/reference-resolution.md § Membership Check.

Goal: given a PDF file, extract all cited references and produce a clean, validated .bib file.

When to Use

  • You have a PDF (paper, report, thesis) and need a .bib file for its references
  • Importing references from a paper that doesn't have a companion .bib file
  • Reconstructing a bibliography from a document with embedded \begin{thebibliography} or numbered references
  • Converting a reference list from any format into BibTeX

When NOT to Use

  • You already have a .bib file and just need to validate it — use the configured bibliography validator
  • Finding new references on a topic — use an installed literature workflow or scholarly search
  • The PDF is already in Paperpile — export via paperpile export-bib instead (faster, more accurate)

Input

A single PDF file path. The PDF should contain a bibliography, reference list, or works cited section.

Output

A .bib file, located by context:

  • PDF inside a research project (e.g. articles/, paper-*/, project root) — write to the same directory as the input PDF, named references.bib (per project convention). If references.bib already exists, ask before overwriting — offer to merge or use a different name (e.g., extracted-refs.bib).
  • Standalone PDF (ad-hoc extraction with no project home — e.g. a client-managed upload) — write to ~/vault/parsed-bibs/<slug>.bib, where <slug> describes the source (e.g. kasberger-algorithmic-cooperation-geb-2026.bib). This is the standing location for one-off parses (established 2026-06-14). Create the folder if absent.

Any staged Paperpile-import entry (Phase 4.1) is written into a .bib under .paperpile-import/ next to the output .bib.


Phase 1: Read

1.1 Read the PDF

Use split-pdf to read the PDF contents. This handles large PDFs by splitting into chunks. Focus on the bibliography / references section — typically the last few pages. Identify:

  • Numbered reference lists (e.g., [1] Smith, J. (2020)...)
  • APA / Harvard style reference lists
  • \bibitem entries (if the PDF was generated from LaTeX)
  • Footnote-based citations
1.2 Skeleton confirmation (mandatory for ≥10 references)

Before running any enrichment queries, render the parsed reference list as a numbered table and ask the user to confirm the split is correct. A misparsed reference list (one citation accidentally split across two rows, or two citations merged into one) makes Phase 2 spend 30+ API calls on the wrong entries — expensive in time and rate-limit budget.

markdown
Detected N references. Confirm the split before I enrich each one:

| # | parsed reference (verbatim) |
|---|----------------------------|
| 1 | Bebchuk, L. A., Cohen, A., & Hirst, S. (2017). The agency problems of institutional investors... |
| 2 | Smith, J. (2020). Title... |
| ... | ... |

Anything wrong with the split? (Reply "ok" to proceed, or list the row numbers that need merging/splitting.)

Skip the confirmation step if any of these:

  • Fewer than 10 references parsed (cheap to fix after the fact)
  • The PDF was generated from LaTeX and \bibitem boundaries are unambiguous
  • The user explicitly said "just go" / "no confirmation"

When the user flags a bad split, fix it and re-render the skeleton before proceeding. Don't proceed to Phase 2 with unaddressed split issues — that's exactly the failure case this gate prevents.


Phase 2: Enrich

2.1 Extract reference metadata

For each reference found, extract:

FieldPriorityNotes
AuthorsRequiredFull names, {Last, First and Last, First} BibTeX format
TitleRequiredExact title from the reference
YearRequiredPublication year
Journal / BooktitleRequired (articles/proceedings)Full journal name, not abbreviation
Volume / Number / PagesIf availableStandard bibliographic fields
PublisherIf availableFor books and proceedings
DOIBest effortExtract if printed in the reference

Large reference lists (50+ entries): process in batches of ~20. Verify each batch before moving to the next. Report progress: "Processed 20/87 references...". This caps the rate-limit blast radius if a batch fails.

2.2 Verify and enrich

For each extracted reference, verify and enrich using available tools:

  1. Search by title via web search to confirm the reference exists and pull missing metadata (DOI, volume, pages).
  2. Use the scholarly CLI for multi-source enrichment:
    • scholarly scholarly-search "<title>" --json — search by title across OpenAlex + S2 + Scopus + WoS
    • scholarly scholarly-paper-detail <paper_id> --json — get full metadata including pre-formatted BibTeX (citationStyles), TLDR summary, and open access PDF link. When BibTeX is available, use it as the primary template instead of manually constructing entries — reduces formatting errors.
    • scholarly openalex-lookup-doi <doi> --json — get full metadata if DOI was found.
  3. Cross-check extracted metadata against search results: confirm author names, year, fill in missing DOI/volume/pages/publisher.

Important: do NOT silently replace the extracted metadata with search results. If there's a conflict (e.g., different year, different spelling of author name), flag it as a note field in the .bib entry and keep the original from the PDF.

2.3 Check Paperpile library (LIBRARY-FIRST gate)

For each parsed reference, check if it already exists in Paperpile using the resolution order from shared/reference-resolution.md:

  1. Check membership by DOI — paperpile lookup-by-doi --doi <DOI> for each parsed reference (verify the DOI itself first if unsure). This is the membership test. Batch ≥6 references via one Bash sub-agent returning a merged {doi: citekey-or-null} map.
  2. Only for DOI-less references, fall back to paperpile search-library with first-author surname + title keywords (limit ≥10) — a discovery aid, not a membership test.
  3. Match → ALREADY IN PAPERPILE: reuse the returned Paperpile citekey, skip staging in Phase 4.1. A confirmed DOI miss (or, for DOI-less refs, an author+title miss) → NEW — never tag NEW off a search-library miss alone. Foundational classics (Simon, March, Levinthal, Cyert & March, …) are the most common false NEW; check them by DOI too.

Status summary:

PaperpileStatusPhase 4.1 action
YesALREADY IN PAPERPILESkip (reuse key)
NoNEWStage as BibTeX for Paperpile import

Graceful degradation: if the paperpile CLI is unavailable, skip with a warning and treat all references as NEW.


Phase 3: Construct

3.1 Generate citation keys

Better BibTeX conventions:

  • Format: {Author}{Year}-{xx} — e.g., Smith2020-xy
  • First author's last name, title-cased
  • Four-digit year
  • Two-character suffix (Better BibTeX style)
  • If merging into an existing .bib, match the key format already in use
  • For references already in Paperpile (Phase 2.3), copy the Paperpile citekey into the entry (do not keep the generated key) and backfill the DOI from Paperpile, but keep the richer local metadata (type, journal, volume, pages, full authors — Paperpile's export-bib is @misc/thin). Add note = {key reconciled to Paperpile <key>}. Full rule + first-author-match guard: shared/reference-resolution.md § Key Reconciliation.
Show full SKILL.md (689 more words)Show less
3.2 Determine entry types
Source typeBibTeX typeKey fields
Journal article@articleauthor, title, journal, year, volume, number, pages
Conference paper@inproceedingsauthor, title, booktitle, year, pages
Book@bookauthor/editor, title, publisher, year
Book chapter@incollectionauthor, title, booktitle, publisher, year, pages
Working paper / preprint@techreport or @unpublishedauthor, title, institution/note, year
Thesis@phdthesis or @mastersthesisauthor, title, school, year
Website / online@miscauthor, title, howpublished, year, note
3.3 Write the .bib file

Write entries to the output .bib file with:

  • One blank line between entries
  • Fields indented with 2 spaces
  • Required fields first, then optional fields
  • DOI field included when available
  • A note field for any metadata conflicts or uncertainties flagged in 2.2

Example entry:

bibtex
@article{smith2020optimal,
  author = {Smith, John and Doe, Jane},
  title = {Optimal Decision Making Under Uncertainty},
  journal = {Management Science},
  year = {2020},
  volume = {66},
  number = {3},
  pages = {1234--1256},
  doi = {10.1287/mnsc.2019.3456}
}
3.4 Quality fallbacks

Two cases that cross sub-steps:

Poor OCR / unreadable references (PDFs with poor text extraction, scanned documents, unusual formatting):

  1. Flag references that couldn't be reliably parsed.
  2. Add them as @misc entries with note = {MANUAL CHECK NEEDED: ...}.
  3. Include whatever text was extracted so the user can fix it manually.

Incomplete references (missing key fields like year or journal):

  1. Attempt to find the complete reference via web search (typically already done in 2.2).
  2. If found, fill in the missing fields and add note = {metadata enriched from web search}.
  3. If not found, write what's available and flag with note = {INCOMPLETE: missing [field]}.

Phase 4: Validate

4.1 Stage for Paperpile import

Follow the filing sequence from shared/reference-resolution.md. For references marked NEW in Phase 2.3:

  1. Present a summary table before staging:

    #KeyTitleAuthorsYearStatus
    1Smith2020-xyTitle...Smith, J.2020NEW — staging for import
    2Doe2019-abTitle...Doe, J.2019ALREADY IN PAPERPILE (skipped)
  2. Stage under .paperpile-import/ — write each new entry's BibTeX into a .bib under .paperpile-import/ (Paperpile CLI is read-only; write-bib --citekeys only exports entries already in the library). Mark any draft cite \CiteTodo{...} until imported.

  3. Remind user — "Import the staged .bib under .paperpile-import/ into Paperpile to complete the sync."

Graceful degradation: if the paperpile CLI is unavailable, skip this sub-step. The .bib file from Phase 3.3 is still the primary output.

4.2 Validate the generated bibliography (HARD GATE)

Run the configured bibliography validator when installed. Otherwise perform these checks directly:

  • Check for required fields
  • Verify DOIs resolve correctly
  • Flag any remaining issues

Surface the validation report inline in the final summary (see Report section below). Do not proceed to 4.3 when citation keys are unresolved, required fields are missing, or metadata cannot be verified—fix and re-validate first.

4.3 Output verification (before commit)

Before any auto-commit, emit an outputs manifest and run the shared verifier per _shared/verify-outputs.md:

  1. Write manifest to <project>/.claude/state/outputs-manifest-<UTC-timestamp>.json listing every file this skill claims to have written, paths relative to the project root.

  2. Run:

    bash
    uv run python "<skills-root>/_shared/verify_outputs.py" \
        --manifest "$MANIFEST" \
        --project-root "$PROJECT_ROOT"
  3. If the verifier exits non-zero, do not commit. Surface the missing-files list and stop. The verifier logs an error entry to ~/.local/state/ai-workflows/skill-outcomes.jsonl.

Closes the "hallucinated outputs" failure class (commit b2cff75, 2026-04-18).


Report

After completion, provide a summary:

## bib-parse Summary

**Input:** [filename.pdf]
**Output:** [output.bib]

| Metric | Count |
|--------|-------|
| References found in PDF | X |
| Successfully parsed | Y |
| DOIs found/verified | Z |
| Already in Paperpile | A |
| Staged for Paperpile import | B |
| Flagged for manual review | W |

### Bibliography validation report
[paste the configured validator's verdict, or the direct checks performed, plus any critical issues]

### Entries needing attention
- `key1` — missing journal name
- `key2` — year mismatch between PDF (2019) and DOI lookup (2020)

Cross-References

  • Installed bibliography validator — validates the generated .bib file when available in Phase 4.2
  • bib-coverage — compare project .bib vs Paperpile project/topic folder — find uncited papers and unfiled references
  • split-pdf — reads the input PDF (called in Phase 1.1)
  • Installed literature workflow or scholarly search — for finding additional references beyond what's in the PDF
  • shared/reference-resolution.md — canonical lookup + filing sequence used by Phase 2.3 and Phase 4.1

Citation Contract

<!-- paperpile-citation-contract -->
  1. Paperpile is the only source of truth for committed citation keys and BibTeX metadata.
  2. Before writing \cite{key}, verify with paperpile get-item key and paperpile export-bib key.
  3. Resolve unknowns in order: DOI lookup → Paperpile substring search → refpile semantic search → Paperpile verify.
  4. A DOI miss is not non-membership; continue with title/author search and refpile.
  5. If unresolved, write \CiteTodo{slug}{title/author/year/DOI hint} — never a guessed key.
  6. Drafting sub-agents must not write/edit the active .bib; only the orchestrator regenerates it from Paperpile exports.
  7. Stage genuine new refs under .paperpile-import/ for manual Paperpile import; don't cite until Paperpile mints the key.
  8. Run scripts/bib/citation_lint.py before commit; zero placeholders, zero non-Paperpile keys, zero hand-authored metadata.

See rules/paperpile-citations.md for the full workflow.

© flonat, 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 skills/bib-parse of flonat/flonat-research.

Open the folder on GitHubat commit da27600

Compare with similar skills

Bib Parse 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.

Bib Parse compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bib Parse this skillflonat/flonat-research145—~3.8kAutomated safety check: PassMIT
Paper Reading ZhMrGeDiao/paper-reading-zh103—~1.3kAutomated safety check: PassMIT
01 Paper Reviewagentscope-ai/OpenJudge8681 repos~2.4kAutomated safety check: PassApache-2.0
Colt Camera Readybrycewang-stanford/Awesome-Journal-Skills1.2k—~1.7kAutomated safety check: PassMIT
Check Review Alignmentmajiayu000/claude-skill-registry6661 repos~1.5kAutomated safety check: PassMIT
Paper Auditbahayonghang/academic-writing-skills497—~5.1kAutomated safety check: PassNone

Similar skills

  • Paper Reading Zh

    MrGeDiao/paper-reading-zh

    中文论文深读、总结/TL;DR、工程拆解、按论文实现/复现、比较与证据审计。用户给出论文 PDF、链接、标题、摘要、正文或图表,或明确要读论文时使用。只有论文锚点且无附言时澄清阅读目标;只有阅读意图时问哪篇。已有论文时,“看看这篇”直接深读。不用于仅翻译、解释单个术语、生成 BibTeX、找或下载论文。

    103 GitHub stars~1.3k tokensUpdated 4 days ago
    Research & ScienceAuto-check passed
  • 01 Paper Review

    agentscope-ai/OpenJudge

    Review academic papers for correctness, quality, and novelty using OpenJudge's multi-stage pipeline.

    868 GitHub starsUsed in 1 repo~2.4k tokens
    Research & ScienceAuto-check passed
  • Colt Camera Ready

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when converting an accepted COLT (Conference on Learning Theory) paper into its PMLR proceedings version, covering de-anonymization, acknowledgements and funding restoration…

    1.2k GitHub stars~1.7k tokensUpdated 11 days ago
    Research & ScienceAuto-check passed
  • Check Review Alignment

    majiayu000/claude-skill-registry

    当用户明确要求"核查/优化综述 {主题}review.tex 的正文引用"或"运行 check-review-alignment"时使用。通过宿主 AI 的语义理解逐条核查引用是否与文献内容吻合,只在发现致命性引用错误时对"包含引用的句子"做最小化改写,并复用 systematic-literature-review 的渲染脚本输出…

    666 GitHub starsUsed in 1 repo~1.5k tokens
    Research & ScienceAuto-check passed
  • Paper Audit

    bahayonghang/academic-writing-skills

    Reviewer-style audit and submission gate for academic papers in .tex, .typ, or .pdf.

    497 GitHub stars~5.1k tokensUpdated 10 days ago
    Documents & OfficeAuto-check passed
  • Literature Downloader

    Lucaswangzcx/literature-downloader-skill

    中文文献检索、筛选、批量采集和合法全文获取助手。用于用户需要查找论文、下载可合法获取的 PDF/HTML/XML 全文、生成关键词和检索式、查询 DOI/PMID、筛选高影响因子或高分区期刊、检查开放获取、做引用链扩展、批量文献候选表、下载日志、去重清单、Zotero/BibTeX 整理,或解决文献难下载问题;禁止绕过付费墙、盗版下载、共享账号或规避版权限制。

    236 GitHub stars~1.4k tokensUpdated 5 mo ago
    Research & ScienceAuto-check passed

More from flonat/flonat-research

All 83 skills in this repo
  • Latex Posters

    flonat/flonat-research

    Create a large-format academic poster in LaTeX using beamerposter, tikzposter, or baposter.

    145 GitHub stars~1.5k tokensUpdated 8 days ago
    Auto-check: notes
  • Skill Creator

    flonat/flonat-research

    Create, revise, and evaluate reusable AI workflow skills, including trigger-quality tests.

    145 GitHub stars~4.4k tokensUpdated 8 days ago
    Auto-check passed
  • DOCX

    flonat/flonat-research

    Create, read, edit, or convert Microsoft Word documents while preserving professional document structure.

    145 GitHub stars~1.2k tokensUpdated 8 days ago
    Auto-check passed
  • PDF

    flonat/flonat-research

    Read, create, combine, split, rotate, OCR, watermark, secure, or extract content from PDF files.

    145 GitHub stars~488 tokensUpdated 8 days ago
    Auto-check passed
  • Init Project Orchestration

    flonat/flonat-research

    Create or migrate project-level agents, repeatable project workflows, and planning state from one client-neutral contract, then render repository-scoped adapters for both Claude Code and Codex.

    145 GitHub stars~1.6k tokensUpdated 8 days ago
    Auto-check passed
  • Pre Commit Audit

    flonat/flonat-research

    Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers.

    145 GitHub stars~2.8k tokensUpdated 8 days ago
    Auto-check: notes

Works with

Questions about Bib Parse

What does Bib Parse do?

Extract citations from a PDF and generate a validated .bib file. Bib Parse is an agent skill from flonat/flonat-research.bib file.

When should I use Bib Parse?

Bib Parse fits situations like: the user asks to extract citations from a PDF and generate a validated .bib file; tasks that involve Citation management; tasks that involve PDF.

How do I install Bib Parse in Claude Code?

Run `npx skills add flonat/flonat-research --skill bib-parse -a claude-code`. Or copy the skill folder (skills/bib-parse in flonat/flonat-research) into .claude/skills/bib-parse in your project. Claude Code loads it when a task matches its description.

How do I install Bib Parse in Codex?

Run `npx skills add flonat/flonat-research --skill bib-parse -a codex`. Or copy the skill folder (skills/bib-parse in flonat/flonat-research) into .agents/skills/bib-parse in your project. Codex loads it when a task matches its description.

Can I use Bib Parse 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 flonat/flonat-research --skill bib-parse -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bib-parse, .gemini/skills/bib-parse, .github/skills/bib-parse and .opencode/skills/bib-parse in your project.

What does Bib Parse need to run?

Going by SKILL.md and its folder, Bib Parse needs the command-line tools its instructions call (uv). Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Bash(mkdir*), Bash(ls*), Bash(uv*), WebFetch, WebSearch, Skill(split-pdf), Bash(paperpile*).

Does Bib Parse access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Bib Parse 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 Bib Parse use?

Bib Parse 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 Bib Parse use?

About 3.8k tokens (SKILL.md is roughly 15k 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 Bib Parse?

Skills that share tags, products or a category with Bib Parse: Paper Reading Zh (MrGeDiao/paper-reading-zh, 103 stars), 01 Paper Review (agentscope-ai/OpenJudge, 868 stars), Colt Camera Ready (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Check Review Alignment (majiayu000/claude-skill-registry, 666 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bib Parse?

flonat (a GitHub user) maintains it in flonat/flonat-research, which has 145 GitHub stars. The repository holds 83 skills in this directory. The repository was last updated on September 29, 2026.

Source: flonat/flonat-research on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.