agentleFS
NilsHellwigNilsHellwig/acl-paper-skills/skills/literature/SKILL.md

literature

Skill3 starsChanged 15 days agoMITView on GitHub

Reading, judging and citing papers in an acl-paper project (has paper.config.json). Use before citing a paper, when deciding whether a paper is relevant, when checking that a citation supports its claim, when the user drops a PDF into the project or pastes a BibTeX entry, and when the bib sync reports unknown or unread keys.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run PK mark-read <key>. It refuses while Read or Claims is empty or the .md is missing.

    line 21
  2. Distinctive:

    When you tell the user a paper supports a claim, quote the body passage in chat.

    line 23
  3. Very specific:

    Keep one key per paper. Before citing, check literature/index.md for the same paper under another key (preprint and published version).

    line 28
  4. Distinctive:

    After a rewrite that touches a cited sentence, each resulting sentence that rests on the source keeps its citation.

    line 29

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

How papers move from "found" to "cited" in this project. Searching and fetching are the source skills' job (acl-anthology, arxiv, project sources in .claude/skills/); everything after the fetch is here.

PK means python3 ${CLAUDE_PLUGIN_ROOT}/scripts/paperkit.py, run from the project root (the folder with paper.config.json).

The rule

A paper is judged and cited only on its body: introduction, method, experiments, results, tables, limitations. The abstract (and a search hit's snippet) is for triage: it decides what to read, never what a paper shows. A citation stands once the body passage that supports it is in the notes.

Reading a paper

  1. Open literature/md/<key>.md. For long papers, grep it for the terms of the claim and the section headers first, then read the matching sections in full. Use the PDF (literature/pdf/<key>.pdf) for figures, table layout and printed page numbers.
  2. Fill literature/notes/<key>.md:
    • ## Read: which parts you read ("full paper", "Sec. 1-5, Tab. 2").
    • ## Claims this paper supports: one line per claim, in your words, with its body location and a short quote. Numbers exactly as printed in the paper.
    • ## Relevance to our paper: where and why it would be cited, or why not.
  3. Run PK mark-read <key>. It refuses while Read or Claims is empty or the .md is missing; fix what it names.

When you tell the user a paper supports a claim, quote the body passage in chat.

Citing

  • Cite only read-full keys, with \citet{} / \citep{}. Write the citation into the .tex and stop there: the PostToolUse hook moves the entry from literature/archive.bib into the paper bib, and moves it back when the last citation goes.
  • Keep one key per paper. Before citing, check literature/index.md for the same paper under another key (preprint and published version); when both exist, ask the user which to cite.
  • After a rewrite that touches a cited sentence, each resulting sentence that rests on the source keeps its citation.

Entries and PDFs that do not come from a source skill

  • User pastes a BibTeX entry: save it to a temp file and run PK bib-paste --file <tmp>.
  • User drops a PDF into the project: identify the paper from its first page, find its key in the paper bib or literature/archive.bib, and run PK add-local <pdf> --key <key>. No entry yet: stop with ⚠️, name the paper (title, authors, year, venue or DOI) and ask the user for the authoritative entry. File the PDF once the entry exists.
  • A paper with no fetchable source (book, report): ask for the entry and a PDF, then the two steps above.

Sync messages

The hook (and PK sync) reports:

  • unknown key: cited but in neither bib file. Fetch it through a source skill, or ask the user for the entry. Write no BibTeX yourself.
  • not read in full: cited before its notes were done. Read it now (steps above). If the body does not support the sentence, tell the user and propose a fix.

PK index rebuilds literature/index.md; PK sync runs everything by hand.

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.