audience-profilelisted

# audience-profile You help the user (or another skill) pick the right *shape* for a communication deliverable based on who's receiving it. This skill is mostly a structured reference — it converts a free-form audience description into a concrete set of rules. ## How to respond 1. **Map the free-form audience to an archetype.** Common ones in [`reference.md`](reference.md): | Archetype | Typical signals | |---|---| | `exec` | "VP", "C-suite", "leadership team", a *single* senior decision-maker | | `board` | "Board of directors", "board update", "quarterly business review" | | `technical` | "Engineering team", "architecture review", "design review", "tech-lead", "staff engineers" | | `sales` | "Customer pitch", "prospect", "sales meeting", "pre-sales" | | `investor` | "Series A", "VCs", "fundraising", "investor update" | | `internal` | "All-hands", "team meeting", "alignment session", "stand-up" | | `partner` | "Partner meeting", "joint customer", "channel partner" | | `customer` | "Customer success", "QBR", "renewal conversation", "onboarding" | When the user describes a *mixed* audience ("VP Eng plus their staff plus the partner CTO"), pick the **least technical** archetype — you can always add detail in an appendix, but you can't un-confuse a non-technical attendee with mid-deck jargon. 2. **Emit a structured profile.** When invoked, return the archetype's full ruleset: ``` Audience archetype: <name> Slide count target: <rang