CtrlK
BlogDocsLog inGet started
Tessl Logo

stakeholder-map

Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, well-structured instructional skill that gives Claude concrete templates and a clear sequence for producing a stakeholder map and communication plan. Adding a worked example and a completeness validation step would lift it to fully executable.

Suggestions

Include one brief worked example of a filled communication-plan table so Claude has a concrete template to mirror.

Add an explicit validation step (e.g., 'Confirm every identified stakeholder appears in the plan and each conflict has an alignment strategy') before saving.

Consider adding a few natural-language trigger synonyms like 'stakeholder analysis' to broaden when the skill fires.

DimensionReasoningScore

Conciseness

Lean and efficient — defines the grid, table schemas, and per-quadrant recommendations without re-explaining stakeholder/power/interest concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Provides concrete table structures (the Power×Interest grid and the communication-plan column schema) and specific per-quadrant guidance, but lacks a worked example of a filled communication plan.

4 / 5

Workflow Clarity

Six clearly sequenced, well-defined steps with an explicit output instruction, but no validation checkpoint to confirm the map is complete or internally consistent.

4 / 5

Progressive Disclosure

A short, well-organized single file with clear sections (Context, Instructions, Further Reading) and no need for external bundle references, satisfying the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that pairs three concrete capabilities with an explicit, multi-trigger 'Use when' clause tailored to stakeholder engagement scenarios. The only gap is slightly formal trigger phrasing lacking a few natural synonyms.

DimensionReasoningScore

Specificity

Lists three comprehensive concrete actions ('Build a stakeholder map using a power/interest grid', 'identify communication strategies per quadrant', 'generate a communication plan'), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both what (build map, identify strategies, generate plan) and when ('Use when managing stakeholders, preparing for a launch...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural triggers ('managing stakeholders', 'preparing for a launch', 'aligning cross-functional teams', 'planning stakeholder engagement') but missing common synonyms like 'stakeholder analysis' and casual phrasings users would say.

4 / 5

Distinctiveness Conflict Risk

Clear niche of stakeholder mapping via power/interest grid with triggers specific to stakeholder engagement, minimal overlap with unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
phuryn/pm-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.