Guide · Agent skill
How to use the Stakeholder Map Builder agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Stakeholder Map Builder is an agent skill that asks your AI agent to map the people involved in a project or launch on a power and interest grid, then turn that map into a communication plan. It is written for product managers, project leads and anyone new to an initiative who needs a structured view of who matters and why. By the end of this guide you will know what the skill does, how to install it, how to trigger it with a plain request, and where its limits are.
Stakeholder Map Builderphuryn/pm-skills · MIT Download the skill Quick start
- 1Download the ZIP. Get the stakeholder-map ZIP from this page and unzip it so that SKILL.md is in a stakeholder-map folder.
- 2Choose a location. Move the folder to ~/.claude/skills/ for personal use, or to .claude/skills/ inside a project. Claude apps users can upload the ZIP under Settings → Capabilities → Skills instead.
- 3Describe the initiative. Ask the agent in plain language to build a stakeholder map, naming the project or launch you are working on.
- 4Attach context. Add an org chart, project brief or team roster if you have one, so the agent can base its list on real names and roles.
- 5Review the grid. Check each Power and Interest rating and move any stakeholder the agent has misplaced.
- 6Use the communication plan. Work from the plan table for frequency, channel and key message, and act on the flagged conflicts.
- 7Save and update. Keep the saved markdown file in your project and rerun the skill when the initiative changes.
What is an agent skill, and what does this one do?
An agent skill is a folder containing a SKILL.md file that gives an AI agent specific instructions for a task. When a request matches the skill's description, the agent follows those instructions. The skill is named stakeholder-map and its full name is Stakeholder Map Builder.
When you ask the agent to map the people involved in a project, the skill tells it to list relevant individuals and groups, such as executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners and end users. Each one is rated Low or High on two dimensions: Power (ability to influence decisions, resources or outcomes) and Interest (how much the project directly affects them or how engaged they are).
- Places each stakeholder in one of four quadrants: Manage Closely, Keep Satisfied, Keep Informed or Monitor.
- For each quadrant, recommends communication frequency, format, key messages and the risks of neglecting that group.
- Produces a communication plan table with stakeholder, role, power, interest, strategy, frequency, channel and key message columns.
- Flags stakeholders whose interests compete and suggests alignment strategies.
- Saves the stakeholder map as a markdown document.
Install the skill from the ZIP download
Download the ZIP for the stakeholder-map skill from this page and unzip it. The skill is a single file, SKILL.md, so the unzipped folder should contain that file. Then place the folder in one of two locations, depending on how you want to use it.
For personal use across all your projects, put it in your user skills folder. For a single project, put it in that project's skills folder so the skill travels with the repository. Claude apps users can instead upload the ZIP under Settings → Capabilities → Skills.
- Personal: move the unzipped stakeholder-map folder into ~/.claude/skills/
- Project-only: move it into .claude/skills/ inside your project folder
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
~/.claude/skills/stakeholder-map/SKILL.mdTrigger the skill with a natural request
You do not need a special command. The skill's description covers situations such as managing stakeholders, preparing for a launch, aligning cross-functional teams and planning stakeholder engagement. Describe your situation in plain language and mention the initiative by name, because the skill fills in the initiative from your request.
If you have files such as an org chart, a project brief or a team roster, attach or point the agent to them. The skill tells the agent to read those first. If you only describe the product or initiative, the agent infers likely stakeholders from that description.
- "Build a stakeholder map for the Q3 checkout redesign launch."
- "Map stakeholders for our new billing feature and suggest a communication plan."
- "Our engineering and sales teams disagree on the launch date. Map the stakeholders and flag the conflict."
- "Here is our org chart and project brief. Who should I manage closely for this migration?"
Work through the output
Read the grid first. Check that the Power and Interest ratings match what you know about each person, since the skill makes its ratings from the context you gave it. Then review the communication plan table, which is the part you will act on.
Treat the conflict flags as a starting point for conversation rather than a verdict. The saved markdown file can be edited like any other document, so correct any rating or add people the agent missed.
- Confirm each Power and Interest rating against your own knowledge.
- Add missing stakeholders such as regulators, partners or a specific customer group.
- Adjust frequencies and channels to match how your team actually works.
- Keep the saved file in your project so you can update it as the initiative changes.
Safety, privacy and what the skill needs
The skill requires nothing beyond the agent itself. It runs no scripts and uses no network access, according to its listing. Its only file is SKILL.md.
The output is a judgement about named people, and it may be inaccurate. Do not share the map widely if it contains political or personal assessments of individuals, and do not use it for sensitive personnel decisions. The skill applies a general framework and does not check legal or regulatory obligations, so use a separate review for those.
- No scripts are run and no network use is declared.
- Keep maps of named individuals within the team that needs them.
- Verify any legal or regulatory stakeholder duties yourself.
Tips for better maps
The quality of the map depends mostly on the context you give. Name the initiative, its goal and its timeline, and attach real documents if you have them. A request that includes the launch date and the teams involved will produce a more specific plan than a one-line request.
Use the skill again as the project changes. Stakeholder power and interest shift when priorities move or when a new executive joins, so rerunning the map keeps the communication plan current.
- State the goal, timeline and teams in your first message.
- Ask for conflict flags explicitly when teams have different priorities.
- Rerun the skill at each major milestone and compare the saved files.
What people use it for
- Preparing a product launch by identifying which executives need 1:1s and which teams only need demos.
- Coordinating engineering, sales and support during a cross-functional release.
- Onboarding onto an unfamiliar initiative and getting a quick structured view of who has influence.
- Spotting competing goals between teams and drafting alignment strategies before a decision meeting.
Frequently asked questions
How do I install the stakeholder-map skill?
Download the ZIP from this page and unzip it. Move the stakeholder-map folder into ~/.claude/skills/ for personal use or into .claude/skills/ inside a project. In the Claude apps, you can upload the ZIP under Settings → Capabilities → Skills.
What does the stakeholder map skill require?
The skill lists no requirements. It runs no scripts and uses no network access. It consists of a single SKILL.md file and works through your agent.
Is the stakeholder-map skill free to use?
The skill is published under the MIT licence, as stated on this page. Check the repository licence file for the full terms before reusing it.
What is the difference between Manage Closely and Keep Satisfied?
Both groups have high power. Manage Closely stakeholders also have high interest, so the skill recommends regular 1:1s and early involvement in decisions. Keep Satisfied stakeholders get periodic updates and are escalated to only for critical issues.
Can this skill replace a legal or regulatory stakeholder review?
No. The skill applies a general power and interest framework and does not check legal or regulatory obligations. Use a dedicated legal review for those requirements.
When should I not use this skill?
Avoid it for sensitive personnel or political assessments of named people, and for very small projects with only one or two people, where a grid adds little value.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits product managers preparing a launch, project leads coordinating several teams and anyone new to an initiative who wants a quick, structured view of who matters. It is a practical starting point that you should check and edit against your own knowledge. If you need legal or regulatory stakeholder analysis, or a judgement about individuals to share widely, pick a dedicated process instead.
Download the skill