← ClaudeAtlas

paper-anchorlisted

Use PAPER.md as the entry point for a paper's design, evidence, active tasks, and results. Use by default for paper-related work in projects whose rules adopt paper-anchor, or when the user asks to use it.
SPYfighting/my-academic-skills · ★ 24 · AI & Automation · score 84
Install: claude install-skill SPYfighting/my-academic-skills
# Paper Anchor ## Open the paper record Use this workflow for paper-related work when project rules adopt paper-anchor or the user requests it. In an adopting project it is the default. Read the relevant claims in the root `PAPER.md` if it exists. When the project first needs its paper design recorded, create `PAPER.md` directly from [the Markdown template](templates/PAPER.md). Start from available plans and evidence, mark proposed wording as a draft, and leave unknowns explicit. Read-only work uses any existing record as context and reports findings in the requested deliverable. Use `PAPER.md` as the project overview for claims, evidence, active research, and the next steps. Update it in place and preserve evidence IDs and recorded decisions. The [fictional example](examples/PAPER.example.md) shows the links for an active analysis. Reuse the project-local skill copy. Update it when the user asks to sync, keeping the existing `PAPER.md`, evidence IDs, and links. ## Plan and carry out research 1. Identify the paper question and relevant claim or evidence gap. Use stable IDs such as `R1` for claims and `R1.E1` for evidence. An authorized exploration can start with a specific uncertainty and acquire an evidence ID later. 2. For formal work, record the comparison, readout, controls, and what would support or weaken the claim. Keep details in project records. In the evidence row, link the Task from Planned work and link available interim or final results, figures, or tables