Przejdź do treści
Biblioteka skilli
Nauka i badania · Przegląd i audyt

references

/references

Przegląda i porządkuje bibliografię repozytorium swarm-routing, potwierdza wpisy w Crossref lub Zenodo i odświeża tabelę źródeł.

Repozytorium
skills ↗
Licencja
LGPL
Ostatnia zmiana repozytorium
13.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
54
Skrypty
13
Komentarze HTML
2
Adresy URL w SKILL.md
3
Przestarzałość

Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

LGPL, otwarta.

Co sprawdzić przed instalacją
  • 13 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
  • SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.

Skrypty: evals/crossref-error-two-records/graders/01-bib-check-clean.sh, evals/crossref-error-two-records/graders/02-year-2005.sh, evals/crossref-error-two-records/place-files.sh, evals/datacite-doi-on-repository-record/graders/01-bib-check-clean.sh, evals/datacite-doi-on-repository-record/graders/02-datacite-doi.sh, evals/datacite-doi-on-repository-record/place-files.sh, evals/protocol-sheet-to-bib/grader

Co robi i kiedy

Przegląda i porządkuje bibliografię repozytorium swarm-routing, potwierdza wpisy w Crossref lub Zenodo i odświeża tabelę źródeł.

Oryginalny opis (EN)

Review and set up a swarm-routing repository's bibliography, docs/references.bib: find every paper, thesis, dataset and org release the repository relies on, confirm each from Crossref or Zenodo, write the entries with their fidelity keys and a role, then regenerate the fidelity Sources table and CITATION.cff references from the bib and check them. Use whenever a repository needs its references.bib (epic swarm-routing/.github#307 and its per-repo tickets), a paper is added to or dropped from a fidelity sheet, a README or doc cites a work by hand, CITATION.cff references look stale, someone ask

Jak działa

  1. The rules the scripts enforce, and why
  2. 1. Inventory
  3. 2. Confirm each work and write its entry
  4. 3. Regenerate
  5. 4. Verify and hand over
  6. Reporting without changing anything
Sekcje z nagłówków SKILL.md, w oryginale · 198 linii, 1 846 słów
Podgląd SKILL.md
---
name: references
description: "Review and set up a swarm-routing repository's bibliography, docs/references.bib: find every paper, thesis, dataset and org release the repository relies on, confirm each from Crossref or Zenodo, write the entries with their fidelity keys and a role, then regenerate the fidelity Sources table and CITATION.cff references from the bib and check them. Use whenever a repository needs its references.bib (epic swarm-routing/.github#307 and its per-repo tickets), a paper is added to or dropped from a fidelity sheet, a README or doc cites a work by hand, CITATION.cff references look stale, someone asks which papers an implementation follows or how to cite them, or a reference shows a bare URL where a DOI exists. Script first: the scripts fetch every field; you never type a DOI, author or title from memory."
license: MIT OR GPL-2.0-only
compatibility: Needs git, python3 and network access to github.com (scripts/org-tool clones swarm-routing/.github tools/), api.crossref.org and zenodo.org.
metadata:
  author: swarm-routing
  repository: https://github.com/swarm-routing/skills
---

# references

Every implementation in the org rests on papers, and a reader must be able to
go from the code to the exact work it follows. `docs/references.bib` is the one
place a repository records those works (swarm-routing/.github#307). Everything
else that lists them is generated from it: the fidelity sheet's Sources table,
`CITATION.cff` `references:`, the README's citing section and the site's
project page. A hand-typed copy drifts and a field typed from memory is wrong
often enough to matter, so the scripts write the fields and you decide what
belongs and why.

Set once, then work from the repository's checkout:

```bash
SKILL="${CLAUDE_PLUGIN_ROOT}/skills/references"   # as the Claude Code plugin
# installed with skills.sh (npx skills add): SKILL=<the directory this SKILL.md is in>
T="$SKILL/scripts/org-tool"    # T fidelity|lit-search|zenodo|org-sync ...
```

`ORG_TOOLS_DIR=<checkout of swarm-routing/.github>` points the wrapper at a
local checkout instead of the cached snapshot.

## The rules the scripts enforce, and why

- **DOI links first.** A reference with a DOI is shown as its
  `https://doi.org/<DOI>` link everywhere: the link survives publisher
  moves, and a reader lands on the version of record. `url` is for a work
  with no DOI (a thesis in a university repository, a technical report, an
  arXiv preprint without a DataCite record). When an entry has only a `url`,
  look for a DOI before accepting it (step 2).
- **Keys are the fidelity keys** (`G02`, `R05`, `DDG04`), so `[G02] §3.2` in
  the sheet, in a code comment and in the bib is one work. A work in
  CONTRIBUTING's "References" key table takes the table's key in every
  file; where another bib in the repository (AntHocNet's `paper/paper.bib`)
  uses a different key for it, rename it there and in every `[KEY]` and
  `\cite{}` that uses the old key (`git grep` it). Otherwise reuse the key
  that other bib already uses, or the sheet's when it cites numbers: one key
  per work across every file, and entries both files carry stay identical.
- **Each entry has a role** in `keywords`: `implemented` (what the code
  follows), `restates` (a later description of the same algorithm),
  `compared` (a protocol or result the repository compares against),
  `dataset`, `tool` (software it builds on: ns-3, an org release),
  `background`. The roles decide what reaches `CITATION.cff`
  (`implemented`, `tool`, `dataset`).
- **Never the repository's own DOI**: that is `CITATION.cff`'s own `doi`;
  listing it again makes the repository cite itself.
- **Never the private paper store.** The org keeps paper copies in a private
  repository; a public file never names it, points into it, or says where a
  copy is kept. Say what was read and cite it by its DOI link.
- **A repository that used no paper** still has the file: it lists the org
  releases it builds on (`tool`), or stays empty with the header that says
  so.

## 1. Inventory

```bash
"$T" fidelity bib check .            # the bib against the sheet, the rules above, the private-library text
"$T" fidelity bib check . --online   # also asks Crossref for a DOI for every url-only entry
```

It lists, one line each: keys the sheet cites that the bib lacks, entries no
file cites and that carry no role, entries with neither `doi` nor `url`, a
rendered reference that is not its DOI link, url-only entries Crossref can
match, and every public line that mentions the private library.

Then find what the repository cites outside the sheet, since those are the
references a protocol's bib most often misses:

```bash
"$T" fidelity bib scan .             # read-only: every DOI and [KEY] cited outside the bib, then the bib
```

It prints each DOI (as its doi.org link) and each `[KEY]` cited in the
repository's prose and in code and YAML comments once, with its first place,
how many more there are, and whether the bib holds it (`in the bib as [KEY]`,
`NOT in the bib`, or the repository's own DOI); then every bib entry as key,
role and link, `(no doi)` on a url-only one. It skips `skills/*/evals/` and
lookup tools' test fixtures: test inputs, not references. Read every
`NOT in the bib` line: a work the code or a doc relies on needs an entry;
a survey a doc merely mentions, or another release of the repository itself,
may stay out. Also check the org releases the repository builds on (a pinned
`core/`, a harness, an image) and test fixtures derived from a published
dataset (they cite the dataset), which no scan can see.

## 2. Confirm each work and write its entry

```bash
"$T" fidelity bib entry DOI --key G02 --role implemented   # a BibTeX entry from Crossref's record
"$T" lit-search confirm DOI                                # Crossref vs Semantic Scholar and OpenAlex, field by field
"$T" lit-search confirm --title "exact title" --year 2007  # a work without a DOI: find one, or confirm it has none
"$T" fidelity bib entry --url URL --key W07 --role implemented   # a work with no DOI: from its repository's record
"$T" zenodo bibtex REPO --role tool                        # an org release: its concept record as @software, keyed from CONTRIBUTING's table
```

Paste the printed entry into `docs/references.bib` as it is. Run `confirm`
when `bib entry` or the sheet disagree with each other: a `differ` in year or
pages is settled on the publisher's page (online-first year against issue
year is the usual cause), never by picking the convenient value; say which
you used in the PR. A work that seems to have no DOI may still have a DataCite one
(university repositories, technical reports): `bib entry --url` on the
repository's landing page refuses when the page names one and prints the
`bib entry DOI` command to run instead. A work that has no DOI takes its entry
from `bib entry --url` on its institution's or publisher's landing page (a
handle such as `https://hdl.handle.net/1993/20935` is best): the page's
`citation_*` tags and the repository's OAI-PMH record give the fields, the
handle's url and no `doi`; paste it as it is, never a copy's url. A field the
record lacks stays out (a thesis whose record names no degree is `@misc`, with
no `school`): do not add it by hand, say in the PR what the record lacks. When
it refuses (no title, author or year in the record), the work is unconfirmed,
as below. If nothing confirms a work, do
not add it: name it in the PR as unconfirmed, and reword every place the
sheet cites its key (`[R05] §3`) to name the work in prose instead, since
`bib check` fails on a cited key the bib lacks. A row whose Source rests on that work
alone gets Source `unknown` (the sheet's check accepts only a `[KEY]`
locator, `repo choice` or `unknown` there) and names the work in its Status.

Two cases need care:

- **A Crossref record that is wrong or thin** (an author missing, diacritics
  dropped, given and family names swapped, words run together, no year): the publisher's page decides. Correct that one field by hand,
  and say in the PR which field, what Crossref had and which page settled
  it. Without the publisher's page, an error two other
  records agree on (`lit-search confirm` prints them) may be corrected from
  them, said in the PR; otherwise keep Crossref's value and say so.
- **A work with no DOI whose title matches another work** (a dissertation
  and the later book chapter with its title): `bib check --online` keeps
  warning that the title has a DOI. Keep the url when the sheet cites the
  work without a DOI (its locators are the dissertation's), and name the
  other work's DOI in the PR so a reviewer sees it was ruled out.

An entry may carry a `note`: one line, in the repository's words, saying
why the work is cited (org-sync renders it as the role line; without it the
role's generic sentence is shown). Neither script writes it; add it after
pasting. Keys are one per work across the org: use the key CONTRIBUTING's
"References" key table gives the work (`zenodo bibtex` fills it in for an
org release); a work not in the table takes its fidelity key. A repository that
cites nothing keeps the seed header and may add a `%` line saying why.

Keep the entries sorted by key. Give each the narrowest true role; when a
work is both followed and compared against, `implemented` wins.

## 3. Regenerate

```bash
"$T" fidelity bib sources .                 # the Sources table in docs/fidelity.md, between its markers
"$T" org-sync apply .                       # the README's citing section
"$T" org-sync reseed CITATION.cff .         # CITATION.cff is a seed: apply never rewrites it
```

A sheet whose Sources table has no `<!-- fidelity:sources:begin -->` /
`<!-- fidelity:sources:end -->` markers gets them around the existing table
(the table is the bib's from then on). `org-sync apply` also rewrites any
other template drift the repository carries; keep only the citing changes
in this PR (`git checkout` the rest) and leave the drift to org-bot's
refresh PR.

The bib takes over `CITATION.cff` and the README's citing list once it holds
an entry; from then on org-sync warns that the repository's `[[references]]`
in `.github/org-sync.toml` is redundant: remove that table in the same PR, so
the bib is the only source. A repository without `citation = true` in its org-sync config keeps its own
README citing section and `CITATION.cff`: org-sync renders neither, so
update only `CITATION.cff`'s `references:` (the org's references tooling
writes that block alone; see CONTRIBUTING "References") and leave the rest.
A repository with no `.github/org-sync.toml` is not on the templates yet:
do not run `org-sync init` for this task; say that `CITATION.cff` and the
README were not regenerated and that `org_sync.py apply` is the remaining step.
Never edit a generated section by hand: the next run undoes it. If a fidelity
row's prose names a work the bib does not hold, add the entry; if a source is
no longer cited, drop its entry or give it a role that explains why it stays.
Reword every private-store line the check printed, then grep for what the
check cannot see: paths into the store (a `$PAPERS/...` variable, a
`<repo>/library/...` path, a home-directory default) and words for it
(the private repository's name followed by "repo", "the library"); reword
those too.

## 4. Verify and hand over

```bash
"$T" fidelity bib check . --online   # clean
"$T" org-sync check .                # no drift
```

Open the PR with a `docs:` title (`docs: docs/references.bib holds the
protocol's sources`), `Part of` the repository's ticket while a box stays
open, and in the body: the entries added (key, role, DOI link), any `differ`
and how it was settled, works left unconfirmed, and the private-library lines
reworded.

## Reporting without changing anything

Asked only which papers a repository follows, or how to cite it: run step 1
and answer from `bib scan`'s list of entries, with their DOI links and roles.
The list has no titles, authors or years; when the answer needs them (a
url-only entry, a formatted citation), read that entry alone:
`git grep -n -A10 '{KEY,' -- docs/references.bib`. Name anything the check or
the scan printed, but make no change.
Pliki w paczce (54)
  • SKILL.md 12 KB
  • evals/crossref-error-two-records/case.yaml 1 KB
  • evals/crossref-error-two-records/place-files.sh 1 KB
  • evals/crossref-error-two-records/prompt.md 1 KB
  • evals/crossref-error-two-records/files/docs/references.bib 1 KB
  • evals/crossref-error-two-records/graders/01-bib-check-clean.sh 1 KB
  • evals/crossref-error-two-records/graders/02-year-2005.sh 1 KB
  • evals/crossref-error-two-records/graders/03-year-from-two-records.md 1 KB
  • evals/crossref-error-two-records/graders/04-title-and-other-fields.md 1 KB
  • evals/datacite-doi-on-repository-record/case.yaml 1 KB
  • evals/datacite-doi-on-repository-record/place-files.sh 1 KB
  • evals/datacite-doi-on-repository-record/prompt.md 1 KB
  • evals/datacite-doi-on-repository-record/files/docs/references.bib 1 KB
  • evals/datacite-doi-on-repository-record/graders/01-bib-check-clean.sh 1 KB
  • evals/datacite-doi-on-repository-record/graders/02-datacite-doi.sh 1 KB
  • evals/datacite-doi-on-repository-record/graders/03-doi-from-repository-record.md 1 KB
  • evals/datacite-doi-on-repository-record/graders/04-fields-match-datacite.md 1 KB
  • evals/protocol-sheet-to-bib/case.yaml 1 KB
  • evals/protocol-sheet-to-bib/place-files.sh 1 KB
  • evals/protocol-sheet-to-bib/prompt.md 1 KB
  • evals/protocol-sheet-to-bib/files/docs/fidelity.md 1 KB
  • evals/protocol-sheet-to-bib/graders/01-bib-check-clean.sh 1 KB
  • evals/protocol-sheet-to-bib/graders/02-dois-from-scripts.md 1 KB
  • evals/protocol-sheet-to-bib/graders/03-doi-links-rendered.md 1 KB
  • evals/protocol-sheet-to-bib/graders/04-no-private-library.md 1 KB
  • evals/protocol-sheet-to-bib/graders/05-roles.md 1 KB
  • evals/protocol-sheet-to-bib/graders/06-unconfirmed-left-out.md 1 KB
  • evals/protocol-sheet-to-bib/graders/07-urls-looked-up.md 1 KB
  • evals/report-without-change/case.yaml 1 KB
  • evals/report-without-change/place-files.sh 1 KB
  • evals/report-without-change/prompt.md 1 KB
  • evals/report-without-change/files/docs/references.bib 1 KB
  • evals/report-without-change/graders/01-names-roles.md 1 KB
  • evals/report-without-change/graders/02-doi-link.md 1 KB
  • evals/report-without-change/graders/03-no-change.md 1 KB
  • evals/report-without-change/graders/04-w07-url-ddg04-no-doi.md 1 KB
  • evals/tooling-no-paper/case.yaml 1 KB
  • evals/tooling-no-paper/place-files.sh 1 KB
  • evals/tooling-no-paper/prompt.md 1 KB
  • evals/tooling-no-paper/files/CITATION.cff 1 KB
  • evals/tooling-no-paper/files/README.md 1 KB
  • evals/tooling-no-paper/graders/01-bib-check-clean.sh 1 KB
  • evals/tooling-no-paper/graders/02-releases-from-zenodo.md 1 KB
  • evals/tooling-no-paper/graders/03-not-own-doi.md 1 KB
  • evals/tooling-no-paper/graders/04-no-invented-paper.md 1 KB
  • evals/tooling-no-paper/graders/05-org-sync-gap-named.md 1 KB
  • evals/url-only-has-doi/case.yaml 1 KB
  • evals/url-only-has-doi/place-files.sh 1 KB
  • evals/url-only-has-doi/prompt.md 1 KB
  • evals/url-only-has-doi/files/docs/references.bib 1 KB
  • evals/url-only-has-doi/graders/01-bib-check-clean.sh 1 KB
  • evals/url-only-has-doi/graders/02-ddg04-gets-doi.md 1 KB
  • evals/url-only-has-doi/graders/03-thesis-keeps-url.md 1 KB
  • scripts/org-tool 5 KB

Wersje

W bazie nie ma innych skilli o nazwie references.

Migawka bazy z 13.11.2026 · wersja paczki 163b12c0691a (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100zenodo-release
    Publikuje dane projektu w Zenodo jako nową wersję rekordu: najpierw próba, potem sandbox, a produkcja dopiero po wyraźnym potwierdzeniu, z zapisem DOI w MANIFEST.yaml i CITATION.cff.
  • 100validate-bib
    Sprawdza wpisy bibliografii względem cytowań w tekście i szuka brakujących oraz nieużywanych pozycji.
  • 100cite-verify
    Sprawdza w pliku LaTeX, czy każdy klucz cytowania istnieje w BibTeX, a wpisy są prawdziwe i zgodne z Crossref lub arXiv.
  • 100bib-verify
    Weryfikuje plik BibTeX pod kątem zmyślonych źródeł, porównując każdy wpis z CrossRef, arXiv i DBLP i raportując różnice w tytule, autorach, roku i DOI.
  • 90release
    Wydaje cytowalną wersję ww3-gpu i pilnuje metadanych cytowania: DOI, CITATION.cff, .zenodo.json i odznaki w README.
  • 10002-bib-verify
    Weryfikuje plik BibTeX pod kątem zmyślonych odwołań, porównując każdy wpis z CrossRef, arXiv i DBLP i raportując rozbieżności w tytule, autorach, roku i DOI.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.