stakeholder-communication-template
Stakeholder Communication Template - Auto-activating skill for Enterprise Workflows. Triggers on: stakeholder communication template, stakeholder communication template Part of the Enterprise Workflows skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill stakeholder-communication-templateActivation
7%This description is severely underdeveloped, functioning more as a label than a useful skill description. It provides no information about what actions the skill performs, what outputs it produces, or what user requests should trigger it. The redundant trigger terms and lack of concrete capabilities make it nearly useless for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Creates status updates, executive summaries, and progress reports for project stakeholders'
Include a 'Use when...' clause with natural trigger terms like 'update stakeholders', 'project status', 'executive summary', 'progress report', 'team communication'
Remove the redundant trigger term and replace with varied natural language phrases users would actually say when needing this skill
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only names itself as a 'template' and mentions 'auto-activating skill' without describing what it actually does with stakeholder communications. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no explicit use cases beyond the skill name as a trigger). Missing a 'Use when...' clause entirely. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant (same phrase listed twice) and overly specific to the skill name itself rather than natural user language like 'email stakeholders', 'project update', 'status report', or 'communicate with team'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'stakeholder communication' is somewhat specific, the lack of detail about what kind of communications (emails, reports, presentations) or contexts makes it potentially overlap with general writing or communication skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty shell with no actionable content. It describes capabilities it doesn't deliver and provides no templates, examples, or guidance for stakeholder communication. The entire content could be replaced with a single sentence saying 'this skill is not implemented.'
Suggestions
Add actual stakeholder communication templates (e.g., status update template, escalation template, executive summary template) with concrete examples
Include specific guidance on when to use each template type and what information to include in each section
Provide at least one complete example showing input context and the resulting communication output
Remove the meta-description sections (Purpose, When to Use, Capabilities) and replace with actionable content that demonstrates the skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no templates, no examples, no code, no specific steps. The skill describes what it claims to do but never actually shows how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill mentions 'step-by-step guidance' but provides none. There are no sequences, no validation steps, and no actual process to follow. | 1 / 3 |
Progressive Disclosure | The content is a shallow placeholder with no substantive information to organize. There are no references to detailed materials, no examples, and no actual content structure beyond empty section headers. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.