icaire-comms-lead-draft-announcement

Draft official ICAIRE announcements for launches, visits, partnerships, events, reports, and publications. Use when the user asks for a formal announcement, short web version, email version, quote pla

SKILL.md

GitHub

ICAIRE Comms Lead: Draft Announcement

Draft formal announcements that communicate ICAIRE launches, visits, partnerships, events, reports, and publications with accurate institutional language.

Contract

  • Start from the announcement type, audience, release timing, and approval status.
  • Use BigBrain or the ICAIRE MCP connector for ICAIRE facts, people, initiatives, partner context, meeting history, and sensitivities when the user has not supplied enough source material.
  • Provide versions suitable for the requested channels, such as formal announcement, short web version, and email version.
  • For announcement graphics, web cards, email headers, or other visual treatments, use ICAIRE's primary brand color #4A9549 as the main accent unless an approved campaign design system overrides it.
  • Use quote placeholders when quotes are needed but not approved.
  • Mark all facts, names, titles, quotes, partner mentions, and approvals that need confirmation.

Workflow

  1. Define the announcement.
    • Identify what is being announced, who is involved, why it matters, target audience, release date, channels, and required approvals.
    • If timing or approval status is unclear, proceed with placeholders and a review checklist.
  2. Gather source material.
    • Read provided notes, event plans, partnership details, report summaries, bios, website drafts, and prior announcements.
    • Query BigBrain or ICAIRE MCP for current context when claims, names, roles, initiatives, or partner relationships are unclear.
  3. Frame the announcement.
    • Lead with the confirmed news.
    • Explain relevance, context, next steps, and institutional value without overstating commitments or outcomes.
  4. Draft versions.
    • Produce the formal version first, then shorter web or email variants when useful.
    • Include quote placeholders with speaker, topic, and approval status.
  5. Review for release.
    • Check institutional tone, stakeholder sensitivity, factual support, and approval needs.

Output

Default to this structure unless the user requested another format:

  • Formal Announcement: publishable long-form draft.
  • Short Web Version: concise website or news listing version.
  • Email Version: optional internal or partner email text.
  • Quote Placeholders: speaker, intended message, and approval status.
  • Approval Note: facts, names, titles, quotes, partner mentions, and timing to confirm.
  • Source Limits: assumptions or missing material.

Guardrails

  • Do not invent approvals, quotes, commitments, partner positions, or launch dates.
  • Do not imply an agreement, endorsement, or official position that the source material does not support.
  • Do not publish internal uncertainty in external-facing copy.
  • Do not use celebratory language that outruns the facts.
  • Do not claim release readiness while quote, partner, or legal approvals are pending.