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 every stakeholder before engaging anyone. An agent skill from deanpeters/Product-Manager-Skills.
Custom licenceAuto-check passed
Install Stakeholder Identification
$ npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-identification -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install deanpeters/Product-Manager-Skills stakeholder-identification --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/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/stakeholder-identification .claude/skills/stakeholder-identification && 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-identification" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/stakeholder-identification into .claude/skills/stakeholder-identification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-identification", 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/deanpeters/Product-Manager-Skills/tree/main/skills/stakeholder-identificationType 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 deanpeters/Product-Manager-Skills --skill stakeholder-identification -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install deanpeters/Product-Manager-Skills stakeholder-identification --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/stakeholder-identification .agents/skills/stakeholder-identification && 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-identification" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/stakeholder-identification into .agents/skills/stakeholder-identification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-identification", 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 deanpeters/Product-Manager-Skills --skill stakeholder-identification -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install deanpeters/Product-Manager-Skills stakeholder-identification --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/stakeholder-identification .cursor/skills/stakeholder-identification && 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-identification" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/stakeholder-identification into .cursor/skills/stakeholder-identification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-identification", 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/deanpeters/Product-Manager-Skills.git --path skills/stakeholder-identification--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 deanpeters/Product-Manager-Skills --skill stakeholder-identification -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install deanpeters/Product-Manager-Skills stakeholder-identification --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/stakeholder-identification .gemini/skills/stakeholder-identification && 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-identification" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/stakeholder-identification into .gemini/skills/stakeholder-identification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-identification", 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 deanpeters/Product-Manager-Skills stakeholder-identificationInstalls 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 deanpeters/Product-Manager-Skills --skill stakeholder-identification -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/stakeholder-identification .github/skills/stakeholder-identification && 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-identification" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/stakeholder-identification into .github/skills/stakeholder-identification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-identification", 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 deanpeters/Product-Manager-Skills --skill stakeholder-identification -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install deanpeters/Product-Manager-Skills stakeholder-identification --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/stakeholder-identification .opencode/skills/stakeholder-identification && 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-identification" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/stakeholder-identification into .opencode/skills/stakeholder-identification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-identification", 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-identification- GitHub stars
- 7.2k
- Token cost
- ~3k tokens
- SKILL.md length
- 1,381 words
- Files
- 4
- Skills in repo
- 75
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Map every stakeholder before engaging anyone. An agent skill from deanpeters/Product-Manager-Skills.
- Launching an initiative
- SKILL.md covers Purpose, Input, Key Concepts and Application, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Scoping discovery
What it does
Stakeholder Identification is an agent skill from deanpeters/Product-Manager-Skills. Map every stakeholder before engaging anyone. Use when launching an initiative, scoping discovery, or building an engagement plan from scratch.
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `examples/sample-industrial.md`, `examples/sample.md` and `template.md`).
The repository describes itself as: Product Management skills framework built on battle-tested methods for Claude Code, Cowork, Codex, and AI agents.
When your agent uses it
- Launching an initiative
- Scoping discovery
- Building an engagement plan from scratch
Example prompts
- “/stakeholder-identification”
What it can do on your machine
Read from SKILL.md and the folder at commit 1b5a524. 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
Links to these hosts (documentation or services it may open):
itk.mitre.org
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 Identification loads about 3k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 1,381 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,381 words (~3,014 tokens).
“Map every stakeholder before engaging anyone. This skill produces a comprehensive, equity-aware stakeholder set — not just the obvious sponsors and users, but the gatekeepers, the impacted communities, and the voices your team defaults to overlooking.”
- name
- stakeholder-identification
- argument-hint
- [initiative]
- intent
- Produce a comprehensive, equity-aware stakeholder set before any engagement begins. Combines broad brainstorm with structured categorization (Allies /…
- type
- component
- best_for
- Launching a new initiative where the stakeholder landscape is unmapped and influence networks are unknown, Scoping a discovery sprint to define who to…
- scenarios
- Who are all the stakeholders for this initiative?, Are we missing anyone important in our stakeholder map?, Help me prepare the stakeholder section of my PRD…
- sources
- MITRE Innovation Toolkit — Stakeholder Identification Canvas: https://itk.mitre.org/toolkit-tools/stakeholder-identification-canvas/, MITRE Innovation Toolkit…
- theme
- stakeholder-comms
- estimated_time
- 20-30 min
Files
SKILL.md and 3 other files in skills/stakeholder-identification of deanpeters/Product-Manager-Skills.
- SKILL.md
- examples/sample-industrial.md
- examples/sample.md
- template.md
Open the folder on GitHubat commit 1b5a524
Compare with similar skills
Stakeholder Identification 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 Identification this skilldeanpeters/Product-Manager-Skills | 7.2k | — | ~3k | Automated safety check: Pass | Custom licence | |
| Stakeholder Mapphuryn/pm-skills | 27k | — | ~625 | Automated safety check: Pass | MIT | |
| Designing Adversary Engagement With Mitre Engagemukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Shipping and Launch Checklistaddyosmani/agent-skills | 104k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Stakeholder Mapborghei/Claude-Skills | 891 | — | ~2k | Automated safety check: Pass | MIT | |
| Token Mapnexu-io/open-design | 100k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Designing Adversary Engagement With Mitre Engage
mukul975/Anthropic-Cybersecurity-Skills
Plan, run, and measure an adversary engagement operation using the MITRE Engage framework so that deployed deception is driven by strategy instead of deployed ad hoc.
Shipping and Launch Checklist
addyosmani/agent-skills
Prepares a production launch with a pre-launch checklist, monitoring, a staged rollout and a rollback plan so every release is reversible and observable.
Stakeholder Map
borghei/Claude-Skills
Map stakeholders by power × interest and design a communication plan that prevents surprise objections.
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.
Launch Strategy
alirezarezvani/claude-skills
When the user wants to plan a product launch, feature announcement, or release strategy.
More from deanpeters/Product-Manager-Skills
All 75 skills in this repoUser 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.
TAM SAM SOM Calculator
deanpeters/Product-Manager-Skills
Calculates total, serviceable available and serviceable obtainable market size for a product idea with explicit assumptions, methods and caveats.
Organic Growth Path Advisor
deanpeters/Product-Manager-Skills
Diagnoses where a growth constraint lives and recommends one organic growth path from the McKinsey Growth Pyramid to test first.
Prioritization Framework Advisor
deanpeters/Product-Manager-Skills
Picks the right prioritization framework for your stage and context instead of defaulting to RICE or ICE out of habit.
Strategic Roadmap Planning
deanpeters/Product-Manager-Skills
Sequences prioritization, epic definition, and stakeholder alignment into a release plan that ladders up to business outcomes.
User Story Mapping
deanpeters/Product-Manager-Skills
Lays out a user journey as activities, steps, and tasks on a two-dimensional map that then informs backlog slicing.
Questions about Stakeholder Identification
What does Stakeholder Identification do?
Map every stakeholder before engaging anyone. An agent skill from deanpeters/Product-Manager-Skills. Stakeholder Identification is an agent skill from deanpeters/Product-Manager-Skills. Map every stakeholder before engaging anyone.
When should I use Stakeholder Identification?
Stakeholder Identification fits situations like: launching an initiative; scoping discovery; building an engagement plan from scratch.
How do I install Stakeholder Identification in Claude Code?
Run `npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-identification -a claude-code`. Or copy the skill folder (skills/stakeholder-identification in deanpeters/Product-Manager-Skills) into .claude/skills/stakeholder-identification in your project. Claude Code loads it when a task matches its description.
How do I install Stakeholder Identification in Codex?
Run `npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-identification -a codex`. Or copy the skill folder (skills/stakeholder-identification in deanpeters/Product-Manager-Skills) into .agents/skills/stakeholder-identification in your project. Codex loads it when a task matches its description.
Can I use Stakeholder Identification 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 deanpeters/Product-Manager-Skills --skill stakeholder-identification -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-identification, .gemini/skills/stakeholder-identification, .github/skills/stakeholder-identification and .opencode/skills/stakeholder-identification in your project.
What does Stakeholder Identification need to run?
SKILL.md names no scripts, command-line tools or credentials: Stakeholder Identification is instructions for the agent only.
Does Stakeholder Identification access the network?
SKILL.md names 1 domain. As links in the text: itk.mitre.org. This is read from the text; nothing was executed.
Is Stakeholder Identification 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 Identification use?
Stakeholder Identification has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Stakeholder Identification use?
About 3k tokens (SKILL.md is roughly 12k 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 Identification?
Skills that share tags, products or a category with Stakeholder Identification: Stakeholder Map (phuryn/pm-skills, 27k stars), Designing Adversary Engagement With Mitre Engage (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Shipping and Launch Checklist (addyosmani/agent-skills, 104k 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 Identification?
deanpeters (a GitHub user) maintains it in deanpeters/Product-Manager-Skills, which has 7,224 GitHub stars. The repository holds 75 skills in this directory. The repository was last updated on September 1, 2026.
Source: deanpeters/Product-Manager-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.