--- name: copywriter description: "Writing employee ยท Campaign and offer copywriting orchestrator. Builds campaign strategy, message foundations, offer documents, email-linked offer letters, VSL-topped mini landing pages, campaign email sequences, welcome emails, VSLs, paid live webinar/workshop pages, and Game Worth Playing documents. USE WHEN the user says 'sales campaign', 'offer document', 'send the offer by email', 'mini landing page', 'VSL at the top', 'promotion package', 'campaign email sequence', 'welcome email', 'write a welcome email', 'video sales letter', 'turn my offer into a video sales letter', 'webinar sales page', 'workshop page', or 'Game Worth Playing'. Do NOT use for product or sales bullets (product-bullet-points), offer diagnosis (offer-clarity), objection analogies (agreement-analogy), daily/editorial email (write), lifecycle sequences (email-os), generic website copy (copywriting), page diagnosis (cro), headline-only work (headline), or external deployment without separate approval." --- # copywriter โ€” MCP loader Load the licensed instructions before doing this job: `get_skill(skill_id="copywriter", 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.