agentleFS
Sign inStart free
itseffiitseffi/agentic-os/.agents/skills/power-map/SKILL.md

power-map

Skill114 starsChanged 10 months agoMITView on GitHub

Map stakeholders by power and interest to plan engagement strategy. Use when starting multi-stakeholder initiatives.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When starting an initiative that involves multiple stakeholders.

    line 12
  2. Distinctive:

    Place each stakeholder in the 2x2 based on:

    line 42
  3. Distinctive:

    Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

    line 80

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Stakeholder Power-Interest Map

Map stakeholders by power and interest to plan engagement strategy.

When to Use

When starting an initiative that involves multiple stakeholders.

The Framework

Power-Interest Grid

Low InterestHigh Interest
High PowerKeep SatisfiedManage Closely
Low PowerMonitorKeep Informed

Influence Pyramid

Beyond formal power, map informal influence:

  • Top tier: Decision makers, budget holders
  • Middle tier: Gatekeepers, team leads
  • Base tier: Super-connectors, exec assistants

The Process

1. List Stakeholders

Gather:

  • Names and roles
  • Organizational position
  • Known relationships
  • Allies and blockers

2. Map to Grid

Place each stakeholder in the 2x2 based on:

  • Power: Formal authority, budget control, veto ability
  • Interest: How much they care about this initiative

3. Build Influence Pyramid

Identify informal power:

  • Who controls access?
  • Who influences opinion?
  • Who connects people?

4. Profile High-Power Stakeholders

For each, document:

  • Goals and success metrics
  • Likely concerns (political, operational, reputational)
  • Preferred communication style
  • Political risks for you

5. Create Engagement Plan

For each high-power stakeholder:

  • Cadence and channel
  • Format and owner
  • Key message (tied to their priorities)
  • Quick win to offer
  • Fallback if they resist

Output

  • Power-Interest matrix with names
  • Influence pyramid with rationale
  • High-power profiles table
  • Engagement plan table
  • Top 3 political pitfalls to avoid

When Not to Use

Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free