CtrlK
BlogDocsLog inGet started
Tessl Logo

stakeholder-identification

Map every stakeholder before engaging anyone. Use when launching an initiative, scoping discovery, or building an engagement plan from scratch.

63

Quality

76%

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-identification/SKILL.md
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.

The body is a well-structured, actionable methodology with a strong worked example and clearly sequenced checkpointed steps, though it carries some motivational padding that slightly reduces token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient but includes motivational rationale ("Most PM stakeholder lists are written from memory in five minutes...") and persuasive padding that could be tightened without losing instruction, matching the mostly-efficient-but-could-be-tightened anchor.

2 / 3

Actionability

It provides concrete, specific guidance — defined R/P/D tags, exact bias-check questions, a 4-6 minute timing, and a full worked example with tagged stakeholders — and as an instruction-only skill it is complete with no missing key details, matching the concrete-specific-examples anchor.

3 / 3

Workflow Clarity

Steps 1-6 are clearly sequenced with explicit checkpoint steps (the equity lens in Step 4 and bias check in Step 5) acting as quality gates, matching the clear-sequence-with-explicit-validation anchor; no destructive/batch cap applies.

3 / 3

Progressive Disclosure

Content is organized into clear sections (Purpose, Input, Key Concepts, Application, Examples, Common Pitfalls, References) with one-level-deep, clearly signaled references and no nested or monolithic structure, matching the well-organized overview anchor.

3 / 3

Total

11

/

12

Passed

Description

67%

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

The description is concise and clearly answers both what and when with an explicit trigger clause, but it relies on a single action verb and omits the most natural "stakeholder" phrasings, leaving it somewhat generic relative to sibling skills.

Suggestions

Expand the action list beyond "Map" to concrete sub-actions (e.g., brainstorm, categorize as Allies/Audiences/Influencers, apply R/P/D marking, equity check) to reach the specificity anchor 3.

Add natural trigger phrasings users would actually say, such as "identify stakeholders," "stakeholder list," or "who are the stakeholders for this initiative," to improve trigger-term coverage.

Sharpen distinctiveness from stakeholder-mapping by foregrounding the identification-vs-prioritization framing directly in the description (e.g., "name every stakeholder before prioritizing them").

DimensionReasoningScore

Specificity

"Map every stakeholder" is a concrete action, but the description names a single action rather than "multiple specific concrete actions," matching the anchor that names a domain and some actions without being comprehensive.

2 / 3

Completeness

It clearly answers both what ("Map every stakeholder before engaging anyone") and when with an explicit "Use when..." trigger clause, matching the anchor for explicit triggers on both dimensions.

3 / 3

Trigger Term Quality

"Use when launching an initiative, scoping discovery, or building an engagement plan" provides relevant situational triggers, but the most natural user phrasings ("identify stakeholders," "stakeholder list," "who are the stakeholders") are missing from the trigger clause.

2 / 3

Distinctiveness Conflict Risk

The triggers (initiative, discovery, engagement plan) are somewhat broad PM situations and the skill overlaps thematically with a sibling stakeholder-mapping skill, so it could still overlap with similar skills despite being somewhat specific.

2 / 3

Total

9

/

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.