--- name: contextual-insights-cta description: "Writing employee ยท Write CTAs that continue the conversation instead of interrupting it. Three-element structure (concept link, curiosity bridge, soft CTA) that makes the offer feel inevitable, plus the 7-Element Close checklist (Bridge, Value Stack, Price Reveal, Risk Reversal, Objection Handling, Urgency, Decisive Action) for full paid-offer closes. USE WHEN user says 'write CTA', 'improve this CTA', 'CTA feels generic', 'make the CTA better', 'contextual CTA', 'the offer feels plugged in', 'write the close', 'check the close', 'closing section', '7 elements of a close'." user-invocable: false --- # contextual-insights-cta โ€” MCP loader Load the licensed instructions before doing this job: `get_skill(skill_id="contextual-insights-cta", 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.