stakeholder-identification

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

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/stakeholder-identification/SKILL.md

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 instruction skill with a clear sequenced workflow and good cross-skill navigation. Its main weakness is moderate verbosity from concept re-explanation across sections, and the lack of a concrete output artifact template slightly limits copy-paste actionability.

Suggestions

De-duplicate the Key Concepts and Application sections: define equity lens and R/P/D once and reference them in the steps rather than restating each.

Add a compact output template (e.g. a markdown table with columns Name | Category | R/P/D | What to learn) so Step 6 produces a concrete, reusable artifact.

Trim the Purpose section's narrative critique of 'five-minute lists' to one or two sentences to reclaim tokens.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but padded in places: the Purpose section repeats the 'five minutes from memory' critique and several 'Key Concepts' entries restate ideas that appear again in the Application steps (e.g. equity lens described twice, R/P/D described twice), which could be tightened.	3 / 5
Actionability	Steps 1-6 give concrete, executable prompts (specific questions to ask, exact R/P/D definitions, what to capture per priority stakeholder) and the Examples section models a full worked list. It is guidance rather than code, but as an instruction-only skill the guidance is actionable; only minor gaps (no explicit output template) keep it from a 5.	4 / 5
Workflow Clarity	A clear 6-step sequence with explicit checkpoints (Step 5 bias check, Step 6 narrowing) and error-recovery framing (pitfalls list). It is not a destructive/batch operation so the validation cap does not apply; it falls just short of 5 because there is no explicit verification that the final list is complete before handing off.	4 / 5
Progressive Disclosure	Well-organized sections (Purpose, Input, Key Concepts, Application, Examples, Pitfalls, References) with clear one-level-deep links to sibling skills (stakeholder-mapping, stakeholder-engagement-advisor, discovery-interview-prep, proto-persona) and named external sources. No bundle files exist to verify, and the body is appropriately self-contained; minor gap is that the bulk of the worked methodology is inlined rather than split, but for this skill that is appropriate.	4 / 5
	Total	15 / 20 Passed

Description

88%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 clearly states both the concrete actions and triggering situations, with a well-defined niche in a stakeholder workflow. Trigger term coverage is good but could incorporate a few more natural user phrasings, and explicit disambiguation from sibling skills would reduce overlap risk.

Suggestions

Add a natural-sounding trigger phrase a PM would actually say, e.g. 'Use when you need to find everyone affected by a decision' or 'Use when preparing the stakeholder section of a PRD'.

Add a brief clause distinguishing this from stakeholder-mapping, e.g. 'Use this before stakeholder-mapping (which prioritizes).' to further reduce conflict risk.

Dimension	Reasoning	Score
Specificity	Maps every stakeholder via concrete actions: brainstorm, categorize (Allies/Audiences/Influencers), R/P/D marking, equity check, narrow to priority targets. Lists multiple specific concrete actions with comprehensive coverage of the workflow.	5 / 5
Completeness	Explicitly answers what ('Map every stakeholder before engaging anyone') and when ('Use when launching an initiative, scoping discovery, or building an engagement plan from scratch') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage with natural trigger phrases ('launching an initiative', 'scoping discovery', 'building an engagement plan from scratch'), though it misses some natural user synonyms like 'who should we talk to' or 'find stakeholders' that the scenarios elsewhere capture.	4 / 5
Distinctiveness Conflict Risk	Clear niche (pre-engagement identification vs. stakeholder-mapping's prioritization) with distinct triggers; minor overlap risk with the closely related stakeholder-mapping skill, which the description does not explicitly disambiguate.	4 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: skills/stakeholder-identification/SKILL.md
Commit: a03af68

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.