agentleFS
Sign inStart free
clearsmogclearsmog/claude-skills/validate-bib/SKILL.md

validate-bib

Skill2 starsChanged 9 months agoMITView on GitHub

Validate bibliography entries against citations in all document files (.tex, .qmd, .typ). Find missing entries and unused references.

6 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 1 is common, 0 are distinctive, and 0 are very specific to this project.

  • 1

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Common:

    No malformed characters or encoding issues

    line 32

“Common” is measured: kept by at least 6 in 10 of the 6 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

Validate Bibliography

Cross-reference all citations in lecture files against bibliography entries.

Steps

  1. Read the bibliography file and extract all citation keys
  2. Scan all document files for citation keys:
    • .tex files: look for \cite{, \citet{, \citep{, \citeauthor{, \citeyear{
    • .qmd files: look for @key, [@key], [@key1; @key2]
    • .typ files: look for @key references (Typst uses @key syntax, no \citet/\citep distinction)
    • Also check for #bibliography("refs.bib") or #bibliography("refs.yml") (Hayagriva format) in .typ files
    • Note: some Typst projects use inline links instead of bibliography — detect and report
    • Extract all unique citation keys used
  3. Cross-reference:
    • Missing entries: Citations used in lectures but NOT in bibliography
    • Unused entries: Entries in bibliography not cited anywhere
    • Potential typos: Similar-but-not-matching keys
  4. Check entry quality for each bib entry:
    • Required fields present (author, title, year, journal/booktitle)
    • Author field properly formatted
    • Year is reasonable
    • No malformed characters or encoding issues
  5. Report findings:
    • List of missing bibliography entries (CRITICAL)
    • List of unused entries (informational)
    • List of potential typos in citation keys
    • List of quality issues

Files to scan

All .tex, .qmd, and .typ files in the project.

Bibliography location

Whatever the documents reference: \bibliography{} / \addbibresource{}, bibliography: in Quarto YAML, or #bibliography(...) in Typst. If nothing is referenced and several .bib/.yml files exist, ask which one.

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