---
name: write-hook
description: Writing employee · Write non-YouTube hooks and short-form CTA openings. One gated procedure (the PSF Hook Scaffold) voiced through five accents — 5-Beat Claim, Empathy, Framework, Story, PADAI Offer — as either the opening of a longer piece OR a complete short-form CTA piece. USE WHEN user says 'write a hook', 'write the opening', 'hook for this', '5-beat hook', 'carousel hook', 'proof slide', 'evidence structure', 'opening for this piece', 'slide 2', 'grab attention', 'short-form CTA', 'PADAI', 'VSL opener', 'offer email opener', 'sales email opener', 'one-day open', 'launch email opener'. Do NOT use for a long-form YouTube opening, title, or thumbnail; a full announcement post; building a carousel; reel ideation or a full reel; a full sales email/sequence or sales page; or full argument structure. Route those jobs to their installed owners — `youtube-strategy`, `write`, `carousel`, `reel-creator`, `copywriter`, or `writing-logic` — when available; otherwise return a production-ready handoff brief.
---

# write-hook — MCP loader

Load the licensed instructions before doing this job:

`get_skill(skill_id="write-hook", path="SKILL.md", section="contents")`

The tool prefix varies by host. Search available and lazy-loaded tools for any name ending in `get_skill`. If none exists, run the local `check-setup` skill and follow its repair. Do not improvise install commands or versions, and never ask for a license key in chat.

Follow the returned routing map. Fetch only the section this run needs, then fetch each workflow, reference, template, example, or script it names with the same `skill_id` and exact remote path. Those files live on the AIEB server, not local disk. If a fetched instruction says to run a script, fetch it first and follow its safety instructions.

If the server returns a 🔒, entitlement, or setup message, relay its explanation and next action once. Do not retry a locked call, reconstruct paid content, or claim setup is fixed before a live fetch succeeds.