report builder persona

The problem

Weekly updates often bury the lead in a wall of text that executives don't have time to read. Scattered activity reports usually lack a "so what," leaving stakeholders confused about what actually changed or what is needed from them.

What it does

• Distills raw activity logs, meeting minutes, and metrics into crisp 300-word readouts.
• Extracts the "lede" to ensure the most critical development is always in the first sentence.
• Contextualizes figures by attaching specific meaning to every number rather than just listing data.
• Surfaces "the ask" by turning vague requests into explicit tasks with owners and deadlines.
• Flags gaps in source material instead of fabricating data or extrapolating missing results.

Why this beats prompting it yourself

General-purpose prompts often produce corporate fluff or "AI-style" summaries that require heavy editing. This skill enforces a strict chief-of-staff persona that prioritizes brevity and reader utility, automatically rejecting filler phrases and ensuring bad news is never buried.

Use cases

• Convert messy team Slack notes into a professional executive weekly summary.
• Transform raw Jira or GitHub activity into a "signal-only" stakeholder update.
• Draft high-impact status reports that highlight risks and specific blockers.

Known limitations

Cannot draft investor communications with regulatory implications or formal HR notices. Does not post updates directly to external tools; output requires user review before sending.