write-hook
Social media hooks
A hook is the headline of a social post, and it deserves as much care as the post. It has one job: make the right reader stop scrolling and want the rest. It does that by promising, as specifically as it can, what the post delivers, and by opening a curiosity gap: enough to make the reader curious, not enough to satisfy them. It fails in two directions. A vague hook could sit on top of any post ("Some thoughts on file search"). A hyped hook promises more than the post delivers ("You won't believe what fd does"), and readers learn to distrust everything after it.
The author's original prompt is in references/hook-prompt.md. The writing principles behind this workflow, from Ann Handley's Everybody Writes, are in references/everybody-writes.md; read it when a group isn't working and you need more than the summary here.
Usage
/write:hook [file | URL | pasted text]
Text after a --- line in the user's message is the source. A file path or URL is read. With nothing given, use the article you created or edited most recently in this conversation, else run ${CLAUDE_SKILL_DIR}/../write-review/scripts/last-article.sh (it prints the newest changed jeffbaileyblog article). Don't stop to confirm the pick; name it and how you found it on the Source line so the user can redirect you. If the script is missing (write-review not installed), ask which article to use.
The checker in step 7 compares the hooks against the source, so it needs the source as a file: use the article path, or save pasted text or a fetched URL to a scratch file.