# Apollo Sheets

> Render a Markdown report as a print-ready PDF review sheet in the style of the Apollo Operations Handbook (numbered paragraphs, ruled tables, cautions, checklists, change bars, line-art block diagrams and graphs, timelines, plots, maps, memory maps, bit fields, bar charts, matrices, trees, labelled pictures and many more figures drawn from text). Use when the user asks for an Apollo sheet, a handbook-style or NASA-style report, or a printable review sheet of a report, design or procedure.

- Skill: `hed0rah/apollo-sheets` (Agent Skill, multi-file: 92 files)
- Install (CLI): `npx get-skill add hed0rah/apollo-sheets`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hed0rah/apollo-sheets/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: hed0rah (https://skillmd.com/u/hed0rah)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/hed0rah/apollo-sheets

---


# apollo-sheets

`sheet.py` turns Markdown into a PDF through headless Chrome. Start from `template.md`. The reference sheet
`examples/apollo/apollo.md` shows every block beside its source; `README.md` summarizes the syntax.

## Workflow

1. Write or take the report as Markdown. Add front matter (title, section, tab, system, doc, mission, date).
   Quote any value that contains a colon.
2. Use the blocks where they carry information: `:::diagram` for a signal or data path, or a graph with
   `diamond` decisions, `bend=R` back-edges and `loop` self-edges; `:::timeline` for a sequence, `:::plot` for
   CSV data or exact `fn` curves (`panel` for a second panel on the same x), `:::table` for anything tabular,
   `:::checklist` for a procedure, `:::caution` / `:::warning` for hazards, `:::sequence` for hand-offs or
   protocols, `:::signals` for timing, `:::budget` for used-against-capacity, `:::stack` for layers or a memory
   map, `:::bits` for register or packet fields, `:::bars` for categories, `:::matrix` for a feature comparison,
   `:::tree` for a hierarchy, `:::callouts` to name the parts of a picture, `:::scatter` (`point X Y "LABEL"`,
   `fit`) for two quantities, `:::dist` for a spread, `:::sankey` for flows, `:::treemap` for nested shares,
   `:::quadrant`, `:::venn` and `:::funnel`, `:::map` for places, routes and choropleths, `:::contour`,
   `:::raster` and `:::polar` for fields and directions, `:::waterfall`, `:::waffle`, `:::slope`, `:::parallel`
   and `:::network`, `:::equations` and `:::symbols` for derivations. Options worth knowing: `area`, `percent`
   and `err=` on a plot, `percent` and `dots` on bars, `strip` and `ecdf` on a dist, `shade` on a matrix for a
   heatmap, `ends=1:N` and `lane` on a diagram, `milestone` and `after` on a timeline, a `::::row` of three or
   more for small multiples, `[[spark 3 5 4 8]]` inline. `CATALOG.md` picks a figure by the job it does, and
   section A.9 of the reference sheet is a table for choosing one. A block that holds
   blocks takes four colons (`::::changed` around `:::equations`).
   A long document organizes with parts (`# Part` then `:::part` with `thesis:`), a `status=` on each mechanism's
   `##` heading (`built`, `prototyped`, `designed`, `speculative`), `link=#anchor` on the nodes of a system-map
   `:::diagram`, a `:::trace` (`step "label" | what happens | #anchor`) to walk one thing through the system, and a
   `:::glossary` (`term | definition`); `examples/core-blocks` shows all five.
3. Render with page PNGs and look at every page:

       python <skill dir>/sheet.py report.md --png

4. Fix what overlaps. Diagram edges route round other boxes (one elbow, else a Z through a gap); if none
   clears, move nodes or use `bend=R` rather than accept an edge through a box. Keep timeline `call` lettering
   clear of the tick labels, and put callout points where their leaders do not cross the picture's own lettering.
   Keep wide figures (`bits`, `signals`, `sankey`, `treemap`, `timeline`, a heatmap) out of `::::row`. An
   unclosed block, a missing image or a bad figure spec stops the render with a message naming the block.

To ingest someone else's report without editing it, set front matter from the command line:
`-s section=3 -s tab=PHY`.

For a screen, the same source renders as an Interactive Whitepaper, one HTML file with a rail, cross-references
and light and dark: `python <skill dir>/web.py report.md`. Links between parts (`[text](#heading-slug)`,
`#fig-N.M`, `#tab-N.M`) work there and print as their words on paper. It needs the page template, `SHEET_TEMPLATE`.

Requirements: Python 3.8+ with matplotlib, numpy and pyyaml, Chrome or Chromium, the URW base35 fonts.
`SHEET_FONTS` and `SHEET_CHROME` override the font directory and browser.

