agentleFS
CodesbyFebinCodesbyFebin/linkedin-manager/skills/linkedin-hook-lab/SKILL.md

linkedin-hook-lab

Skill0 starsChanged 39 days agoMITView on GitHub

Write five opening lines for one claim. Use when the draft is stuck on the first line. Does not write the rest of the post.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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 five hooks, each under 210 characters, each a different shape: number, object, failure, constraint, question.

    line 12
  2. Very specific:

    Do not draft the body unless asked.

    line 14

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

Hook lab

Five openings. One claim. Nothing else.

Steps

  1. Lock the claim in one sentence. Ask if it is vague.
  2. Write five hooks, each under 210 characters, each a different shape: number, object, failure, constraint, question.
  3. Score each for filler and em dashes. Drop any that fail.
  4. Do not draft the body unless asked. Hand the winner to linkedin-post-writer.

Related

  • linkedin-approval-gate
  • linkedin-humanizer
  • ../../references/voice-rules.md

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.