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.

70

Quality

87%

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

85%

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

A well-structured, highly actionable instruction skill with a clear sequenced workflow and a worked example. The only real weakness is conciseness — the Purpose section and several framing passages could be trimmed without losing clarity.

Suggestions

Trim the Purpose section to avoid restating the description and the Key Concepts framing; let the Application steps carry the method.

Consider moving the full worked Example or the quadrant-by-quadrant Key Concepts into a reference file to shorten the main body while keeping it one click away.

DimensionReasoningScore

Conciseness

Almost all content is method-specific knowledge rather than padding about concepts Claude already knows, but the Purpose section restates the description and several passages ('Running only the first grid optimizes for managing relationships with the powerful...') are discursive and could be tightened.

2 / 3

Actionability

Step 1-5 give concrete assessment questions, per-quadrant engagement strategies, explicit migration actions (e.g. 'Q1 -> Q2: Actively recruit them into advisory processes, discovery research, and requirements review'), plus a fully worked example — copy-ready guidance for an instruction-only skill.

3 / 3

Workflow Clarity

A clear five-step sequence (run Power x Interest, run Impact x Power, compare for gaps, plan migration, feed into engagement) where the Step 3 comparison acts as the method's built-in validation checkpoint; no destructive/batch step requires an explicit validate-fix-retry loop.

3 / 3

Progressive Disclosure

No bundle files exist; the body is organized into well-delineated sections (Purpose, Input, Key Concepts, Application, Examples, Common Pitfalls, References) with one-level-deep, clearly signaled references to sibling skills and MITRE sources.

3 / 3

Total

11

/

12

Passed

Description

90%

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 with an explicit 'Use when' trigger, natural PM terminology, and a clear niche. Its only weakness is specificity: the actions are stated abstractly and the two grids are referenced but not named.

Suggestions

Name the two grids in the description (e.g., 'Power x Interest and Impact x Power grids') to make the actions concrete rather than abstract.

Optionally surface the headline output ('reveals high-impact, low-power stakeholders you are under-engaging') to sharpen what the skill produces.

DimensionReasoningScore

Specificity

Names the domain and several actions ('Prioritize stakeholders using two complementary grids', 'setting engagement strategy', 'surfacing whose voice needs elevating') but the actions stay abstract and the two grids are not enumerated, so it stops short of listing multiple concrete specific actions.

2 / 3

Completeness

Explicitly answers both: what ('Prioritize stakeholders using two complementary grids') and when ('Use when setting engagement strategy and surfacing whose voice needs elevating after stakeholder identification').

3 / 3

Trigger Term Quality

Natural PM vocabulary a user would actually say is well covered — 'prioritize stakeholders', 'engagement strategy', 'whose voice needs elevating', 'after stakeholder identification'.

3 / 3

Distinctiveness Conflict Risk

Clear niche — dual-grid stakeholder prioritization positioned 'after stakeholder identification' — that is distinguishable from sibling skills and unlikely to trigger for the wrong one.

3 / 3

Total

11

/

12

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.