Free

Post Scan

A plain post mock-up is scanned line by line, key phrases get marked, and it ends on a summary.

Install

Install the "Post Scan" skill into ~/.claude/skills/mb-post-scan.
Download each file and save it under that folder:
https://skilllift.pages.dev/packs/mb-post-scan/SKILL.md → SKILL.md
https://skilllift.pages.dev/packs/mb-post-scan/references/style.md → references/style.md
https://skilllift.pages.dev/packs/mb-post-scan/assets/engine.html → assets/engine.html
https://skilllift.pages.dev/packs/mb-post-scan/assets/engine.js → assets/engine.js
https://skilllift.pages.dev/packs/mb-post-scan/assets/fx-post-scan.js → assets/fx-post-scan.js
https://skilllift.pages.dev/packs/mb-post-scan/assets/catalogue.json → assets/catalogue.json
https://skilllift.pages.dev/packs/mb-post-scan/assets/library.json → assets/library.json
https://skilllift.pages.dev/packs/mb-post-scan/assets/library.zh.json → assets/library.zh.json
https://skilllift.pages.dev/packs/mb-post-scan/scripts/render.mjs → scripts/render.mjs
https://skilllift.pages.dev/packs/mb-post-scan/scripts/check.mjs → scripts/check.mjs
https://skilllift.pages.dev/packs/mb-post-scan/scripts/sheet.mjs → scripts/sheet.mjs
https://skilllift.pages.dev/packs/mb-post-scan/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.

The preview
The preview
A new brief, made by a separate agent
A new brief, made by a separate agent

One test run on a fictional brief. Letterforms can differ on systems without the same fonts.

A plain original post mock-up is scanned line by line, key phrases get marked, and the clip ends on a summary line. Use it to pick apart a piece of writing. 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.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.
Read the full SKILL.md
---
name: mb-post-scan
description: A plain original post mock-up is scanned line by line, key phrases get marked, and the clip ends on a summary line. Use it to pick apart a piece of writing. 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
---

# Post Scan

A plain original post mock-up is scanned line by line, key phrases get marked, and the clip ends on a summary line. Use it to pick apart a piece of writing.

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. 2 to 6 lines of text, the phrase to mark in each, an optional author and a summary 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 pine.

**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: marks not in their line, a plate touching other words, overflow, frozen clips, an empty summary, wrong size or codec, and placeholders.

## beats.json

```json
{
 "lang": "en",
 "palette": "pine",
 "label": "Fictional example",
 "source": "Fictional example: a post by a baker.",
 "beats": [
  {
   "id": "clip",
   "job": "quote",
   "effect": "post-scan",
   "seconds": 8,
   "slots": {
    "author": "Ana, a fictional baker",
    "lines": [
     {
      "text": "We stopped baking everything every day.",
      "mark": "stopped baking"
     },
     {
      "text": "Now the rye comes out twice a week.",
      "mark": "twice a week"
     },
     {
      "text": "People plan around it."
     }
    ],
    "summary": "Fewer loaves, and fewer left over."
   }
  }
 ]
}
```

| 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 | pine |
| `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 | `quote` | `quote` |
| `beats[].effect` | Keep as shown | `post-scan` | `post-scan` |
| `beats[].seconds` | Clip length | 5 to 9 | 8 |

## Every field in slots

| Field | Meaning | Limit (characters) | Thin brief |
|---|---|---|---|
| `author` | Name on the post. Keep it fictional or supplied. | 24, optional | Leave it out: a blank bar stands in. Never use a real account that did not write this. |
| `lines.text` | One line of the post, as supplied. | 60, required | Use the wording in the source. |
| `lines.mark` | The key phrase to mark. It must appear exactly in that line. | 30, optional | Leave it out if the source stresses nothing there. |
| `lines` | List (2 to 6 items) | | |
| `summary` | The line the clip ends on. Required. | 70, required | Restate the point of the source, and list it as inferred. |

## Rules

**The mock-up is neutral:** no logos, no counts, no resemblance to a real network, and it must not be restyled to look like one. **Do not present invented words as a real post.** Label it fictional, or use real supplied text with permission. **mark** must appear exactly in its line, or the check fails.

**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

You need to prove a real post exists: use a real screenshot. 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.

Similar skills