Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    Stakeholder Brief

    1

    Convert messy data dumps into high-signal, one-page stakeholder briefs with one ask and one risk.

    $10

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned
    Stakeholder Brief

    Stakeholder Brief

    Example session with this skill installed

    Brief the CTO using the dump in notes.txt. Target audience is CTO, as_of 2023-10-27. Project path is ./internal/migration. The ask is to approve the database schema freeze.

    • Read your context and instructions
    • Compiled the stakeholder brief
    • Generated the document

    I have processed the source data from notes.txt and generated the stakeholder brief. The draft identifies the single ask regarding the schema freeze and highlights the risk to the migration timeline if delayed. No data was invented, and house-specific chat IDs were stripped.

    Stakeholder Brief

    • Audience: CTO
    • From Role: Technical Lead
    • As Of: 2023-10-27
    • By When: 2023-11-01
    • Status: ready
    • Write Mode: draft

    What changed

    • API response times increased by 40% after the v2 migration (Source: notes.txt, line 12)
    • New indexing strategy validated in staging environment (Source: notes.txt, line 18)
    • Legacy database support deprecated since 2023-10-20 (Source: buyer paste)

    Ask

    Approve the database schema freeze to prevent further migration drift. (Source: buyer line)

    Risk

    If the audience does not approve the schema freeze, the v2 migration will exceed the Q4 infrastructure budget. (Source: derived)

    By when

    2023-11-01 (Source: notes.txt, line 4)

    Diff

    (none)

    Gaps

    • sister skill refused: Stripped weekly commitments and capacity table found in notes.txt.
    • house path stripped: Local vault directory removed from header.

    Residual

    • Mutated: no
    • Invented: no

    Next steps

    1. Review the generated brief in ./internal/migration/docs/stakeholder-brief.md.
    2. To publish this to the internal wiki, re-run with write_mode=apply.
    3. If the risk needs to be more specific, provide the harm details and I will update the draft.

    stakeholder-brief.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Draft a single-audience brief from a messy project dump.Extract a verb-based ask from informal meeting notes.Identify operational risks associated with a specific project change.Generate standardized Markdown briefs for stakeholder approval.

    About this skill

    The problem

    Stakeholders are often buried under status novels and multi-page reports that obscure the actual request. Developers and PMs waste time formatting weekly updates when they only need to signal a critical change or secure a specific approval.

    What it does

    • Extracts a single, verb-based ask from messy meeting notes or data dumps.
    • Distills complex project updates into exactly one page for one specific audience.
    • Identifies operational risks and hard deadlines with strict source citations.
    • Enforces a rigid format including change bullets, risks, and ISO-dated dues.
    • Flags contradictions or missing data as blocking issues rather than inventing placeholders.

    Frameworks & tools

    This skill is framework-agnostic. It operates on any environment capable of reading and writing Markdown files, such as Claude Code, Cursor, or local file systems.

    Why this beats prompting it yourself

    Generic prompts often hallucinate dates, soften asks into "FYIs," or include irrelevant status padding like capacity hours and stalled tasks. This skill uses a strict procedure to strip "house" formatting, reject sister-skill artifacts like SOPs or weekly reviews, and ensure no data is invented or leaked from memory.

    Use cases

    • Briefing an owner on a critical architectural shift and the required approval.
    • Summarizing a project risk for a lead after a disruptive technical discovery.
    • Creating a one-pager for a specific stakeholder that requires a single decision by a fixed date.

    Known limitations

    Does not support multi-audience recaps or multiple asks per brief. It requires ISO dates and will not resolve relative terms like EOD or ASAP without a source.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 1 day ago

    • Passed all security checks, Safe to install

    Listed1 day ago

    Frequently Asked Questions