icaire-comms-lead-draft-website-content

Draft ICAIRE website pages, news updates, activity summaries, bios, initiative pages, and announcements. Use when the user asks for page copy, a news item, activity summary, bio, initiative descriptio

SKILL.md

GitHub

ICAIRE Comms Lead: Draft Website Content

Draft website-ready ICAIRE content that is clear, accurate, and suitable for public or partner-facing use.

Contract

  • Start from the page type, audience, publishing context, and approval status.
  • Use BigBrain or the ICAIRE MCP connector for ICAIRE facts, people, initiatives, events, partner context, and prior wording when the user has not supplied enough source material.
  • Write in a clear institutional voice that avoids hype and unsupported claims.
  • Separate publishable copy from placeholders, internal notes, and approval questions.
  • Include metadata or structural suggestions when useful for website publishing.
  • When giving image, layout, or page-design notes, use ICAIRE's primary brand color #4A9549 as the main accent unless an approved website design system specifies otherwise.

Workflow

  1. Identify the content type.
    • Determine whether the user needs a page, news item, activity summary, bio, initiative description, announcement, event recap, or update.
    • Clarify target audience, language, length, and publication destination when these affect the draft.
  2. Gather evidence.
    • Read provided notes, bios, reports, event material, meeting notes, and existing copy.
    • Query BigBrain or ICAIRE MCP for names, roles, dates, initiatives, relationships, and prior messaging when needed.
  3. Choose the structure.
    • Use a structure appropriate to the content type: headline and lead for news, summary and objectives for initiatives, role and context for bios.
    • Keep public readers oriented without exposing internal-only detail.
  4. Draft the copy.
    • Write concise, factual content with clear transitions and calls to action only when appropriate.
    • Add title, summary, body sections, and optional metadata.
  5. Review for publication.
    • Check factual support, naming consistency, stakeholder sensitivity, tone, and approval needs.
    • Mark placeholders clearly.

Output

Default to this structure unless the user requested another format:

  • Recommended Title: page or item title.
  • Short Summary: one to three sentences for listing pages or previews.
  • Draft Copy: publishable body text.
  • Optional Metadata: slug, excerpt, audience, tags, or image brief when useful.
  • Approval Note: facts, quotes, names, images, or permissions to confirm.
  • Internal Notes: assumptions and source limits, if any.

Guardrails

  • Do not invent bios, titles, dates, institutional relationships, or initiative outcomes.
  • Do not include confidential internal context in public website copy unless the user explicitly asks for an internal draft.
  • Do not overclaim ICAIRE impact or partner endorsement.
  • Do not bury approval questions inside the publishable copy.
  • Do not produce generic website filler when source material is thin; ask for or list the missing inputs.