oprogramadorreal/optimus-claude / skills/paper-init
paper-init
VerifiedPrepares durable context for implementing and reproducing a paper from a URL, PDF, DOI, or arXiv id: sources, source-linked requirements, empirical acceptance criteria, uncertainties, scope, and data provenance under paper/. Downloads sources and datasets (into data/) and updates .gitignore, .gitattributes, and README routing. Context only: writes no implementation code and sets up no project stack.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 10.3 KB |
| SKILL.md | skill md | 22.9 KB |
| agents/openai.yaml | config | 198 B |
| references/empirical-reproduction.md | markdown | 9.5 KB |
| references/re-running.md | markdown | 3.0 KB |
references/re-running.md
View on GitHub# Re-running on an existing bundle
Same paper — a resolved identifier (DOI, arXiv id) matches
`source/metadata.json`, or one source names the other's identifier (an arXiv
page listing the published DOI): refresh in place — update, don't duplicate,
and keep the original acquisition records (append the refresh; a preprint's
provenance is not overwritten by its published version's). When the match is
uncertain, ask before touching the existing bundle. Preserve target
and question IDs, decision rationale, and history. A scope decision in
`metadata.json` binds the selected scope. For empirical papers, apply it in
`acceptance.md`; `spec.md` keeps the original reported results. For older
empirical bundles that reduced the spec's targets, migrate those decisions
into acceptance and recover the paper's
originals from sources. Surface conflicts when a new source revision makes
an earlier decision inapplicable; never silently drop or reinterpret it.
Retire removed requirement IDs with a reason instead of reusing or renumbering
them. Read existing decision ledgers, including `decisions.md` if present;
preserve them and do not reopen settled questions without new evidence.
Before replacing context used by an active or past evaluation, preserve its
bar and linked protocols in a revision snapshot. Consult existing evaluation
records when available. Record changed requirements and which evidence needs revalidation;
never overwrite run artifacts, logs, or critic verdicts, or silently replace
an active run's fixed bar. A new acceptance revision is a proposed bar for a
new evaluation, not permission to relax failed criteria. Preserve necessary
source versions and acquisition records too. Snapshots inherit the source
license and ignore rules: never expose ignored sources or reference code by
copying them into a tracked archive. Git history stands in for a snapshot
only when it actually retains the prior bytes.
Cited works already in `paper/cited/` are kept, not re-fetched unless the
required source version changes or a missing file must be re-acquired;
when the revision drops a citation the bundle fetched, ask before removing
its directory. A different paper while
`paper/` already holds one: use `papers/<slug>/` (kebab-case slug from the
title) as the bundle root everywhere — datasets go in `papers/<slug>/data/`
with their own `data/README.md`, and every `.gitignore` and `.gitattributes`
entry (license-rule entries and `!` exceptions included) and the
`git check-ignore` check use nested paths (`paper/` becomes `papers/<slug>/`,
`data/` becomes `papers/<slug>/data/`): a pattern containing slashes anchors
at its file's location, so bare paths cannot reach a nested bundle. Leave
the existing bundle untouched and add the new one to the routing block. If
`papers/<slug>/` already holds a different paper, disambiguate the slug
(append the year or venue) — never
refresh a bundle that is not the same work. Never merge two papers into one
bundle; never move an existing `paper/` — that restructuring is the user's
call.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |