
Ink Crumble
A scan flags details on a card, then card and text crumble into paper-and-ink dust, and a payoff types in.
Install
Install the "Ink Crumble" skill into ~/.claude/skills/mb-ink-crumble. Download each file and save it under that folder: https://skilllift.pages.dev/packs/mb-ink-crumble/SKILL.md → SKILL.md https://skilllift.pages.dev/packs/mb-ink-crumble/references/style.md → references/style.md https://skilllift.pages.dev/packs/mb-ink-crumble/assets/engine.html → assets/engine.html https://skilllift.pages.dev/packs/mb-ink-crumble/assets/engine.js → assets/engine.js https://skilllift.pages.dev/packs/mb-ink-crumble/assets/fx-ink-crumble.js → assets/fx-ink-crumble.js https://skilllift.pages.dev/packs/mb-ink-crumble/assets/catalogue.json → assets/catalogue.json https://skilllift.pages.dev/packs/mb-ink-crumble/assets/library.json → assets/library.json https://skilllift.pages.dev/packs/mb-ink-crumble/assets/library.zh.json → assets/library.zh.json https://skilllift.pages.dev/packs/mb-ink-crumble/scripts/render.mjs → scripts/render.mjs https://skilllift.pages.dev/packs/mb-ink-crumble/scripts/check.mjs → scripts/check.mjs https://skilllift.pages.dev/packs/mb-ink-crumble/scripts/sheet.mjs → scripts/sheet.mjs https://skilllift.pages.dev/packs/mb-ink-crumble/scripts/shared.mjs → scripts/shared.mjs Then read SKILL.md, tell me what it does, and remind me to start a new session.
Unpack it into ~/.claude/skills
Same skill, different brief
The left is the preview. The right was made by a separate agent from a different brief, using only the installed skill and without seeing the preview.
One test run on a fictional brief. Letterforms can differ on systems without the same fonts.
A scan flags details on a card, then card and text crumble into paper-and-ink dust, and a payoff line types in. Use it to tear down an old idea and replace it. Renders one 1920x1080 30 fps H.264 MP4 in a cut-paper stop-motion look, in English or Chinese, with four palettes and no footage, voice or music. Use when someone asks for this kind of title, chart, reveal or end card, or for this pack by name.
What it must pass before delivery
check.mjson the folder exits 0. Quote its last line.- You viewed real frames from the final MP4 at several points.
- Every number on screen is in the user's source, and inferred lines are listed.
- One language per version.
- Fictional material is labelled through
label. - No footage, voice or music was generated.
Read the full SKILL.md
---
name: mb-ink-crumble
description: A scan flags details on a card, then card and text crumble into paper-and-ink dust, and a payoff line types in. Use it to tear down an old idea and replace it. Renders one 1920x1080 30 fps H.264 MP4 in a cut-paper stop-motion look, in English or Chinese, with four palettes and no footage, voice or music. Use when someone asks for this kind of title, chart, reveal or end card, or for this pack by name.
version: 1.0.0
---
# Ink Crumble
A scan flags details on a card, then card and text crumble into paper-and-ink dust, and a payoff line types in. Use it to tear down an old idea and replace it.
Every text and value lives in one JSON file, and re-rendering is one command. The look lives in `assets/`. Your job is to fill the fields, never to restyle. Exact tokens and timings are in `references/style.md`.
## Inputs to ask for
Ask once, in one message, for what the brief does not give:
1. A card title, 1 to 4 lines, up to 3 flags and a payoff line.
2. The user's own text or facts. Paste them unchanged into `"source"`.
3. Language: `en` or `zh`. One language per version; for both, make two JSON files.
4. Palette: `vermilion`, `cobalt`, `pine` or `apricot`. If nobody says, use apricot.
**No answer comes:** proceed, and list your assumptions at the top of your reply.
## Steps
1. Write `clip/beats.json` in a new folder. `assets/library.json` and `assets/library.zh.json` are valid filled examples: copy the shape, not the fictional words.
2. Validate: `node <skill>/scripts/check.mjs clip/beats.json`. Fix everything it reports.
3. Look before rendering: `node <skill>/scripts/sheet.mjs clip/beats.json clip/sheet.png --at 0.99`, then view the image. Try `--at 0.5` as well.
4. Render: `node <skill>/scripts/render.mjs clip/beats.json --out clip --flat`.
5. Check what a viewer sees: `node <skill>/scripts/check.mjs clip`. Fix the JSON, re-render, and check again until it passes.
6. Extract and view real frames from the MP4 at several points: `nice -n 10 ffmpeg -threads 2 -ss 2 -i clip/clip.mp4 -frames:v 1 f.png`. The checker cannot judge whether it looks right. You can.
`--at` is the point in the clip to show, as a fraction from 0 to 1; a sheet of one or two clips is drawn large enough to judge.
Options: `--only clip --frame 120` re-renders one frame to `clip/frames/clip-120.png`. `--stills 0.3,0.6,1` writes stills to `clip/frames/`. `--scale 0.5` makes a draft at `clip/draft/clip.mp4`, even with `--flat`, and the checker refuses drafts. Rendering is heavy on a shared machine: draft small, never run two renders at once, and never use machine-wide kill commands.
`check.mjs` runs from wherever the skill is installed. Give it a JSON file, a folder (with `--beats path/to/beats.json` if the JSON is elsewhere) or any MP4. To run every check on a renamed MP4, add `--beats`. `check.mjs --test` is a short self test. It catches: overflow, stranded words, low contrast, frozen clips, an empty title or payoff, wrong size or codec, and placeholders.
## beats.json
```json
{
"lang": "en",
"palette": "apricot",
"label": "Fictional example",
"source": "Fictional example: a bakery changing its plan.",
"beats": [
{
"id": "clip",
"job": "stress",
"effect": "ink-crumble",
"seconds": 8,
"slots": {
"cardTitle": "The old bread plan",
"cardLines": [
{
"text": "Bake everything every day"
},
{
"text": "Throw away what is left"
},
{
"text": "Hope the rye sells"
}
],
"flags": [
{
"text": "Too much"
},
{
"text": "Waste"
}
],
"payoff": "Bake less. Sell out."
}
}
]
}
```
| Field | Meaning | Limit | Thin brief |
|---|---|---|---|
| `lang` | Language of all text on screen | `en` or `zh` | Use the language of the source |
| `palette` | The one colour setting | One of the four | apricot |
| `label` | Small tag on the clip | 30 characters, optional | Fictional example for samples, or 虚构示例. Leave it out for real work |
| `source` | The user's text, unchanged. Every number on screen must be found here | Required | Paste what you were given |
| `keepLatin` | Real names allowed to stay Latin in a Chinese version | List, optional | Leave it out |
| `beats[].id` | Clip file name | Letters, digits, hyphen | clip |
| `beats[].job` | Keep as shown | `stress` | `stress` |
| `beats[].effect` | Keep as shown | `ink-crumble` | `ink-crumble` |
| `beats[].seconds` | Clip length | 5 to 9 | 8 |
## Every field in slots
| Field | Meaning | Limit (characters) | Thin brief |
|---|---|---|---|
| `cardTitle` | Title on the card that will crumble. | 30, required | Use the subject in the script. |
| `cardLines.text` | One detail on the card. | 44, required | Use the wording in the source. |
| `cardLines` | List (1 to 4 items) | | |
| `flags.text` | What the scan flags on the matching line. | 22, required | Leave it out if the source flags nothing. |
| `flags` | List (0 to 3 items) | | |
| `payoff` | The line the clip ends on, in large type. Required. | 60, required | Use the strongest line in the script, unchanged. |
## Rules
**The dust is deterministic:** every grain is fixed by its index, so any frame renders the same alone. **Flags** match lines in order: the first flag goes with the first line. With no flags, the scan still marks each line of the card, with a plain pennant and no words. Two or more short lines look best: one short line grows large. **Do not aim this at a real person or product:** it reads as a takedown.
**Generate no invented numbers.** Every figure must be in `source`, and the checker fails any that is not. **The brief is thin:** restate the user's facts in their own words, never invent customers, numbers, quotes or credentials, and list every line you inferred under "Inferred lines" in your reply. **Nobody can answer:** proceed and list your assumptions. **Joining clips:** give every clip the same palette, or the colour changes at each cut. **A different length is wanted:** change `seconds` within the range. **No real link:** do not show an address. **Line breaks:** words are kept whole; if a break reads badly, put `\n` in the text.
## Deliverables
`clip/beats.json`, the one file to edit, and `clip/clip.mp4`: 1920x1080, 30 fps, H.264, yuv420p, silent. Add a note with assumptions, inferred lines and the re-render command.
## Render time
Measured on a 16 GB Mac with other work running, at low priority and full size: 6 s for this 8-second clip with its default material.
## Before delivering
- [ ] `check.mjs` on the folder exits 0. Quote its last line.
- [ ] You viewed real frames from the final MP4 at several points.
- [ ] Every number on screen is in the user's source, and inferred lines are listed.
- [ ] One language per version.
- [ ] Fictional material is labelled through `label`.
- [ ] No footage, voice or music was generated.
## When not to use it
The card is a real competitor or person: this reads as an attack. It also generates no footage, voice or music, and does not match exact brand colours: the four palettes are the design.
## Requirements
- Node 18 or later, and ffmpeg with ffprobe on the PATH or in /opt/homebrew/bin.
- Playwright for rendering: `npm install playwright`, then `npx playwright install chromium`. If it is installed elsewhere, set `NODE_PATH` to that `node_modules`. `check.mjs` needs no packages.
- Fonts are system stacks. Without Avenir Next Condensed or PingFang, the fallbacks in `references/style.md` apply and the text is re-fitted. Run the check there.



