CtrlK
BlogDocsLog inGet started
Tessl Logo

stakeholders

Identify people who need to approve, consult on, or be informed about a change or project — use when someone asks who needs to know about a change, who should be looped in, who needs to approve, who should be consulted, who is affected, or needs a RACI for a change, refactor, migration, or decision.

76

Quality

95%

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

88%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 workflow with concrete tool commands, a vetting checklist, and copy-paste output templates. Its main weakness is mild verbosity from duplicated clarification questions and slight overlap between the principles list and the vetting table.

Suggestions

Remove the duplicated clarification questions — keep them only in Phase 1 (or only in the intro) to trim ~4 lines of repetition.

Collapse the 'Core Principles' list into the Phase 3 vetting table, since 'quality over quantity', 'distinguish roles', and 'be skeptical' are already encoded there.

Consider splitting the large output markdown template (lines 77-124) into a referenced file to shorten the SKILL.md body and aid progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly lean and free of concepts Claude already knows, but the clarification questions are repeated (once in the intro, once in Phase 1) and a few principles overlap with the vetting table, leaving minor trimming opportunities.

4 / 5

Actionability

Provides concrete, copy-paste-ready Glean commands with example query strings, a vetting table with explicit criteria, and a full output markdown template covering the common cases.

5 / 5

Workflow Clarity

Clear four-phase sequence with an explicit validation checkpoint (the CRITICAL vetting phase), a self-check question, a vetting checklist table, and recovery paths for edge cases (no stakeholders, too many stakeholders, Glean unavailable).

5 / 5

Progressive Disclosure

Well-organized into clearly headed phases with no deeply nested references and no content that clearly belongs in a separate file; the single-file body is slightly long, which keeps it just shy of a 5.

4 / 5

Total

18

/

20

Passed

Description

100%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.

An exemplary description: concise, third-person, with a clear 'what' and an explicit, trigger-rich 'when' clause. It names concrete role-actions and natural user phrases that map well to how the skill is actually invoked.

DimensionReasoningScore

Specificity

Names the domain (stakeholder identification) and multiple concrete role-actions — 'approve, consult on, or be informed' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (identify people who need to approve/consult/be informed) and 'when' via a clear 'use when someone asks...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Densely packed natural trigger phrases users would actually say — 'who needs to know', 'who should be looped in', 'who needs to approve', 'who should be consulted', 'who is affected', 'needs a RACI' — plus change types (refactor, migration, decision).

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (RACI / stakeholder discovery) with distinctive triggers unlikely to fire for unrelated skills; minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
gleanwork/claude-plugins
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.