Skip to content
Back to search

sheets-to-playbook

SkillWorks with Claude CodeGitHub

Run a round-table workshop on paper, photograph the sheets, and get an accessible playbook website where every line traces back to the photos. Paper kit, slides and a Claude Code skill.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/chris-keene--sheets-to-playbook/badge.svg)](/listings/chris-keene--sheets-to-playbook)

HTML

<a href="/listings/chris-keene--sheets-to-playbook"><img src="/api/listings/chris-keene--sheets-to-playbook/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

git clone https://github.com/Chris-Keene/sheets-to-playbook.git && cd sheets-to-playbook
pip install -r requirements.txt

python3 build/build.py                 # the example playbook and a blank template, in playbook/
python3 print/build_paper.py           # print-ready kit in print/out/paper/, zipped in print/out/
python3 print/build_sheets_html.py     # fillable HTML sheets in print/out/html/
python3 slides/build_slides.py         # slides/out/slides.html

Open `playbook/index.html` to see what you'll end up with. Every build reads `playbook.config.json`; try `--config examples/can/playbook.config.json` on any of them to see a fully branded version.

Then open Claude Code in this folder. The `sheets-to-playbook` skill is picked up automatically. To use it from anywhere, run `python3 tools/install_skill.py`.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 122 lines
  1. # sheets-to-playbook
  2. Run a round-table workshop on paper, photograph the sheets, and have a playbook website the same afternoon, where every line traces back to something someone wrote.
  3. ![The example playbook's home page: a blue band headed "Growing and sustaining support for accessibility", with counts of themes, challenges, actions and commitments, and a ring of arrows standing for the tables in the room](docs/playbook.png)
  4. It comes in four parts:
  5. | Part | What it is | Where |
  6. | --- | --- | --- |
  7. | **Paper kit** | Three A1 worksheets that walk a table from problem to action, a side sheet for quotes and resources, a perforated commitment card and table cards. Print-ready PDFs plus fillable HTML versions. | `print/` |
  8. | **Facilitator slides** | One self-contained HTML deck with built-in timers, and a PDF backup. | `slides/` |
  9. | **Photo-to-playbook engine** | Claude Code reads the photographed handwriting, one sub-agent per table, and writes a draft playbook. Scripts prepare the photos, check coverage and blur, and verify that nothing was invented. | `ingest/`, `.claude/skills/` |
  10. | **Review app and site builder** | A keyboard-first app for confirming uncertain words against close-ups of the photos, and a builder for the finished, accessible website. | `tools/review/`, `build/` |
  11. It was built for the CAN Community Forum (Champions of Accessibility Network) in November 2026, and opened up after people at the session asked to run their own.
  12. ## How it works
  13. 1. **Before the day:** set your names and colours in `playbook.config.json`, then build the paper kit and the slides.
  14. 2. **On the day:** each table works through the three sheets. A table lead writes, everyone else talks. People fill in a commitment card, tear off the stub and hand it in.
  15. 3. **Straight after:** photograph every sheet and every stub. Hand the folder to Claude Code: *"build the playbook from this folder"*.
  16. 4. **Claude prepares and checks the photos**, tells you at once if a sheet is missing or blurred (while it's still on the wall), then reads every table in parallel.
  17. 5. **It writes a draft playbook** and a review pack. Every line cites the photo it came from; `verify` fails anything it can't trace, any quote that drifted from the words on the sheet, and any name left in.
  18. 6. **A person reviews it.** Uncertain words are flagged, never guessed; the review app gets through them quickly.
  19. 7. **Publish:** one command builds a static site you can host anywhere.
  20. [On the day](docs/on-the-day.md) has the timeline, roles and commands.
  21. ## The rules it keeps
  22. - **Nothing invented.** Every line on the page traces to a photo. Empty is better than plausible. Claude may not add examples, statistics or advice from general knowledge, and `ingest.py verify` enforces it.
  23. - **Uncertain words stay marked.** A word that can't be read for certain is written `[?word]` and goes to a human. In our handwriting stress tests (synthetic handwriting on the real sheets, `tests/hw/`), round 3 had no unflagged errors in 135 items. Real handwriting is harder; the human review is not optional.
  24. - **Anonymous by default.** Names of people and employers are removed from everything except a commitment card's optional Name and Organisation lines, which the card asks people to fill in only if they're happy to be named.
  25. - **Accessible.** The site, slides and HTML sheets are built to WCAG 2.2 AA: real headings and landmarks, labelled controls, full keyboard use, and contrast checked in light and dark mode. If your brand colours would fail contrast, the builder adjusts them and tells you.
  26. ## What you need
  27. - **Claude Code**, for reading the handwriting and writing the playbook. The readers run as sub-agents, one per table. Without it, you can type the sheets in yourself and every check and build still works: see [On the day](docs/on-the-day.md#if-claude-isnt-available).
  28. - **Python 3.9 or later** and the packages in `requirements.txt`: `pip install -r requirements.txt`.
  29. - **A Mac is easiest.** The review app's close-ups use Apple's Vision text recognition, which needs Xcode's command line tools (`xcode-select --install`), and iPhone HEIC photos convert with the built-in `sips`. On Linux or Windows, everything still works: install `pillow-heif` for HEIC photos, and the review app shows whole photos instead of close-ups.
  30. - **Optional:**
  31. - Node and Playwright, for the slides' PDF backup (`slides/README.md`).
  32. - Whisper and ffmpeg, if you record voice notes as well: `pip install openai-whisper` (or `brew install openai-whisper ffmpeg` on a Mac).
  33. - Poppler (`pdftoppm`), scipy and an internet connection the first time, for the handwriting stress tests (`tests/README.md`).
  34. New to the vocabulary (table lead, stub, run, readers)? There's a short glossary at the top of [On the day](docs/on-the-day.md).
  35. ## Quick start
  36. ```bash
  37. git clone https://github.com/Chris-Keene/sheets-to-playbook.git && cd sheets-to-playbook
  38. pip install -r requirements.txt
  39. python3 build/build.py # the example playbook and a blank template, in playbook/
  40. python3 print/build_paper.py # print-ready kit in print/out/paper/, zipped in print/out/
  41. python3 print/build_sheets_html.py # fillable HTML sheets in print/out/html/
  42. python3 slides/build_slides.py # slides/out/slides.html
  43. ```
  44. Open `playbook/index.html` to see what you'll end up with. Every build reads `playbook.config.json`; try `--config examples/can/playbook.config.json` on any of them to see a fully branded version.
  45. Then open Claude Code in this folder. The `sheets-to-playbook` skill is picked up automatically. To use it from anywhere, run `python3 tools/install_skill.py`.
  46. ## Make it yours
  47. `playbook.config.json` holds everything that isn't content:
  48. | Setting | Used for |
  49. | --- | --- |
  50. | `org.short`, `org.name` | "About CAN", sheet footers, the header wordmark when there's no logo |
  51. | `org.forum`, `org.team` | Sentences on the site: "created during the *community forum*", "*the organisers* photographed every sheet" |
  52. | `org.about`, `org.join` | The About page and the closing band (a link to join your network) |
  53. | `playbook.name`, `playbook.url` | Page titles and footers; **the QR code on the commitment card points at the url**, so set it before printing |
  54. | `playbook.searchable` | `false` (the default) keeps every page out of search results. Set `true` to let search engines list the final playbook; drafts never are. |
  55. | `playbook.file_name` | What "Download this playbook" saves as. Default: the playbook's name, e.g. `community-playbook.html`. |
  56. | `playbook.share` | Optional link previews for LinkedIn, Slack and Teams once the playbook is online: `{"image": "share.jpg", "image_alt": "..."}`. Needs `playbook.url`. The picture is copied beside the page. |
  57. | `brand.accent`, `brand.highlight` | Two colours. Every other shade, in light and dark mode, is worked out from them and checked for contrast. |
  58. | `brand.logo` | Optional SVG or PNG logos (`primary`, `secondary`, `mark`), relative to the settings file. Without one, the name is set as a wordmark. An SVG takes the page's logo colour so it follows dark mode; set `"keep_colours": true` to keep its own colours. A logo in its own colours (or a PNG) can have a second file for dark backgrounds: `secondary_dark` and so on. The print kit draws SVGs only; with a PNG it uses the wordmark. |
  59. | `brand.font` | The typeface for every page, sheet and slide: `{"family": "Outfit", "files": {"Regular": ..., "Medium": ..., "SemiBold": ..., "Bold": ...}}`. Use static woff2 (or TTF) files, not a variable font: the print kit draws its lettering from them too. Poppins by default. |
  60. | `brand.palette` | Optional exact colours, if you'd rather set every shade yourself (still contrast-checked) |
  61. | `brand.cmyk` | Optional print colours your printer has proofed, `{"accent": [c, m, y, k], "highlight": [...]}`. Otherwise the kit converts your hex colours, which is fine for an office printer but worth proofing for a print shop. |
  62. | `kit.licence` | The licence line on the playbook's "Run your own" page. The default keeps the CC BY credit the kit needs when you pass it on. |
  63. | `kit.source` | Where the tools live, linked from the "Run your own" page. `""` leaves the link out. |
  64. | `credit` | The small "Built with sheets-to-playbook by Chris Keene" line, with its logo, at the foot of every playbook. `{"show": false}` switches it off. |
  65. `examples/can/playbook.config.json` is a complete worked example (the logo files aren't included: see `examples/can/brand/README.md`).
  66. ## Privacy
  67. Photos of sheets can include names, faces in the background and the odd phone number.
  68. - The scripts run on your machine. Photos reach Claude only through Claude Code, to be read. (`verify --links` also checks that resource links on the sheets still work, which contacts those sites.)
  69. - The folders that hold event data (`runs/`, `inbox/`, `data/session.json`) are ignored by git, so they can't be committed by accident.
  70. - The published playbook stays out of search results unless you set `playbook.searchable`.
  71. - Once the playbook is final, delete the photos, voice notes and runs you agreed not to keep.
  72. ## Repository map
  73. ```
  74. .claude/skills/sheets-to-playbook/ the Claude Code skill: the whole day, stage by stage
  75. ingest/ingest.py prepare, status, verify, draft, review, publish
  76. ingest/RAW_FORMAT.md how handwriting is transcribed, and the rules for writing the playbook
  77. build/ site builder, settings and colour maths, templates
  78. print/ paper kit: PDFs and fillable HTML
  79. slides/ facilitator deck
  80. tools/review/ the review app (see its README)
  81. tools/install_skill.py install the skill for every Claude Code session
  82. docs/on-the-day.md runbook: before, straight after, and if Claude isn't available
  83. examples/ an example playbook, a blank template, and the CAN settings
  84. tests/ fixtures and handwriting stress tests (see tests/README.md)
  85. ```
  86. ## Licence
  87. - **Code:** MIT (`LICENSE`).
  88. - **Workshop kit** (sheets, cards, slides and written guidance): CC BY 4.0 (`LICENSE-CONTENT.md`). Adapt it freely; credit *sheets-to-playbook by Chris Keene*.
  89. - **Poppins** typeface: SIL Open Font License (`assets/fonts/OFL.txt`).
  90. ## Credits
  91. Designed and built by Chris Keene for the CAN Community Forum. Built with Claude Code.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.