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 stakeholders for a product decision and produce a tailored influence strategy with talking points.
MITAuto-check passed
Install Stakeholder Influence Mapper
$ npx skills add mohitagw15856/pm-claude-skills --skill stakeholder-influence-mapper -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills stakeholder-influence-mapper --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/stakeholder-influence-mapper .claude/skills/stakeholder-influence-mapper && 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-influence-mapper" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/stakeholder-influence-mapper into .claude/skills/stakeholder-influence-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-influence-mapper", 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/mohitagw15856/pm-claude-skills/tree/main/skills/stakeholder-influence-mapperType 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 mohitagw15856/pm-claude-skills --skill stakeholder-influence-mapper -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills stakeholder-influence-mapper --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/stakeholder-influence-mapper .agents/skills/stakeholder-influence-mapper && 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-influence-mapper" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/stakeholder-influence-mapper into .agents/skills/stakeholder-influence-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-influence-mapper", 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 mohitagw15856/pm-claude-skills --skill stakeholder-influence-mapper -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills stakeholder-influence-mapper --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/stakeholder-influence-mapper .cursor/skills/stakeholder-influence-mapper && 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-influence-mapper" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/stakeholder-influence-mapper into .cursor/skills/stakeholder-influence-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-influence-mapper", 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/mohitagw15856/pm-claude-skills.git --path skills/stakeholder-influence-mapper--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 mohitagw15856/pm-claude-skills --skill stakeholder-influence-mapper -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills stakeholder-influence-mapper --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/stakeholder-influence-mapper .gemini/skills/stakeholder-influence-mapper && 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-influence-mapper" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/stakeholder-influence-mapper into .gemini/skills/stakeholder-influence-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-influence-mapper", 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 mohitagw15856/pm-claude-skills stakeholder-influence-mapperInstalls 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 mohitagw15856/pm-claude-skills --skill stakeholder-influence-mapper -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/stakeholder-influence-mapper .github/skills/stakeholder-influence-mapper && 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-influence-mapper" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/stakeholder-influence-mapper into .github/skills/stakeholder-influence-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-influence-mapper", 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 mohitagw15856/pm-claude-skills --skill stakeholder-influence-mapper -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills stakeholder-influence-mapper --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/stakeholder-influence-mapper .opencode/skills/stakeholder-influence-mapper && 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-influence-mapper" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/stakeholder-influence-mapper into .opencode/skills/stakeholder-influence-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-influence-mapper", 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.
Facts
- Skill name
stakeholder-influence-mapper- GitHub stars
- 1.4k
- Token cost
- ~952 tokens
- SKILL.md length
- 446 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Map stakeholders for a product decision and produce a tailored influence strategy with talking points.
- Works in 6 steps: Build stakeholder map with: role,… → Identify the critical path of… → For each stakeholder, lead with their… → …
- Asked to get alignment
- SKILL.md covers Required Inputs, Process, Output Structure and Notes, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Stakeholder Influence Mapper is an agent skill from mohitagw15856/pm-claude-skills. Map stakeholders for a product decision and produce a tailored influence strategy with talking points. Use when asked to get alignment, build consensus, get buy-in from engineering or finance or legal, navigate organisational resistance, or plan stakeholder conversations for a major initiative. Produces a stakeholder map, recommended conversation sequence, and tailored talking points per stakeholder.
Its SKILL.md is about 950 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: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to get alignment
- Build consensus
- Get buy-in from engineering
- Navigate organisational resistance
Example prompts
- “/stakeholder-influence-mapper”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Build stakeholder map with: role, primary concern, decision authority (blocker / influencer / informed), current stance (supportive /…
- Identify the critical path of conversations — who must be won before others
- For each stakeholder, lead with their concern, not your ask
- Prepare one likely objection per stakeholder and a prepared response
- Flag any stakeholders who should NOT be approached until others are aligned
- Validate — Confirm every "blocker" stakeholder has a specific tactic (not just "have a conversation"), and that the sequence accounts for…
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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
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.
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 Influence Mapper loads about 952 tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 446 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.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 446 words, ~952 tokens.
Download SKILL.mdSave it as
.claude/skills/stakeholder-influence-mapper/SKILL.md (or your agent's skills folder).- name
- stakeholder-influence-mapper
- description
- Map stakeholders for a product decision and produce a tailored influence strategy with talking points. Use when asked to get alignment, build consensus, get buy-in from engineering or finance or legal, navigate organisational resistance, or plan stakeholder conversations for a major initiative. Produces a stakeholder map, recommended conversation sequence, and tailored talking points per stakeholder.
Stakeholder Influence Mapper Skill
Turn a product initiative into a structured influence plan — who needs to be aligned, in what order, and exactly what to say to each person in their language.
Required Inputs
Ask the user for these if not provided:
- Initiative description (what you want to do and why)
- List of key stakeholders (name, role, relationship to initiative)
- Timeline pressure (when do you need a decision?)
- Any known objections or political context (what you're already aware of)
Process
- Build stakeholder map with: role, primary concern, decision authority (blocker / influencer / informed), current stance (supportive / neutral / resistant / unknown)
- Identify the critical path of conversations — who must be won before others
- For each stakeholder, lead with their concern, not your ask
- Prepare one likely objection per stakeholder and a prepared response
- Flag any stakeholders who should NOT be approached until others are aligned
- Validate — Confirm every "blocker" stakeholder has a specific tactic (not just "have a conversation"), and that the sequence accounts for political dependencies
Output Structure
Stakeholder Map: [Initiative Name]
| Stakeholder | Role | Primary Concern | Authority | Current Stance |
|---|---|---|---|---|
| [name] | [role] | [concern] | [type] | [stance] |
Recommended Conversation Sequence
- [Name first] — because [reason they unlock others]
- [Name second] — once [first] is aligned [continue...]
Talking Points by Stakeholder
[Stakeholder Name]
Lead with: [Their concern, not your feature] Your ask: [One specific thing you need from them] Likely objection: [What they'll push back on] Prepared response: [How to address it without being defensive] What success looks like: [What alignment from them looks like]
Show full SKILL.md (191 more words)Show less
Notes
- Never send the same message to all stakeholders — calibrate every time
- Engineering leads want technical feasibility acknowledged first
- Finance stakeholders want ROI framing before anything else
- Legal/compliance stakeholders want risk mitigation addressed upfront
Quality Checks
- Every blocker has a specific tactic (not just "have a chat")
- Conversation sequence accounts for political dependencies
- Each stakeholder's talking points lead with their concern, not your agenda
- At least one "do not approach until X is aligned" flag is considered
- The ask from each stakeholder is a single, specific thing (not a vague "support")
Anti-Patterns
- Do not approach high-influence blockers before aligning their sponsors — approach order determines outcome
- Do not create talking points that lead with your agenda — always lead with the stakeholder's stated concern
- Do not treat every stakeholder as equally important — focus depth on the decision-makers and key influencers
- Do not omit the "do not approach until X is aligned" flags — sequencing mistakes can permanently close doors
- Do not build the map based only on org chart position — influence often lives outside formal authority
Example Trigger Phrases
- "Get alignment."
- "Build consensus."
- "Get buy-in from engineering."
- "Plan stakeholder conversations for a major initiative."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/stakeholder-influence-mapper of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Stakeholder Influence Mapper 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 Influence Mapper this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~952 | 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 | |
| Token Mapnexu-io/open-design | 100k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Stakeholder Mapborghei/Claude-Skills | 891 | — | ~2k | Automated safety check: Pass | MIT | |
| Maps Geographyasgeirtj/system_prompts_leaks | 69k | — | ~717 | Automated safety check: Pass | CC0-1.0 |
Similar skills
Stakeholder Mapping
deanpeters/Product-Manager-Skills
Prioritize stakeholders using two complementary grids. An agent skill from deanpeters/Product-Manager-Skills.
Token Map
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.
Stakeholder Map
borghei/Claude-Skills
Map stakeholders by power × interest and design a communication plan that prevents surprise objections.
Maps Geography
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
Apify Influencer Discovery
sickn33/agentic-awesome-skills
Find and evaluate influencers for brand partnerships, verify authenticity, and track collaboration performance across Instagram, Facebook, YouTube, and TikTok.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Questions about Stakeholder Influence Mapper
What does Stakeholder Influence Mapper do?
Map stakeholders for a product decision and produce a tailored influence strategy with talking points. Stakeholder Influence Mapper is an agent skill from mohitagw15856/pm-claude-skills. Map stakeholders for a product decision and produce a tailored influence strategy with talking points.
When should I use Stakeholder Influence Mapper?
Stakeholder Influence Mapper fits situations like: asked to get alignment; build consensus; get buy-in from engineering; navigate organisational resistance.
How do I install Stakeholder Influence Mapper in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill stakeholder-influence-mapper -a claude-code`. Or copy the skill folder (skills/stakeholder-influence-mapper in mohitagw15856/pm-claude-skills) into .claude/skills/stakeholder-influence-mapper in your project. Claude Code loads it when a task matches its description.
How do I install Stakeholder Influence Mapper in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill stakeholder-influence-mapper -a codex`. Or copy the skill folder (skills/stakeholder-influence-mapper in mohitagw15856/pm-claude-skills) into .agents/skills/stakeholder-influence-mapper in your project. Codex loads it when a task matches its description.
Can I use Stakeholder Influence Mapper 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 mohitagw15856/pm-claude-skills --skill stakeholder-influence-mapper -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-influence-mapper, .gemini/skills/stakeholder-influence-mapper, .github/skills/stakeholder-influence-mapper and .opencode/skills/stakeholder-influence-mapper in your project.
What does Stakeholder Influence Mapper need to run?
SKILL.md names no scripts, command-line tools or credentials: Stakeholder Influence Mapper is instructions for the agent only.
Does Stakeholder Influence Mapper 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 Influence Mapper 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. Review the folder before installing.
What licence does Stakeholder Influence Mapper use?
Stakeholder Influence Mapper is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Stakeholder Influence Mapper use?
About 952 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Stakeholder Influence Mapper?
Skills that share tags, products or a category with Stakeholder Influence Mapper: Stakeholder Map (phuryn/pm-skills, 27k stars), Stakeholder Mapping (deanpeters/Product-Manager-Skills, 7.2k stars), Token Map (nexu-io/open-design, 100k stars) and Stakeholder Map (borghei/Claude-Skills, 891 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Stakeholder Influence Mapper?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-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.