Papercut Hook

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites: none for the install itself: no account, no API key, no paid service, and nothing else to install first. This skill is text only — SKILL.md plus one reference file, no code, no scripts, no library. SKILL.md itself says "Minimal is enough. No library needed." For using it afterwards, I provide the project inputs myself in my own project folder: the BRIEF and facts list at the top of episodes/NN-slug/research/facts.md and the SERIES.md file for the audience level and regions (both are files from my own series/episode project, not files from this repository). If there is no BRIEF, SKILL.md says to run the sibling skill papercut-strategy first — that sibling is NOT part of this listing and is NOT installed by this install (see point 2). Install "papercut-hook" for me. It writes or fixes the hook of a papercut reel — a short vertical explainer that looks like layered construction paper. Before anything else in the script, it writes all three hook layers in one HOOK block (SAY: the first spoken sentence, opening a gap within about 10 words, naming who it is for and the stake or number early, never answering itself; WRITE: the frame-0 cover title, 2-5 words, ideally a number, fully visible on frame 0 for about 2-3 seconds and never the same words as the voice; SHOW: what frame 0 and the first 2 seconds show, the most striking moment already mid-action, readable muted; ALIGN: the one idea all three point at), passes the alignment test (cover any two layers, the remaining one still hints at the same idea), writes 5 variants from at least three of the seven patterns in references/hook-patterns.md, scores each variant with the 6-question hook check (one point per yes, and any variant failing question 6 — every claim true to the facts sheet — is dropped), picks the best-scoring variant, specifies the frame-0 title as the "hook" key for episode.json, and plans the motion out of the hook (an accelerating push in the hook scene's last ~10 frames, scene 2 opening on an impact, the title lifting away on the cut). Repository: https://github.com/0xS4N4TG/papercut-explainer (the skill is the whole skills/papercut-hook/ folder at the pinned commit: SKILL.md plus its references/ folder, 2 files) Pinned version: install the code at commit ff8223abc8136cc09e8d7e9b62ecb5d080c389e1 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/0xS4N4TG/papercut-explainer into a temporary folder, check out commit ff8223abc8136cc09e8d7e9b62ecb5d080c389e1, and copy the skills/papercut-hook/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-19: [FINGERPRINTS] - SKILL.md: SHA-256 3881124cf73a9cb07801238ab573e55ce88433f5f15bace73b8d085417e57909 - references/hook-patterns.md: SHA-256 644a1b4c15f604ef4136a597e9edeb5f0be82c68cf52079b677c2ee1c298d340 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full and read references/hook-patterns.md in full, and tell me in plain words: what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 2 files only, both plain text: SKILL.md (4,975 bytes) and references/hook-patterns.md (4,063 bytes). There is no code, no script, no import, no API call and no URL anywhere in the folder. The one internal reference, references/hook-patterns.md (the seven hook patterns used to write the 5 variants), sits inside the folder, next to SKILL.md. - Dependencies outside the folder, disclosed here: the skill's writing workflow itself needs no file from elsewhere in the repository — not the library/, not the other eight skills, not the README, not install.sh — and SKILL.md says so ("Minimal is enough. No library needed."). What it does read and write at use time are files in my own episode project, not repository files: it reads the BRIEF and facts list in episodes/NN-slug/research/facts.md and SERIES.md, and it writes the HOOK block at the top of episodes/NN-slug/papercut/STORYBOARD.md (creating that file if it is not there). Two neighbouring stages are named, and neither is installed by this install: if there is no BRIEF, SKILL.md says to run the sibling skill papercut-strategy first; and its hand-off says the next stage is the sibling skill papercut-script, which puts SAY into line l1_hook of narration/script.json. SKILL.md also documents the "hook" key format for episode.json (lines as torn tags, hot words, until/hold, size, top) and notes that a downstream library tool, build_vo.py (in the repository's library/tools/, outside this folder, not installed here and never run by this skill), later writes that key into plan.json. Do not fetch, install or run any of those outside items during this install. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. No script is run during installation, no key is asked for, and there is no telemetry in the folder. - What leaves this machine at use time, disclosed here before it ever happens: nothing. Using this skill sends nothing to any service: there is no network call, no API, no account and no key anywhere in its two files. Its work stays between you and me on this machine: it reads the two local project inputs above (my facts sheet and SERIES.md) and writes one local output (the HOOK block in STORYBOARD.md, plus the episode.json "hook" key shape it specifies for a later stage). Using the skill is a separate step that only starts when I ask for a hook. If a later, separate stage (for example papercut-script or papercut-build, which are not this skill and are not installed here) ever does its own research, fetching or rendering, that is that stage's own disclosed behaviour, not this skill's. - The truth rule from SKILL.md and references/hook-patterns.md: every claim in the hook must be true to the facts sheet — score question 6 drops any variant that fails it, the identity of a named source must be credible and named (never anonymous framing like "Someone just released..."), a price-shock line is only used when it is true for the viewer's real setup, and an own-authority line ("I tested...") is only said if it is true. Do not invent numbers, sources or results when using it. - Do not install anything else during this install, do not run papercut-strategy, papercut-script or build_vo.py, do not create an episode project, and do not write any hook: using the skill is my decision, later, when I actually ask for one. 3. When I say "yes, install", install it as a skill: copy the whole papercut-hook folder into the agent's skills directory, in a folder named "papercut-hook", keeping all 2 files (SKILL.md at its root and references/hook-patterns.md in its references/ subfolder). A manual clone followed by copying the skills/papercut-hook folder into ~/.claude/skills/ is the route described here; any other route is fine only as long as every installed file matches its fingerprint. 4. Verify with no network calls: frontmatter valid (name: papercut-hook), all 2 files in place with matching fingerprints. Do not run any script to verify — there is none in this folder. 5. Report what was installed, where, and what I still need to do myself (for example: provide, in my own project folder, the BRIEF and facts list in episodes/NN-slug/research/facts.md and a SERIES.md, or obtain the sibling papercut-strategy skill separately if I want it to run when a BRIEF is missing; expect the output as a HOOK block at the top of episodes/NN-slug/papercut/STORYBOARD.md; using the skill is a separate step that only starts when I ask for it, and no use-time sends happen then either, as disclosed above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.