# Paper Playbook

> Use when drafting or restructuring a cryptography paper (IACR LNCS / IACR journal / security-conference format). Gives the overall skeleton, page budget, and the rhetorical moves of every section from title to appendix, with good/bad toy examples.

- Skill: `jiayaoqijia/paper-playbook` (Agent Skill, multi-file: 20 files)
- Install (CLI): `npx get-skill add jiayaoqijia/paper-playbook`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jiayaoqijia/paper-playbook/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: jiayaoqijia (https://skillmd.com/u/jiayaoqijia)
- Updated: 2026-11-12
- Page: https://skillmd.com/skills/jiayaoqijia/paper-playbook

---


# Paper Playbook — structure and rhetorical moves for crypto papers

The playbook fixes the **form** of a paper; the content is always rewritten for the
new paper. Templates here are structures, not wording to copy.

## Five principles (read first)

1. **Every number has one source.** Abstract, intro, body, tables and appendix quote
   the same value from the same row of `EVIDENCE.md`. No number enters the paper
   without an EVIDENCE row (SPEC §3). Numbers are generated or grep-checked, never
   retyped from memory.
2. **Write falsifiable claims first, then try to break them.** Each contribution is
   first written as one sentence in `CLAIMS.md`; the `falsifier` and `reviewer-sim`
   agents attack it before the prose is polished.
3. **Form is fixed, wording is new.** Reuse the skeleton and the moves, never the
   sentences of a previous paper.
4. **The body carries the weight; the appendix only supplements.** Reviewers are not
   obliged to read appendices. No claim in the body may depend solely on an appendix.
5. **Late edits are only necessary and verifiable ones.** In the last 24 hours before
   a deadline, fix errors only; no stylistic rewrites.

## Section files

| file | section |
|---|---|
| `sections/00_overall_structure.md` | skeleton, page budget, layout hard rules, notation freeze |
| `sections/01_title.md` | title patterns and anti-patterns |
| `sections/02_abstract.md` | three-part paradigm (state of the art → technique → results/artifact) |
| `sections/03_introduction.md` | funnel → pipeline → objective equation → open question |
| `sections/04_contributions.md` | lead-in + ordered bullets; wording rules |
| `sections/05_technique_overview.md` | recall routes → reduce to questions → insights answer them |
| `sections/06_related_work.md` | organise by axis not by time; comparison table; bridge paragraph |
| `sections/07_preliminaries.md` | compact notation table, only what is reused |
| `sections/08_main_construction.md` | statement → construction → cost/selection rule |
| `sections/09_security_correctness.md` | security claim, attack checklist, correctness/noise |
| `sections/10_experiments.md` | nine-part evaluation section; number discipline |
| `sections/11_conclusion.md` | two-to-three sentence conclusion |
| `sections/12_appendix.md` | appendix organisation; "not load-bearing" rule |
| `examples/toy_abstracts.md` | good/bad abstracts for three toy papers |
| `examples/toy_intro_and_contributions.md` | toy intro funnel + contribution list, good vs bad |
| `examples/toy_overview_and_related.md` | toy technique overview and related-work table |

Toy papers used throughout (all numbers are **invented and illustrative**):

- **T1 (FHE):** "faster programmable bootstrapping (PBS) via LUT packing" — pack
  several small lookup tables into one test polynomial.
- **T2 (symmetric):** "a new 6-round differential distinguisher for a toy SPN" found
  by SAT-based trail search.
- **T3 (protocols):** "PSI with lower communication" via a toy OPRF + cuckoo-hash
  variant.

## Workflow (used by the `writer` agent)

1. Freeze notation and the framework's one-word name (`00_overall_structure.md`).
2. Write `CLAIMS.md` rows for each contribution; get falsifier verdicts.
3. Draft in this order: contributions → technique overview → main construction →
   experiments → related work → introduction → abstract → title → conclusion.
   (The abstract is written last because it summarises the other sections.)
4. After each section, run the section's checklist (end of each file).
5. Hand to `reviewer-sim`; iterate; hand to `submission-rebuttal`.

## Related skills

- [abstract-craft](../abstract-craft/SKILL.md), [technique-overview](../technique-overview/SKILL.md),
  [related-work-writing](../related-work-writing/SKILL.md),
  [experiments-writing](../experiments-writing/SKILL.md),
  [venue-calibration](../venue-calibration/SKILL.md), [polish-writing](../polish-writing/SKILL.md)
- LaTeX skeleton: `templates/paper/`.

