New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Stakeholder Map

by borghei in borghei/Claude-Skills

Map stakeholders by power × interest and design a communication plan that prevents surprise objections.

MITAuto-check passedProduct & Project Management

Install Stakeholder Map

skills CLI
$ npx skills add borghei/Claude-Skills --skill stakeholder-map -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills stakeholder-map --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/project-management/execution/stakeholder-map .claude/skills/stakeholder-map && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
stakeholder-map
GitHub stars
874
Token cost
~2k tokens
SKILL.md length
883 words
Files
5 (incl. scripts, references, assets)
Skills in repo
364
Repo updated
First seen
Licence
MIT

At a glance

Map stakeholders by power × interest and design a communication plan that prevents surprise objections.

  • Works in 7 steps: List all stakeholders → Rate Power + Interest (1-5) → Add Support (stance) → …
  • Launching a major initiative
  • SKILL.md covers When to use this skill, The 2x2: Power × Interest, Clarify First and Workflow, plus 5 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Stakeholder Map is an agent skill from borghei/Claude-Skills. Map stakeholders by power × interest and design a communication plan that prevents surprise objections. Use when launching a major initiative, navigating an enterprise deal, planning a re-org, or pre-empting resistance to a roadmap change.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/stakeholder_map_template.md`, `references/stakeholder-anti-patterns.md` and `references/stakeholder-mapping-framework.md`).

It sits in Product & Project Management. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Launching a major initiative
  • Navigating an enterprise deal
  • Planning a re-org
  • Pre-empting resistance to a roadmap change

Example prompts

  • “/stakeholder-map”

Requirements

  • Python 3

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. List all stakeholders
  2. Rate Power + Interest (1-5)
  3. Add Support (stance)
  4. Identify the matrix sweet spot
  5. Design engagement plan per quadrant
  6. Address blockers explicitly
  7. Run stakeholder_analyzer.py

What it can do on your machine

Read from SKILL.md and the folder at commit c9a1487. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Stakeholder Map loads about 2k tokens when it runs, and up to ~5.1k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 883 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit c9a1487, republished under its MIT licence (© borghei). 883 words, ~1,985 tokens.

Download SKILL.mdSave it as .claude/skills/stakeholder-map/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
stakeholder-map
description
Map stakeholders by power × interest and design a communication plan that prevents surprise objections. Use when launching a major initiative, navigating an enterprise deal, planning a re-org, or pre-empting resistance to a roadmap change.
license
MIT + Commons Clause
metadata.version
1.0.0
metadata.author
borghei
metadata.category
project-management
metadata.domain
execution
metadata.updated
2026-05-27
metadata.python-tools
stakeholder_analyzer.py
metadata.tech-stack
stakeholder-mapping, power-interest, change-management

Stakeholder Map

A 2x2 grid of stakeholders, plus a tactical engagement plan derived from the map. Used to pre-empt resistance, route decisions correctly, and match communication cadence to influence.

When to use this skill

  • Major initiative launch (re-platform, pricing change, market expansion)
  • Enterprise deal navigation (multiple buying-committee members)
  • Org re-design / re-org planning
  • Roadmap change affecting multiple stakeholders
  • Pre-board / pre-exec strategic decisions
  • Post-mortem stakeholder map (who didn't we engage that we should have?)

The 2x2: Power × Interest

Low PowerHigh Power
High InterestKeep informedManage closely
Low InterestMonitorKeep satisfied
Quadrants
  • Manage closely (HP/HI): key decisions; influence + engaged. Highest investment.
  • Keep satisfied (HP/LI): authority but not engaged. Don't let them surprise you.
  • Keep informed (LP/HI): advocates and detractors who care. Use them.
  • Monitor (LP/LI): light touch.

Clarify First

Before mapping, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • The initiative being mapped — the specific launch/deal/re-org/roadmap change (defines who counts as a stakeholder at all, Step 1)
  • Each stakeholder's power source — hierarchy vs veto vs budget vs domain expertise (a compliance lead may outrank a VP; drives the Power axis in Step 2)
  • Each stakeholder's stance — champion → supporter → neutral → skeptic → blocker (drives Step 3 and the conversion plans in Step 6)
  • Decision/launch deadline — when the verdict lands (sets engagement cadence per quadrant, Step 5)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Workflow

Step 1 — List all stakeholders

Brainstorm:

  • Executive sponsors
  • Decision-makers
  • Influencers
  • Implementers
  • Users / customers
  • Adjacent teams
  • External parties (vendors, regulators, partners)

Don't filter yet. List broadly, prune later.

Step 2 — Rate Power + Interest (1-5)

For each:

  • Power: can they kill or accelerate this? authority? budget? veto?
  • Interest: how much do they care about the outcome?
Step 3 — Add Support (stance)

Each stakeholder is also somewhere on:

  • Champion (actively supports)
  • Supporter (positive but passive)
  • Neutral
  • Skeptic
  • Blocker (actively opposes)

This complements Power×Interest with directionality.

Step 4 — Identify the matrix sweet spot

The critical stakeholders: high power + high interest + not-yet-supporters.

These are who you need to convert.

Step 5 — Design engagement plan per quadrant
QuadrantEngagement pattern
Manage closelyWeekly 1:1, deep involvement, co-author key docs
Keep satisfiedMonthly check-in, pre-brief major decisions
Keep informedEmail updates, FYI inclusion, surface their concerns publicly
MonitorQuarterly newsletter; no proactive
Step 6 — Address blockers explicitly

For each blocker:

  • What's their objection?
  • What evidence might change their view?
  • Who do they listen to?
  • Can we convert, neutralize, or out-vote?

Ignoring blockers = late surprise objection that derails the initiative.

Step 7 — Run stakeholder_analyzer.py

Audit for: missing key stakeholders by role, blockers without plans, power-without-interest gaps, no engagement plan.

bash
python3 project-management/execution/stakeholder-map/scripts/stakeholder_analyzer.py \
  --input stakeholders.json --format markdown

Decision frameworks

Power dimensions (be specific)
  • Hierarchical authority (CEO/board > VP > Director)
  • Budget control (who allocates $)
  • Veto power (legal, compliance, infosec)
  • Domain expertise (the one person who actually understands X)
  • Coalition power (who their faction follows)
  • External legitimacy (analyst, customer reference, regulator)

A "low-hierarchy / high-veto" stakeholder (e.g., compliance lead) often has more power than a "high-hierarchy / low-domain" one.

Interest dimensions
  • Outcome impact (will this affect their world?)
  • Personal stake (career, comp, ego)
  • Resource impact (their team, their budget)
  • Public visibility (their reputation tied to this)
Show full SKILL.md (349 more words)Show less
Common engagement patterns

For executive sponsor (HP/HI):

  • Weekly 1:1 (you bring updates + asks)
  • Co-author the strategic narrative
  • Defend at board level
  • Veto power to be used selectively

For powerful skeptic (HP/HI, low support):

  • Discover the actual objection (often different than stated)
  • Find evidence that addresses it
  • Pre-brief before big decisions
  • Make their support visible to their peers

For powerless advocate (LP/HI, high support):

  • Use them to influence others
  • Amplify their voice publicly
  • Don't burn them with surprise asks

For powerful absent leader (HP/LI):

  • Don't let them tune in late and veto
  • Pre-brief before key decisions
  • Make engagement low-friction (5-min readouts)
When to escalate vs route around
  • Escalate when: stakeholder's authority is structurally needed
  • Route around when: stakeholder is tangential and adding friction
  • Never route around: legal, security, compliance, finance approvers

Common engagements

"Help me build a stakeholder map for the launch"
  1. Brainstorm 20+ stakeholders.
  2. Rate Power, Interest, Support per stakeholder.
  3. Plot the 2x2.
  4. Identify the critical 5-10 (HP/HI).
  5. For each blocker, design conversion plan.
  6. Document engagement cadence per quadrant.
"Audit a recent failed launch"
  1. Map the stakeholders involved.
  2. Identify who derailed it (often a HP/LI we missed).
  3. Identify who could have helped but wasn't engaged.
  4. Update default stakeholder template for next launch.
"Navigate an enterprise deal with 8 buying-committee members"
  1. Map all 8 + 4-5 unofficial influencers.
  2. Identify economic buyer, technical buyer, user, executive sponsor.
  3. Engagement plan per role.
  4. Address blockers (legal, security) early; don't wait for procurement.

Anti-patterns to avoid

  • No stakeholder map. Trust the org chart; surprised by lateral resistance.
  • Map without engagement plan. Knowing isn't acting.
  • Ignoring blockers. They surface at the worst moment.
  • Treating power as just hierarchy. Vetoes matter; expertise matters.
  • No HP/LI engagement. Sleeping authority becomes late veto.
  • Static map. Power + stance shift; refresh per quarter / per phase.
  • Mapping without input from someone politically savvy. Solo maps miss reality.

References

  • references/stakeholder-mapping-framework.md — power dimensions, support spectrum, engagement plans
  • references/stakeholder-anti-patterns.md — common failures + worked fixes
  • project-management/execution/daci-framework — decision-rights model
  • project-management/execution/summarize-meeting — communication artifacts
  • c-level-advisor/ceo-advisor — executive context
  • c-level-advisor/general-counsel-advisor — legal stakeholder navigation
  • business-growth/sales-engineer — buying-committee mapping

© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts, references, assets) in project-management/execution/stakeholder-map of borghei/Claude-Skills.

  • SKILL.md
  • assets/stakeholder_map_template.md
  • references/stakeholder-anti-patterns.md
  • references/stakeholder-mapping-framework.md
  • scripts/stakeholder_analyzer.py

Open the folder on GitHubat commit c9a1487

Compare with similar skills

Stakeholder Map next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Stakeholder Map compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Stakeholder Map this skillborghei/Claude-Skills874—~2kAutomated safety check: PassMIT
User Story Writerdeanpeters/Product-Manager-Skills7.2k2 repos~2.9kAutomated safety check: PassCustom licence
Game Changing FeaturesopenstatusHQ/data-table-filters2.3k3 repos~2.1kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Convex Create Componentspokvulcan/poker-planning1148 repos~2.6kAutomated safety check: PassMIT
Self Improving Agentfarm-fe/farm5.6k2 repos~3.3kAutomated safety check: NotesMIT

Similar skills

  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed

  • Game Changing Features

    openstatusHQ/data-table-filters

    Find 10x product opportunities and high-leverage improvements.

    2.3k GitHub starsUsed in 3 repos~2.1k tokens
    Product & Project ManagementAuto-check passed

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Convex Create Component

    spokvulcan/poker-planning

    Builds reusable Convex components with isolated tables and app-facing APIs.

    114 GitHub starsUsed in 8 repos~2.6k tokens
    Product & Project ManagementAuto-check passed

  • Self Improving Agent

    farm-fe/farm

    A universal self-improving agent that learns from ALL skill experiences.

    5.6k GitHub starsUsed in 2 repos~3.3k tokens
    Product & Project ManagementAuto-check: notes

  • Weekly Engineering Retro

    garrytan/gstack

    Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.

    136k GitHub stars~2.4k tokensUpdated today
    Product & Project ManagementAuto-check passed

More from borghei/Claude-Skills

All 364 skills in this repo

  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    874 GitHub stars~4.2k tokensUpdated yesterday
    Auto-check passed

  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    874 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    874 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed

  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    874 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    874 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed

  • Brainstorm Okrs

    borghei/Claude-Skills

    OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.

    874 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Stakeholder Map

What does Stakeholder Map do?

Map stakeholders by power × interest and design a communication plan that prevents surprise objections. Stakeholder Map is an agent skill from borghei/Claude-Skills. Map stakeholders by power × interest and design a communication plan that prevents surprise objections.

When should I use Stakeholder Map?

Stakeholder Map fits situations like: launching a major initiative; navigating an enterprise deal; planning a re-org; pre-empting resistance to a roadmap change.

How do I install Stakeholder Map in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill stakeholder-map -a claude-code`. Or copy the skill folder (project-management/execution/stakeholder-map in borghei/Claude-Skills) into .claude/skills/stakeholder-map in your project. Claude Code loads it when a task matches its description.

How do I install Stakeholder Map in Codex?

Run `npx skills add borghei/Claude-Skills --skill stakeholder-map -a codex`. Or copy the skill folder (project-management/execution/stakeholder-map in borghei/Claude-Skills) into .agents/skills/stakeholder-map in your project. Codex loads it when a task matches its description.

Can I use Stakeholder Map in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill stakeholder-map -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stakeholder-map, .gemini/skills/stakeholder-map, .github/skills/stakeholder-map and .opencode/skills/stakeholder-map in your project.

What does Stakeholder Map need to run?

Going by SKILL.md and its folder, Stakeholder Map needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Stakeholder Map access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Stakeholder Map safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Stakeholder Map use?

Stakeholder Map is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Stakeholder Map use?

About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.1k tokens, read only when the agent opens those files.

What are the alternatives to Stakeholder Map?

Skills that share tags, products or a category with Stakeholder Map: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Convex Create Component (spokvulcan/poker-planning, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Stakeholder Map?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 874 GitHub stars. The repository holds 364 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.