Skip to content
SkillModel-led533 tokens in use

stakeholder-map

Map stakeholders on a power and interest grid and get a communication plan with frequency, channel and key message for each.

28,201 stars on the repository MIT Licensephuryn/pm-skills · pm-execution/skills/stakeholder-map
claude plugin install pm-execution@pm-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing stakeholder-map costs

51tokens idle
533tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure23/25
  • Examples0/15
  • Output7/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity80
  • Maintenance76
  • Community60
  • Maturity32
  • Momentum40

stakeholder-map lists the people and groups around an initiative, rates each as high or low on power and on interest, and places them in a four-quadrant grid: Manage Closely, Keep Satisfied, Keep Informed and Monitor.

For every quadrant it recommends how often to communicate, in what format, with which key messages, and what goes wrong if the group is neglected. It also flags stakeholders whose interests conflict and suggests how to align them.

What You Get

  • A list of stakeholders classified by power and interest
  • The Power by Interest grid with a strategy per quadrant
  • A communication plan table with role, strategy, frequency, channel and key message
  • Neglect risks for each group
  • A list of conflicting interests with alignment suggestions
  • A markdown document

Common Use Cases

  • Preparing stakeholder engagement for a launch
  • Aligning cross-functional teams on a platform migration
  • Deciding who gets a weekly update and who gets a monthly one

What Makes It Unique

It goes beyond the grid to a full communication plan table, and it names conflicts between stakeholders. For a large Keep Informed group it suggests an anonymous live Q&A through the live-qa skill so people can raise concerns they would not voice in a meeting.

Under The Hood

The skill is one SKILL.md of instructions with no scripts. The agent reads any org charts, project briefs or rosters you provide, works through the classification step by step and saves the stakeholder map as a markdown file. It does not call external services.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers