Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 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

    Money-back guarantee

    Converts to your local currency at checkout

    Security 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

    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.

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

    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.

    Strictly one audience and one ask per brief. No support for relative dates like "ASAP". Requires a source dump; cannot crawl personal vaults or chat history.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    Permissions

    Read Files
    Write Files
    Listed2 months ago

    What's inside

    Frequently Asked Questions

    Unlike general-purpose assistants that often generate 'fluff' or status novels, this skill uses a strict logic gate to filter out everything except one specific request and one primary risk, ensuring your stakeholders actually read and act on the document.

    The skill is designed for any Markdown-compatible environment, including developer-focused tools like Claude Code and Cursor, as well as local IDEs that support AI agent extensions.

    No, the skill is hard-coded to reject relative terms; you must provide a reference date or specific ISO-dated source material, otherwise it will flag the deadline as a blocking issue to prevent scheduling errors.

    The purchase includes the core logic configuration files for the skill, a README with integration instructions for various agents, and a set of templates to ensure consistent output formatting.

    Yes, buyers receive lifetime access to all future refinements, including updates that improve extraction accuracy or add compatibility for new AI agent frameworks as they emerge.

    The skill is built to generate one brief for one specific audience at a time; if you need to brief multiple stakeholders with different needs, you should run the skill separately for each to maintain the 'one ask' high-signal focus.

    New in Technical Documentation