agentleFS
m-binimranm-binimran/creator-pack/skills/hook-writer/SKILL.md

hook-writer

Skill3 starsChanged 5 months agoMITView on GitHub

Write scroll-stopping hooks - the first line / first 3 seconds - for Reels, carousels, and posts. Use when a piece needs a stronger opening or you want hook options to test.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write 5-10 hooks for the idea, across angles.

    line 20
  2. Very specific:

    No fabricated numbers in a hook (truth-telling).

    line 28

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

hook-writer

The hook is 80% of the result. Give options worth testing.

Hook angles (mix and match)

  • Bold claim (you can back): "You're [doing X] wrong."
  • Curiosity gap: "The reason your [thing] isn't working isn't what you think."
  • Direct payoff: "3 ways to [result] without [pain]."
  • Pattern interrupt / contrarian: "Stop [common advice]."
  • Callout to the viewer: "If you [audience trait], watch this."
  • Story open loop: "I almost quit - until this."
  • Number/specific: specifics beat vague ("$0 to 10k saves in 30 days").

Process

  • Write 5-10 hooks for the idea, across angles. Keep them short, concrete, and in the creator's voice. Pair the spoken hook with an on-screen text version (sound-off).

Output

  • A ranked list of hooks (spoken + on-screen text), with a one-line note on why each could work.

Guardrails

  • The hook must match what the content delivers - no bait-and-switch (brand-safety).
  • No fabricated numbers in a hook (truth-telling). Keep it human, not clickbait-y AI.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.