stakeholder-engagement-advisor

Plan engagement for a specific stakeholder. Use when preparing an outreach, navigating resistance, or aligning a critical relationship before a key milestone.

Quality

76%

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

Quality

Content

75%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 thorough, highly actionable guided-conversation skill with concrete scripts, diagnostic sequencing, and worked examples. Its main weakness is moderate verbosity in the conceptual and pitfall prose, and it is a single long file with no progressive split beyond sibling-skill references.

Suggestions

Trim motivational justification in Purpose and Key Concepts to declarative statements; assume Claude grasps why one-size-fits-all engagement fails.

Consider moving the two full worked Examples (or the six Common Pitfalls) into a references/ file linked from the body to improve progressive disclosure and reduce token load.

Add an explicit final confirmation step (e.g., 'Before finalizing, restate the next action and confirm it fits the timeline') to close the workflow-clarity validation gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining generic concepts Claude already knows, but the Purpose paragraph, six elaborated Key Concepts, and six paragraph-length Common Pitfalls include motivational prose (e.g., "Generic stakeholder engagement fails because...") that could be tightened, landing at anchor 3 rather than the minor-trim level of anchor 4.	3 / 5
Actionability	It provides copy-paste-ready conversational scripts — the exact opening line, three fully-written numbered questions, a structured synthesis template, edge-case branches, and two complete worked examples covering common cases — which is the instruction-skill equivalent of fully executable guidance.	5 / 5
Workflow Clarity	The guided flow is clearly sequenced (Opening → Q1 → Q2 → Q3 → Synthesis → selection → plan) with diagnostic checkpoints and a selection/refinement loop plus edge-case branching. It stops at anchor 4 because there is no explicit 'confirm the plan fits before finalizing' validation step, and the operation is non-destructive so the anchor-5 validate→fix→retry pattern does not apply.	4 / 5
Progressive Disclosure	Clear section structure (Purpose, Input, Key Concepts, Application, Examples, Pitfalls, References) with well-signaled, one-level-deep references to sibling skills and the MITRE source, and no nested references. It is a single substantial file with no bundle files to split, so it sits at anchor 4 rather than the fully-split, multi-file navigation of anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

78%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 well-constructed description that cleanly answers both what and when with natural trigger phrases in third person. It is slightly under-specified on the range of concrete actions it performs and carries minor overlap risk with adjacent stakeholder skills.

Suggestions

Expand the 'what' to name 2-3 concrete deliverables (e.g., 'frame the key message, pick medium and cadence, and commit to a named next action') to lift specificity toward anchor 4-5.

Add a couple of common synonyms (e.g., 'buy-in', 'sponsor', 'roadblock') to broaden trigger-term coverage.

Add a disambiguating cue (e.g., 'for a single priority stakeholder, not the full list') to reduce overlap with stakeholder-mapping/identification.

Dimension	Reasoning	Score
Specificity	"Plan engagement for a specific stakeholder" names the domain and one concrete action, but does not enumerate the multiple sub-actions the skill actually delivers (message framing, medium/cadence, next-action commitment). It clears anchor 3 (domain + 1-2 concrete actions) but stops short of the several-action coverage of anchor 4.	3 / 5
Completeness	It explicitly states what ("Plan engagement for a specific stakeholder") and when ("Use when preparing an outreach, navigating resistance, or aligning a critical relationship before a key milestone") with concrete trigger phrases, matching the anchor-5 example structure exactly.	5 / 5
Trigger Term Quality	"preparing an outreach, navigating resistance, or aligning a critical relationship before a key milestone" supplies several natural phrases a user would say, plus "stakeholder"/"engagement". Good keyword coverage with concrete trigger scenarios, but lacks synonym breadth (e.g., "buy-in", "sponsor", "roadblock") that would reach anchor 5.	4 / 5
Distinctiveness Conflict Risk	The per-stakeholder engagement framing and resistance/outreach triggers carve a mostly-distinct niche from sibling skills, but "stakeholder" broadly overlaps with stakeholder-identification and stakeholder-mapping, leaving minor conflict risk with closely related skills rather than the minimal risk of anchor 5.	4 / 5
	Total	16 / 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-engagement-advisor/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.