reference-format
Skill4 starsChanged 6 months agoMITView on GitHub
Convert or normalize the bibliography's citation style via the toolchain (biblatex/biber, CSL via pandoc, bibtex .bst) — deterministic, presentation-only, never altering the underlying facts and never inventing a missing field
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- abstractSkill
- citation-auditSkill
- claim-checkSkill
- cover-letterSkill
- gap-finderSkill
- journal-fitSkill
- lit-briefingSkill
- literature-reviewSkill
- lit-ingestSkill
- lit-lintSkill
- manuscript-cycleSkill
- methods-reviewSkill
- noteSkill
- outlineSkill
- peer-reviewSkill
- plain-language-summarySkill
- response-to-reviewersSkill
- retroSkill
- review-resurfaceSkill
- scorecardSkill
- stats-checkSkill
- submission-pipelineSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
After retargeting (/journal-fit surfaced a style mismatch as a gap).
- Distinctive: line 53
After the tool runs:
- Distinctive: line 118
Keep facts and presentation strictly separate.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Reference Format
Core Rule
Reference formatting is deterministic — route it to the bibliography toolchain, not to the model. Switching APA → a numbered style, abbreviating journal names, reordering author/year/title: these have exactly one correct output, and a CSL processor or biber produces it. Do not hand-retype entries — typing a bibliography by hand burns tokens and injects errors into a path that has a single right answer (CLAUDE.md → Model vs Code).
Two facts the model must hold:
- Presentation only. A style conversion changes how a fact is displayed — never the fact. The DOI, author list, year, title, and venue in
references.bibare immutable; the style decides ordering, punctuation, and abbreviation around them. If a conversion would change a DOI or an author name, that is a bug, not a reformat. - Never invent a missing field to satisfy a style. If the target style requires page numbers or a DOI and an entry lacks them, you do not fabricate one to make the build clean — you flag it
[VALUE — verify](agent_docs/citation-discipline.md → placeholder protocol). A fabricated page range is the same cardinal-rule violation as a fabricated citation.
This skill configures and runs the conversion and reports what is missing. It does not write .bib field values by hand.
When to Use
Invoke with /reference-format when:
- The manuscript's bibliography is in the wrong style for its target venue (drafted APA, the venue wants a numbered style).
- After retargeting (
/journal-fitsurfaced a style mismatch as a gap). - Normalizing inconsistent formatting (mixed "Last, First" / "First Last", mixed full/abbreviated journal names) — a deterministic clean-up, not a content edit.
State the target if it differs from the map: /reference-format ACL. Otherwise read it from MANUSCRIPT_MAP.md → Target journal.
Process
Phase 1: Identify Current and Target Style
- Read
MANUSCRIPT_MAP.md → Target journalto fix the target style. Map venue → style class: NeurIPS/ACL → numbered (author–year in text via the venue style file, ISO-4 abbreviations); IEEE → numbered[1]; APA → author–date with DOIs; Nature-family → superscript numerics. - Detect the current mechanism in the project:
- biblatex + biber — look for
\usepackage[style=...]{biblatex}and\addbibresource. Conversion = changestyle=. - natbib / classic bibtex — look for
\bibliographystyle{...}and\bibliography{}. Conversion = swap the.bst(e.g. the venue's provided style file). - pandoc + CSL — Markdown source compiled with
--citeproc. Conversion = swap the--cslfile.
- biblatex + biber — look for
- Confirm the venue's required style file exists — many venues (NeurIPS, ACL) ship a
.bstor class with the kit/submission template. Use the venue's own file rather than a generic approximation.
Phase 2: Apply the Conversion via the Tool
Pick the mechanism the project already uses; do not migrate engines unless asked.
- biblatex/biber — change the package option, e.g.
\usepackage[style=numeric-comp,sorting=none]{biblatex}for a numbered venue; rerunbiberthenlatexmk. - classic bibtex — set
\bibliographystyle{<venue>}(the provided.bst); rerunbibtexthenpdflatex. - pandoc/CSL — pass the target CSL, e.g.
pandoc paper.md --citeproc --csl=<venue>.csl --bibliography=references.bib -o paper.pdf.
In every case the engine rereads references.bib and re-renders. You do not edit the rendered output. If a field is genuinely missing (the entry has no doi and the target needs one), that is a Phase 3 flag — not something you type in.
Phase 3: Verify — Nothing Lost, Nothing Altered, Required Fields Present
After the tool runs:
- Entry count is conserved — the rendered bibliography lists the same number of works as before. A dropped entry usually means a malformed
.bibrecord the engine skipped — surface it. - Facts unchanged — spot-check that DOIs, author lists, years, and titles match
references.bib. The style changed; the data did not. Required fields for the TARGET style are present, per entry. Different styles demand different fields:
Target style class Commonly required fields APA (author–date) author, year, title, journal/venue, DOI; pages for articles IEEE / numbered author, title, venue, year; pages; volume/number for journals Nature-family author, title, journal, year, volume, pages NeurIPS/ACL numbered author, title, venue/booktitle, year; pages for proceedings For each entry missing a required field, record it — do not fill it from your prior.
- No fabrication to satisfy the style — every gap from step 3 becomes a
[VALUE — verify]flag in the report, never an invented value.
Output Format
# Reference Format — APA → ACL (numbered)
> Mechanism: biblatex + biber (detected \usepackage[style=apa]{biblatex}).
> Deterministic conversion — presentation only; no .bib field values edited by hand.
## Config / command to apply
Change the package option:
\usepackage[style=numeric-comp,sorting=none]{biblatex} % was style=apa
Then rebuild:
biber paper && latexmk -pdf paper.tex
(Use the ACL-provided .bst/style file if submitting via the ACL template.)
## Verification summary
- Entries before: 42 · rendered after: 42 · none dropped.
- Facts spot-checked: DOIs / authors / years unchanged (style-only re-render).
## Fields missing for the TARGET style (flag — do NOT invent)
| Bib key | Missing required field | Action |
|--------------|------------------------|--------|
| tooluse2023 | pages | [VALUE — verify] — get from the published proceedings |
| halluc2022 | pages, volume | [VALUE — verify] — confirm against the source PDF |
## Notes
- 2 entries need page numbers for the numbered style; flagged, not fabricated.
- If staying on classic bibtex instead: \bibliographystyle{acl_natbib} + bibtex run.Pairs With
/citation-audit— run after the conversion; it re-checks dangling keys, duplicates, malformed DOIs, and\ref↔\labelintegrity against the new style. The audit reads the bibliography; this skill re-styles it.citation-gate(.claude/hooks/citation-gate.sh) — fires after every.tex/.bibedit; confirms every\citestill resolves after the style swap. If it fails, a key broke in conversion.MANUSCRIPT_MAP.md— theTarget journalfield is the source of the target style; read it first.
Common Rationalizations
| Rationalization | Reality |
| "I'll just retype the entries in the new style" | One correct output exists — let biber/CSL produce it. Hand-typing injects errors into a deterministic path. |
| "The style needs a DOI; I'll add a plausible one" | A fabricated DOI is a cardinal-rule violation. Flag [VALUE — verify]; never invent it. |
| "This entry has no page numbers — I'll estimate the range" | Estimated pages are invented quantities. Flag and source them; the build can wait. |
| "I'll also fix a wrong author name while I'm here" | A wrong fact is a content fix, a Protected-Claim concern — not part of a style conversion. Surface it separately. |
| "Switch it to biblatex while reformatting" | Engine migration is a separate, larger change. Convert within the project's existing mechanism unless the author asks to migrate. |
Notes
- This is a Drafter-model / tooling task (
CLAUDE.md → Model Selection) — the model's only job is to pick the right config and read the missing-field report; the engine does the formatting. - The cardinal-rule edge case to hold: a missing required field is a flag, never a fill. Styles are satisfied by sourcing the field or by flagging it — never by invention.
- Keep facts and presentation strictly separate. If an edit changes a DOI, year, or author, you left "formatting" and entered "altering the record" — stop.
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.

