lock-in
Skill23 starsChanged 18 days agoMITView on GitHub
Writes the 1 to 3 sentences straight after the hook so they pay it off and turn attention into trust, and finds the dead stretch that loses people after a good hook. Use when a hook stops the scroll but viewers still leave in the next few seconds.
In this repository8 other files it gives its agents.
- four-failures-checkSkill
- hook-formatsSkill
- hook-masterSkill
- niche-tunerSkill
- the-councilSkill
- viewer-panelSkill
- viral-scoutSkill
- visual-matchSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Write what the hook promised, then what actually comes next in the video, with the time.
- Distinctive: line 29
Write the exact 1 to 3 sentences, and what's on screen while they're said.
- Distinctive: line 49
No invented proof to make the lock-in land.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Lock-in
The hook makes a promise. The next 1 to 3 sentences decide whether the viewer believes it. If they get a detour, a backstory or a slow setup, the curiosity turns into "this was bait" and they leave.
Step 1: Find the gap
Write what the hook promised, then what actually comes next in the video, with the time. Flag any stretch that doesn't serve the promise: an intro, a story about the creator, "before we start", a long setup. Say exactly what to cut or move.
Step 2: Pick one lock-in move
| Move | When | Example shape |
| Proof right away | The hook made a claim | Show the result, the number (theirs), the screen |
| Picture the result | The viewer wants a change | "By the end you'll [see / have] [result]" said over the result |
| Stack a second contrast | The hook landed and needs more pull | "And it's not your shoes either." |
| Name the method | The fix has steps | "It's one change: [named thing]." |
| Answer the objection | The viewer is already doubting | "No, you don't need [the thing they think they need]." |
| Say it concretely | The hook was a bold or abstract claim | Restate it with the real number or the real example |
Usually one or two moves is enough. Pick by what this viewer is thinking right after the hook.
Step 3: Write it
Write the exact 1 to 3 sentences, and what's on screen while they're said. Then check:
- Does it confirm the hook within the first sentence or two?
- Does it add something, not repeat the hook?
- Is the claim backed by footage or the creator's own facts?
- Does it set up the rest of the video, so the viewer knows why to keep watching?
Output
Hook promised: [one line]
Video currently does next: [what, until when]
Cut or move: [exact]
Lock-in (say): "[1 to 3 sentences]"
On screen: [shot]
Move used: [name]Rules
- The creator's story is allowed, after the payoff, as proof. Not before.
- No invented proof to make the lock-in land. Use what's in the video, or a [placeholder].
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.