icaire-events-lead-draft-invite

Draft ICAIRE event invites, speaker invitations, ambassador visit invitations, and workshop invitations. Use when producing formal invites, shorter email versions, RSVP details, value propositions, or

SKILL.md

GitHub

ICAIRE Events Lead: Draft Invite

Use this skill to draft invitations for ICAIRE events, workshops, speaker engagements, ambassador visits, and partner sessions.

Contract

  • Start from the invitee, event purpose, host, date or timing, format, and desired response.
  • Use BigBrain or the ICAIRE MCP connector for ICAIRE context, event history, relevant initiatives, partner relationships, attendee context, and approved framing when source material is incomplete.
  • Produce invitation copy that is ready to review, with placeholders for missing logistics instead of invented details.
  • Match tone to the invitation type: formal diplomatic invite, partner email, speaker request, workshop invite, or internal stakeholder invitation.
  • Make the value proposition clear for the invitee and include RSVP mechanics.

Workflow

  1. Identify the invitation type, invitee, sender, host organization, event title, audience, timing, venue or platform, and response deadline.
  2. Gather provided context and retrieve ICAIRE context if the event purpose, relationship, approved wording, or partner relevance is unclear.
  3. Clarify the value proposition: why the invitee matters, why the event matters, and what participation would contribute.
  4. Draft a formal invitation with purpose, invitation ask, event details, value proposition, RSVP instructions, and logistics placeholders.
  5. Draft a shorter email version when useful.
  6. Add optional speaker or ambassador-specific details such as proposed role, session topic, protocol notes, and briefing availability.
  7. Check that dates, locations, titles, names, and participation asks are supported by source material or clearly marked as placeholders.

Guardrails

  • Do not invent event dates, venues, RSVP contacts, speaker roles, protocol status, or institutional commitments.
  • Do not use overly casual wording for formal ambassador, ministry, UNESCO, SDAIA, or senior partner invitations.
  • Do not overpromise audience size, publicity, funding, travel support, or partnership outcomes.
  • Do not include internal planning uncertainty in external invite copy unless it is intentionally represented as a placeholder for review.
  • Do not hardcode ICAIRE event facts into the skill; retrieve current context when the skill is used.

Output Expectations

Return invitation copy in the requested format. When useful, include:

  • formal invitation
  • shorter email version
  • subject line options
  • RSVP details
  • value proposition
  • logistics placeholders
  • proposed speaker or guest role
  • optional follow-up note
  • assumptions and missing information