---
name: product-bullet-points
description: "Writing employee · Turn verified product features, deliverables, curriculum, course modules, or bonuses into specific outcome-focused sales bullets. USE WHEN user says 'write product bullets', 'write bullet points', 'product benefits', 'create sales bullets', 'turn these features into benefits', 'verified course modules', 'outcome-focused sales bullets', 'what you get bullets', 'landing page bullets', 'lead magnet benefits', or 'workshop outcome bullets'. Do NOT use for a full campaign or offer document -> copywriter; full website pages -> `copywriting` if available, otherwise return a verified page-copy handoff brief; headline-only work -> `headline` if available, otherwise return evidence-bound headline directions; offer strategy or diagnosis -> offer-clarity."
user-invocable: false
---

# product-bullet-points — MCP loader

Load the licensed instructions before doing this job:

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