CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

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.

The body is a well-structured, highly actionable interactive skill with a clear multi-step workflow and clean reference signaling. Its main limitation is conciseness: several prose sections explain stakes and rationales that assume less of Claude's intelligence than warranted.

Suggestions

Tighten Key Concepts and Common Pitfalls by cutting rationale restating broadly-known ideas (e.g., why one-size-fits-all engagement fails) and keeping only the skill-specific framing.

Consider moving the two full worked sample flows into a separate EXAMPLES.md reference to reduce inline length while preserving the actionability.

DimensionReasoningScore

Conciseness

The body is mostly purposeful but runs long; sections like Key Concepts and Common Pitfalls include framing prose (e.g., why generic engagement fails) that partly restates what Claude knows and could be tightened, matching the level-2 anchor.

2 / 3

Actionability

It provides copy-paste-ready scripted questions with numbered options, a concrete synthesis template, fully worked sample conversation flows, and explicit edge-case handling — concrete and executable guidance for an instruction-only skill.

3 / 3

Workflow Clarity

The guided conversation is clearly sequenced (Opening → Q1 profile → Q2 power/impact → Q3 context → synthesis → numbered approaches → specific plan) with a synthesis checkpoint after all three answers, and edge cases handled.

3 / 3

Progressive Disclosure

No bundle files exist; the skill is a single self-contained file with well-organized sections and a References section pointing one level deep to sibling skills and one external URL, all clearly signaled.

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.

The description is concise, uses third person, and cleanly pairs a clear capability statement with an explicit "Use when" trigger clause. Its only weakness is specificity: it names a single action rather than enumerating several concrete engagement actions.

Suggestions

Expand the action clause to list concrete engagement outputs (e.g., 'frame the key message, pick the medium and cadence, and commit a named next action') to lift specificity toward level 3.

DimensionReasoningScore

Specificity

It names the domain and a concrete action — "Plan engagement for a specific stakeholder" — but lists only one primary action rather than multiple specific concrete operations, so it falls short of the level-3 anchor.

2 / 3

Completeness

It explicitly answers both what ("Plan engagement for a specific stakeholder") and when (explicit "Use when..." clause), matching the level-3 anchor for both.

3 / 3

Trigger Term Quality

The "Use when preparing an outreach, navigating resistance, or aligning a critical relationship before a key milestone" clause provides natural terms a user would say (outreach, resistance, aligning a relationship, key milestone).

3 / 3

Distinctiveness Conflict Risk

Per-stakeholder engagement planning is a clear niche with distinct triggers (outreach, resistance, pre-milestone alignment), unlikely to fire for unrelated skills.

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.