---
name: invitation-lens
description: Writing employee · The selling philosophy beneath every CTA, offer, and promotional line — invite, don't push; recognition, not manipulation — plus the premium framing shifts (reserve not "lock in", included resource not "bonus"). USE WHEN user says 'apply invitation lens', 'make this less salesy', 'this feels pushy', 'soften the sell', 'invitation framing', 'invite don't sell', 'less aggressive CTA', 'sounds too salesy', or when any selling/persuasion copy needs its relationship-to-the-reader checked. Do NOT use to WRITE a CTA from scratch (→ contextual-insights-cta) or a hook (→ write-hook) — this is the LENS those skills apply.
user-invocable: false
---

# invitation-lens — MCP loader

Load the licensed instructions before doing this job:

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