CtrlK
BlogDocsLog inGet started
Tessl Logo

stakeholder-mapping

Prioritize stakeholders using two complementary grids. Use when setting engagement strategy and surfacing whose voice needs elevating after stakeholder identification.

63

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/stakeholder-mapping/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured, actionable methodology skill with a clear five-step workflow and a strong worked example. Its main weakness is moderate verbosity from repeated rationale and the 'use both grids' message restated across multiple sections.

Suggestions

Consolidate the 'run both grids, not one' rationale so it appears once (e.g., in Purpose) instead of being restated in Key Concepts and Common Pitfalls.

Trim illustrative rationale paragraphs (e.g., 'Running only the first grid optimizes for managing relationships with the powerful') to the essential methodological point.

Add an explicit verification checkpoint in Step 3 — e.g., 'confirm each stakeholder appears on both grids and flag any placement you are unsure of' — to strengthen the feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly efficient and the methodology is legitimate skill content, but the 'run both grids, not one' message is repeated across Purpose, Key Concepts ('Paired Variables'), and Common Pitfalls, and rationale paragraphs like 'Running only the first grid optimizes for managing relationships with the powerful' add padding that could be tightened.

3 / 5

Actionability

The Application section gives concrete per-quadrant actions (co-design sessions, weekly touchpoints, executive briefings), explicit comparison questions, specific migration moves, and a fully worked example — actionable guidance with only minor directional remnants like 'design 1:1 engagement to address those concerns'.

4 / 5

Workflow Clarity

Five clearly sequenced steps (run Power × Interest, run Impact × Power, compare, plan migration, feed into planning) with the comparison step acting as a checkpoint; no destructive/batch validation cap applies, though an explicit verification of placement consistency is not called out.

4 / 5

Progressive Disclosure

Well-organized sections (Purpose, Input, Key Concepts, Application, Examples, Pitfalls, References) with clearly signaled, one-level-deep references to sibling skills; no bundle files exist so the body is self-contained, but nothing is split into separate files, keeping it just short of the top anchor.

4 / 5

Total

15

/

20

Passed

Description

83%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, third-person description that explicitly pairs a concrete 'what' with a specific 'when' trigger clause. It distinguishes itself via the dual-grid framing, with only minor gaps in enumerated actions and trigger synonyms.

DimensionReasoningScore

Specificity

Names several concrete actions — 'Prioritize stakeholders using two complementary grids', 'setting engagement strategy', 'surfacing whose voice needs elevating' — but does not enumerate the two grids (Power × Interest, Impact × Power), leaving a minor coverage gap rather than comprehensive listing.

4 / 5

Completeness

It explicitly states both what ('Prioritize stakeholders using two complementary grids') and when ('Use when setting engagement strategy and surfacing whose voice needs elevating after stakeholder identification') with concrete trigger conditions, matching the highest anchor.

5 / 5

Trigger Term Quality

Natural PM-facing phrases like 'prioritize stakeholders', 'setting engagement strategy', and 'whose voice needs elevating' are present, but common synonyms such as 'stakeholder mapping' or 'stakeholder analysis' are absent.

4 / 5

Distinctiveness Conflict Risk

The 'two complementary grids' framing plus voice-elevation trigger carves a clear niche, but it sits within a stakeholder-comms family with closely related sibling skills, creating minor overlap risk.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 4 suspicious

Warning

Total

14

/

16

Passed

Repository
deanpeters/Product-Manager-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.