Stakeholder Map
phuryn/pm-skills
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan.
Map the people who can make or break a decision onto a Power/Interest grid, with each named stakeholder's stance (champion / skeptic / blocker / unknown), what they care about, and the single…
$ npx skills add sruthir28/enterprise-ai-skills --skill stakeholder-map -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sruthir28/enterprise-ai-skills stakeholder-map --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sruthir28/enterprise-ai-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/stakeholder-map .claude/skills/stakeholder-map && rm -rf skills-srcUse ~/.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/
Install the "stakeholder-map" agent skill from https://github.com/sruthir28/enterprise-ai-skills/tree/main/stakeholder-map into .claude/skills/stakeholder-map/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-map", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sruthir28/enterprise-ai-skills/tree/main/stakeholder-mapType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sruthir28/enterprise-ai-skills --skill stakeholder-map -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sruthir28/enterprise-ai-skills stakeholder-map --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sruthir28/enterprise-ai-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/stakeholder-map .agents/skills/stakeholder-map && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "stakeholder-map" agent skill from https://github.com/sruthir28/enterprise-ai-skills/tree/main/stakeholder-map into .agents/skills/stakeholder-map/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-map", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sruthir28/enterprise-ai-skills --skill stakeholder-map -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sruthir28/enterprise-ai-skills stakeholder-map --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sruthir28/enterprise-ai-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/stakeholder-map .cursor/skills/stakeholder-map && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "stakeholder-map" agent skill from https://github.com/sruthir28/enterprise-ai-skills/tree/main/stakeholder-map into .cursor/skills/stakeholder-map/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-map", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sruthir28/enterprise-ai-skills.git --path stakeholder-map--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sruthir28/enterprise-ai-skills --skill stakeholder-map -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sruthir28/enterprise-ai-skills stakeholder-map --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sruthir28/enterprise-ai-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/stakeholder-map .gemini/skills/stakeholder-map && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "stakeholder-map" agent skill from https://github.com/sruthir28/enterprise-ai-skills/tree/main/stakeholder-map into .gemini/skills/stakeholder-map/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-map", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sruthir28/enterprise-ai-skills stakeholder-mapInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sruthir28/enterprise-ai-skills --skill stakeholder-map -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sruthir28/enterprise-ai-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/stakeholder-map .github/skills/stakeholder-map && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "stakeholder-map" agent skill from https://github.com/sruthir28/enterprise-ai-skills/tree/main/stakeholder-map into .github/skills/stakeholder-map/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-map", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sruthir28/enterprise-ai-skills --skill stakeholder-map -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sruthir28/enterprise-ai-skills stakeholder-map --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sruthir28/enterprise-ai-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/stakeholder-map .opencode/skills/stakeholder-map && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "stakeholder-map" agent skill from https://github.com/sruthir28/enterprise-ai-skills/tree/main/stakeholder-map into .opencode/skills/stakeholder-map/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-map", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
stakeholder-mapMap the people who can make or break a decision onto a Power/Interest grid, with each named stakeholder's stance (champion / skeptic / blocker / unknown), what they care about, and the single…
Stakeholder Map is an agent skill from sruthir28/enterprise-ai-skills. Map the people who can make or break a decision onto a Power/Interest grid, with each named stakeholder's stance (champion / skeptic / blocker / unknown), what they care about, and the single influence move you'll make for them. Use before any cross-functional decision, big launch, reorg, or executive ask — anywhere the politics will decide the outcome more than the merits.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Open-source AI skills for enterprise professionals. McKinsey consulting frameworks, PM workflows, and practical tools. Currently for Claude, expanding to other LLMs. The licence is MIT.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit ae8fe60. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Stakeholder Map loads about 2.4k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 1,230 words of instructions outside code blocks.
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.
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); files beside SKILL.md are not scanned.
The full file from sruthir28/enterprise-ai-skills at commit ae8fe60, republished under its MIT licence (© sruthir28). 1,230 words, ~2,403 tokens.
.claude/skills/stakeholder-map/SKILL.md (or your agent's skills folder).Most decisions don't fail because the analysis was wrong. They fail because the person who could kill it wasn't bought in, or the person who could champion it wasn't asked. This skill makes the politics visible so you can plan around them — without pretending strategy and people are separate problems.
The output is a 2x2 grid + a per-stakeholder action plan. You walk away knowing exactly who you talk to first, what you say, and who you can ignore.
HIGH INTEREST LOW INTEREST
┌──────────────────────────┬──────────────────────────┐
│ │ │
HIGH │ MANAGE CLOSELY │ KEEP SATISFIED │
POWER │ (the actual deciders) │ (don't surprise them) │
│ │ │
├──────────────────────────┼──────────────────────────┤
│ │ │
LOW │ KEEP INFORMED │ MONITOR │
POWER │ (your loud allies) │ (don't waste cycles) │
│ │ │
└──────────────────────────┴──────────────────────────┘The deciders. They will say yes or no. Most of your time goes here. 1:1 alignment before the decision moment. Never let them be surprised in a group meeting.
Senior people whose space you're stepping into but who don't care about this specific decision yet. The risk: they hear about it secondhand and feel disrespected, then start caring (and blocking). Pre-brief them on what you're doing and why. Don't ask for input you won't use.
The team. The folks doing the work. They can't kill it but they can slow it. Visibility + giving them a role kills 80% of friction. Channel them into the decision via the deciders, not as a parallel campaign.
Don't ignore — monitor. Quarterly update is plenty. The risk is they shift into one of the other quadrants (someone gets promoted, scope expands) and you're caught off guard.
| Stakeholder | Role | Quadrant | Stance | What they care about | Your move this week |
|---|---|---|---|---|---|
| Sarah Chen | CTO | Manage closely | Skeptic | Reliability + team retention | 1:1 Tuesday, lead with retention data, ask for her objections before the all-hands |
| ... | ... | ... | ... | ... | ... |
Who needs to be aligned, in what order, before the decision moment. Example:
"Win Sarah by EOW (she's the blocker). Once Sarah's neutral, Mark (champion) will close Priya. Don't engage Tom — he won't care unless Sarah escalates."
Decision: Migrate engineering + product from Jira to Linear by 5/30. Decision moment: EOD Friday (today is Tuesday) — Mark approves or denies the budget swap.
| Stakeholder | Role | Quadrant | Stance | What they care about | Move this week |
|---|---|---|---|---|---|
| Mark Chen | VP Eng (decider) | Manage closely | Neutral → Skeptic | Team retention, no rollout drama | 30-min 1:1 Weds. Lead with NPS data (4/10) + 2 pilot teams' productivity wins. Pre-empt his "what about 6 yrs of history" objection. |
| Priya Patel | PM Lead (pilot) | Manage closely | Champion | Faster ship velocity | Ask her to write a 1-pg "what we learned in pilot" by Thurs AM. Mark reads it before our 1:1. |
| Alex Kim | Eng Director (Platform) | Manage closely | Skeptic | Migration of custom workflows | Loop in by Weds. Offer Platform team as the 3rd pilot. Convert from skeptic by giving them control. |
| Tom Reilly | CFO | Keep satisfied | Unknown | Cost, contract risk | Drop a 3-line note Tues PM: "Net savings $18K/yr, decision Fri, no surprises." Don't ask for input. |
| Sarah Wu | Head of People | Keep satisfied | Unknown | Anything that affects team morale | Same as Tom — short pre-brief Wed AM. |
| Eng Team (60ppl) | IC engineers | Keep informed | Mixed (mostly Supporters per pilot data) | Less tooling friction | Mark posts in #eng-all after Friday decision. Don't run a parallel campaign — let Mark own the comms. |
| Jira AE (vendor) | External | Monitor | Blocker | Renewal | Ignore until decision is made. Then 1 email to cancel. |
Tuesday PM: pre-brief Tom + Sarah (kills the "I didn't know" risk). Wednesday: 1:1 with Mark (the actual decision). Bring Priya's pilot write-up. Wednesday PM: convert Alex by offering Platform as pilot #3. Thursday: Mark + Priya + Alex 30-min sync to lock the migration plan. Friday: Mark says yes. Decision goes out.
If Mark is still skeptical Wednesday, escalate to CTO with the pilot data. Don't let it drift to Monday — the renewal auto-renews 5/30.
© sruthir28, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in stakeholder-map of sruthir28/enterprise-ai-skills.
Open the folder on GitHubat commit ae8fe60
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Stakeholder Map this skillsruthir28/enterprise-ai-skills | 148 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Stakeholder Mapphuryn/pm-skills | 27k | — | ~625 | Automated safety check: Pass | MIT | |
| Stakeholder Mappingdeanpeters/Product-Manager-Skills | 7.2k | — | ~3.5k | Automated safety check: Pass | Custom licence | |
| Stakeholder Mapborghei/Claude-Skills | 881 | — | ~2k | Automated safety check: Pass | MIT | |
| Feature Maponyx-dot-app/onyx | 32k | — | ~459 | Automated safety check: Pass | Custom licence | |
| Token Mapnexu-io/open-design | 100k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 |
phuryn/pm-skills
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan.
deanpeters/Product-Manager-Skills
Prioritize stakeholders using two complementary grids. An agent skill from deanpeters/Product-Manager-Skills.
borghei/Claude-Skills
Map stakeholders by power × interest and design a communication plan that prevents surprise objections.
onyx-dot-app/onyx
Use the Onyx feature map (.agents/feature-map/) to learn what a product surface does, the code behind it, and what a change can break.
nexu-io/open-design
Map an extracted Figma / source-code token bag onto the active OD design system, producing a deterministic mapping the generate stage can consume.
asgeirtj/system_prompts_leaks
Accurate maps from real geo data — use for any map, or whenever geography would make a good graphic for a deliverable
sruthir28/enterprise-ai-skills
McKinsey-style storyline framework for building presentation decks.
sruthir28/enterprise-ai-skills
Score and prioritize AI use cases for your own job. An agent skill from sruthir28/enterprise-ai-skills.
sruthir28/enterprise-ai-skills
Builds a 1-page decision memo (context → options → recommendation → risks → ask) enforcing McKinsey memo DNA — brutal brevity, SCP storyline clarity, decision-forcing output, evidence density.
sruthir28/enterprise-ai-skills
Multi-agent pipeline that builds a polished presentation deck from a single topic.
sruthir28/enterprise-ai-skills
McKinsey-style issue tree framework for breaking down complex problems into MECE (Mutually Exclusive, Collectively Exhaustive) components.
sruthir28/enterprise-ai-skills
Generate McKinsey-style consulting charts as native python-pptx objects (editable inside PowerPoint).
Map the people who can make or break a decision onto a Power/Interest grid, with each named stakeholder's stance (champion / skeptic / blocker / unknown), what they care about, and the single…. Stakeholder Map is an agent skill from sruthir28/enterprise-ai-skills. Map the people who can make or break a decision onto a Power/Interest grid, with each named stakeholder's stance (champion / skeptic / blocker / unknown), what they care about, and the single influence move you'll make for them.
Run `npx skills add sruthir28/enterprise-ai-skills --skill stakeholder-map -a claude-code`. Or copy the skill folder (stakeholder-map in sruthir28/enterprise-ai-skills) into .claude/skills/stakeholder-map in your project. Claude Code loads it when a task matches its description.
Run `npx skills add sruthir28/enterprise-ai-skills --skill stakeholder-map -a codex`. Or copy the skill folder (stakeholder-map in sruthir28/enterprise-ai-skills) into .agents/skills/stakeholder-map in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sruthir28/enterprise-ai-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.
SKILL.md names no scripts, command-line tools or credentials: Stakeholder Map is instructions for the agent only.
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.
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. Review the folder before installing.
Stakeholder Map is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Stakeholder Map: Stakeholder Map (phuryn/pm-skills, 27k stars), Stakeholder Mapping (deanpeters/Product-Manager-Skills, 7.2k stars), Stakeholder Map (borghei/Claude-Skills, 881 stars) and Feature Map (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
sruthir28 (a GitHub user) maintains it in sruthir28/enterprise-ai-skills, which has 148 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 1, 2026.
Source: sruthir28/enterprise-ai-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.