---
name: headline
description: "Writing employee · Generate and review email subject lines, carousel covers, landing-page heroes, offer names, and landing-page section headers from validated direct-response shapes using demand matching. USE WHEN user says 'write a headline', 'subject line', 'email subject', 'carousel cover', 'LP hero', 'section header', 'sales-page headers', 'make this headline better', 'does this convert', 'name this offer', or 'fascination', and whenever another writing skill needs a headline. Landing-page section headers always route here. Do NOT use for body openings → `write-hook`; full argument structure → `writing-logic`; claim tightening → `precision-principle`; perspective discovery → `perspective-shift`; or the full email/carousel → `write` or `carousel`."
---

# headline — MCP loader

Load the licensed instructions before doing this job:

`get_skill(skill_id="headline", 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.