bibtex-normalizer
Skill10 starsChanged 6 days agoMITView on GitHub
Parses a `.bib` file, removes duplicate entries and writes a normalised bibliography in a fixed field order. Fires before any citation-dependent stage so downstream tools see one consistent shape.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/chelate-shell.mdcCursor rule
- 3d-modelerSkill
- ai-trace-removerSkill
- capstone-labmateSkill
- conflict-detectorSkill
- data-profilerSkill
- document-evolution-trackerSkill
- formula-validatorSkill
- fulltext-extractorSkill
- latex-exporterSkill
- literature-retrieverSkill
- longitudinal-analysisSkill
- ml-auditorSkill
- multi-dim-managerSkill
- quantitative-validatorSkill
- reference-auditorSkill
- sci-visualizerSkill
- security-guardSkill
- task-organizerSkill
- video-trackerSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
- Distinctive: line 25
Run this exact form — do not read the source tree:
- Distinctive: line 67
No network lookup; no metadata completion.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
bibtex-normalizer
Normalises and de-duplicates a bibliography. It does not look up missing metadata and does not verify that an entry exists.
- Stage:
ingest· Sandbox: no · Dependencies:bibtexparser
Quick Execution
Run this exact form — do not read the source tree:
python run.py --root <WS> --action normalize --input refs.bib- Output defaults to
<WS>/process/bibtex/; override with--outdir. - The gate lands in
<WS>/process/gates/bibtex-normalizer_<ts>.json.
When to use
- Several
.bibexports must be merged into one consistent file. - Duplicate entries must be removed before a build or a citation check.
When NOT to use
- The entries themselves must be verified — that is
reference-auditor. - Missing fields must be filled from the web — not supported.
Actions
--action | Does | Extra arguments |
normalize | Parse, dedupe, normalise field order | --input <file.bib> [--outdir <dir>] |
Hard constraints
- Never invent metadata. Absent fields stay absent.
- Dedupe by content key, and report what was dropped.
Outputs
<WS>/process/bibtex/— the normalised.bibplus a JSON summary.<WS>/process/gates/bibtex-normalizer_<ts>.json— the gate result.
Failure handling
- A malformed
.bibfails the gate with the parser's message. bibtexparsermissing →UNVERIFIED.
Limitations
- No network lookup; no metadata completion.
- Non-standard entry types are preserved but not validated.
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
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.