agentleFS
Sign inStart free
JunMA98JunMA98/Computer-science-claude-skills/skills/citation-management/SKILL.md

citation-management

Skill3 starsChanged 8 months agoMITView on GitHub

Manage citations and BibTeX for computer science papers, theses, surveys, rebuttals, and project reports. Use when verifying DOI or arXiv metadata, cleaning `.bib` files, deduplicating references, formatting venue-ready citations, or checking that paper, code, and artifact references are consistent.

30 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use experimental-design and hypothesis-generation.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ffsshhttiikkSkill

    experimental-design

    Experimental design for A/B testing and research

    Also in 3 projects that use this

  • garri333Skill

    hypothesis-generation

    Structured hypothesis formulation from observations. Use when you have experimental observations or data and need to formulate testable hypotheses with predictions, propose mechanisms, and design experiments to test them. Follows scientific method framework. For open-ended ideation use scientific-brainstorming; for automated LLM-driven hypothesis testing on datasets use hypogenic.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 6

    Distinctive

    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
  1. Distinctive:

    Use this skill for CS bibliography hygiene.

    line 8
  2. Very specific:

    Use booktitle for conference papers and journal for journal articles.

    line 22
  3. Distinctive:

    Avoid citing a project page when an actual paper exists, unless the project page is the artifact being referenced.

    line 23
  4. Distinctive:

    Keep software or library citations aligned with what the paper or repo actually used.

    line 24
  5. Distinctive:

    Use these local tools when they help:

    line 29
  6. Distinctive:

    When the user asks for citation help without a strict format, return:

    line 47
  7. Distinctive:

    follow-up actions if a citation still needs manual confirmation

    line 51

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

Citation Management

Use this skill for CS bibliography hygiene. Prefer canonical metadata from DOI, arXiv, DBLP, Crossref, publisher pages, or Zotero exports over hand-copied references.

Default Workflow

  1. Normalize identifiers first: DOI, arXiv ID, URL, title, citation key.
  2. Retrieve metadata from the most reliable source available.
  3. Validate author order, title casing, venue name, year, and pages.
  4. Distinguish preprint, conference, workshop, journal, and software citations.
  5. Format clean BibTeX and record unresolved ambiguities.

CS-Specific Checks

  • Distinguish arXiv preprints from the archival conference or journal version.
  • Preserve canonical venue names and abbreviations when the target style expects them.
  • Use booktitle for conference papers and journal for journal articles.
  • Avoid citing a project page when an actual paper exists, unless the project page is the artifact being referenced.
  • Keep software or library citations aligned with what the paper or repo actually used.
  • Watch for duplicate entries caused by conference and journal extensions of the same work.

Local Resources

Use these local tools when they help:

  • scripts/doi_to_bibtex.py
  • scripts/extract_metadata.py
  • scripts/format_bibtex.py
  • scripts/validate_citations.py
  • assets/bibtex_template.bib
  • assets/citation_checklist.md

Read references selectively:

  • references/metadata_extraction.md
  • references/citation_validation.md
  • references/bibtex_formatting.md
  • references/google_scholar_search.md only when canonical metadata is missing elsewhere

references/pubmed_search.md and scripts/search_pubmed.py are inherited upstream resources. Ignore them unless the actual task crosses into biomedical literature.

Default Output

When the user asks for citation help without a strict format, return:

  1. cleaned citation entries or BibTeX
  2. metadata uncertainties or conflicts
  3. duplicates or versioning issues
  4. follow-up actions if a citation still needs manual confirmation

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