agentleFS
styfinitystyfinity/linkedin-engine/skills/linkedin-hook-lab/SKILL.md

linkedin-hook-lab

Skill9 starsChanged 4 months agoMITView on GitHub

Generate ten scored hook variants for one topic, one per formula, and recommend the strongest two. Use when you have a post topic and need the opening line that stops the scroll.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Distinctive:

    Write one hook for EACH of the ten formulas, in this order:

    line 16
  2. Distinctive:

    Keep each hook under 235 characters so it survives the "see more" cut.

    line 27
  3. Distinctive:

    No clickbait. If the hook over-promises, score it down and say so.

    line 36
  4. Distinctive:

    No em-dashes. Draft only - the operator picks the winner and writes the post.

    line 38

≈ “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.

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

LinkedIn Hook Lab

The hook decides whether the post gets read. This skill writes ten openers across ten proven formulas, scores them, and hands you the two best.

Inputs

  • The topic and the audience it is for: $ARGUMENTS
  • The brief (persona tone, pains, offer, voice profile) loads automatically.

Do this

  1. Write one hook for EACH of the ten formulas, in this order:
    • Pattern-Break (says the unexpected thing first)
    • Counter-Intuitive Insight (the truth most people get backwards)
    • Experience-Led Observation (what you noticed doing the work)
    • Direct Consequence (the cost of ignoring this)
    • Confession + Result (an admission plus what it produced)
    • Numbered Promise (a specific count of takeaways)
    • Enemy-Hero-Gasoline-Teaser (name the villain, the win, the open loop)
    • BREAKING / News (frame it as fresh signal)
    • Stat-Anchored (X% vs Y%, a real or clearly-illustrative contrast)
    • Mechanism-Reveal (the "here is how it actually works" angle)
  2. Keep each hook under 235 characters so it survives the "see more" cut. Count them.
  3. Score each hook 1-10 on the four value levers (dream outcome, perceived likelihood, time-to-result, effort-and-sacrifice) plus scroll-stop power.
  4. Pick the top two. Say in one line why each beats the rest.

Output

A table of the ten hooks: formula, hook text, character count, score. Then the recommended two, each with a one-line reason. End with a note: pass the chosen hook to the post draft, then run /linkedin-humanizer on the result.

Rules

  • Counter-intuitive and BREAKING hooks must still be true and defensible. No claim the body cannot pay off.
  • No clickbait. If the hook over-promises, score it down and say so.
  • Real numbers only with honest attribution: "a post that did 12,000 impressions", never a named person or company.
  • No em-dashes. Draft only - the operator picks the winner and writes the post.

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.