lollylisted
Install: claude install-skill ravan/scriptorium
# Lolly
Lolly (https://lolly.tools) is a hosted, template-driven asset generator. Every tool is a URL: the same inputs give the same output, and brand rules (fonts, colours, layout) are enforced by the template, not by you. **Never substitute another generator** (qrencode, matplotlib, hand-drawn QR/chart SVG) for an asset a Lolly tool produces - a substitute is off-brand, carries no editable link, and cannot be reproduced from its inputs.
There is **no local install and no MCP**. Everything runs through `scripts/lolly.ts` (bun, zero npm dependencies) over two tiers:
1. **GET tier** - `https://lolly.art/tool/<id>.<ext>?<inputs>` serves bytes instantly for community tools in browser-free formats (svg/png for SVG-native tools, `emf`/`eps`/`eps-cmyk`/`dxf`, `html`/`md`/`txt`/`json`/`csv`/`ics`/`vcf`).
2. **Browser tier** - for everything else (script-drawn SVG like `d3` charts, brand-pack tools like `quotes` and `org-chart`, pdf, raster, pptx, video), the script launches **local headless Chrome**, opens the public web shell at `#/tool/<id>?...&format=<fmt>&export`, and captures the file the app's own export path downloads. Same bytes a human's Download button produces, ~8s, still one call. Chrome is found automatically (`LOLLY_CHROME` overrides); the wiki's PDF pipeline already requires it.
The share link is only a last resort when no Chrome exists on the machine. A 404 from `lolly.tools/tool/<id>.svg` never means "no API" - that GET route is off there by policy and live on `