icaire-secretarial-draft-speaker-notes

Draft ICAIRE speaker notes from supplied material for slides, meetings, visits, panels, or briefings. Use when the user asks for talking points or presenter notes.

SKILL.md

GitHub

ICAIRE Secretarial Draft Speaker Notes

Create clear presenter notes and talking points from supplied ICAIRE source material, keeping private delivery notes separate from slide text and public claims.

Contract

  • Start from the supplied source material, ICAIRE brain context, or both.
  • Confirm audience, setting, language, duration, desired tone, and whether the notes are for slides, an ambassador visit, a panel, a meeting, or an internal briefing.
  • Keep notes grounded in evidence. Flag missing facts instead of inventing details.
  • Separate speaker notes from slide copy, email copy, and public-facing text.
  • Treat external-facing notes as review-ready, not final-approved.
  • For government-machine workflows, prepare notes the user can transfer manually.

Workflow

  1. Define the speaking assignment.
    • Identify audience, occasion, document or deck source, target length, language, and desired level of formality.
    • Ask for missing source material if the request depends on unprovided details.
  2. Gather and ground.
    • Read supplied text, decks, PDFs, Word files, meeting notes, or relevant ICAIRE brain pages.
    • Mark confirmed facts, assumptions, and gaps.
  3. Draft notes.
    • Produce opening context, key talking points, transitions, and closing points.
    • For slide-based work, align notes to slide numbers or headings.
    • Keep bullets speakable rather than report-like.
  4. Polish and review.
    • Check tone, sensitivity, factual grounding, and flow.
    • Flag any claim that needs approval or source confirmation.

Output

Default to this structure:

  • Purpose: event or meeting, audience, and intended outcome.
  • Speaker Notes: ordered notes by slide, section, or agenda item.
  • Key Messages: short list of takeaways.
  • Optional Opening / Closing: if useful for the setting.
  • Review Flags: facts, names, sensitivities, or approvals still needed.
  • Source Basis: source files or brain pages used.

Guardrails

  • Do not invent ICAIRE achievements, commitments, partner positions, dates, or statistics.
  • Do not turn private speaker notes into public copy unless asked.
  • Do not overload notes with full paragraphs when concise talking points are more useful.
  • Do not hide uncertainty; mark unsupported claims for review.
  • Do not claim external readiness when approvals or source facts are missing.