Skip to content

skilldrop·docs·How-to

Use the Stakeholder comms pack

Install the Stakeholder comms pack, run its first task, and follow a typical session step by step.

Non-technical audiences: audience profiling, exec summaries, decision logs, and guides. Decks live in the design pack.

Reach for it when: You need to turn a long document or a meeting into something a non-technical or time-poor audience can act on.

1. Install it

npx skilldrop-cli install --pack stakeholder-comms                 # Claude Code, your user folder
npx skilldrop-cli install --pack stakeholder-comms --project       # Claude Code, this repo
npx skilldrop-cli install --pack stakeholder-comms --ide cursor    # or kiro, codex, antigravity, copilot
npx skilldrop-cli install --pack stakeholder-comms --local         # this repo, hidden from git

In Claude Code you can also add the marketplace once (/plugin marketplace add sananthanarayan/skilldrop) and run /plugin install stakeholder-comms@skilldrop.

It brings core with it, so the shared skills are there too.

2. Run the first task: turn a long document into a one-page summary for leadership

Paste this into your agent:

Turn this design doc into a one-page executive summary for our steering committee: <paste the doc>.

How to tell it worked: exec-summary returns a one-page summary that a time-poor reader can act on in 30 seconds, written without jargon.

If nothing happens: If exec-summary does not activate, ask for it by name ("use exec-summary") and check that its folder exists in your skills folder (~/.claude/skills/ by default).

3. A typical session

Bring:

A session takes about 30–60 minutes.

  1. decision-log: Paste the meeting notes, thread or transcript. You get: A structured log of decisions, action items, owners and due dates you can paste into a doc or tracker.
  2. audience-profile: Say who will read it, in your own words. You get: The audience archetype with its rules: length, density, tone, must-have sections and things to never include.
  3. exec-summary: Hand it the long document, the decisions, and the audience profile. You get: A one-page summary a time-poor reader can act on in 30 seconds, without jargon.
  4. doc-critique: Run it on the summary before it goes out. You get: A verdict and severity-tagged findings, such as a missing Ask, each with a suggested fix. You decide: Ship, ship with the listed changes, or rewrite.
  5. output-hygiene: Run it on the final version. You get: The text with machine artifacts stripped and any prose tells quoted with rewrites.

You end with: A decision log with owners and dates, and a reviewed one-page summary ready to send.

Next

Edit this page on GitHub · View source