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.
36
Quality
3%
Does it follow best practices?
Impact
99%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/stakeholder-communication-template/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
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 meaningful guidance on when Claude should select it. The redundant trigger terms and lack of concrete capabilities make this description nearly useless for skill selection.
Suggestions
Add specific actions the skill performs (e.g., 'Generates formatted stakeholder updates, creates executive summaries, drafts status reports for project sponsors')
Add a 'Use when...' clause with diverse trigger scenarios (e.g., 'Use when the user needs to communicate project status, prepare executive briefings, or draft updates for stakeholders, sponsors, or leadership')
Include natural keyword variations users might say: 'status update', 'executive summary', 'project communication', 'sponsor update', 'leadership briefing'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Stakeholder Communication Template') without describing any concrete actions. There are no verbs indicating what the skill actually does - no 'creates', 'generates', 'formats', or similar action words. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and the 'when' guidance is just a repeated trigger phrase rather than meaningful context. No 'Use when...' clause or equivalent explicit trigger guidance exists. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant (same phrase repeated twice: 'stakeholder communication template') and overly specific. Missing natural variations users might say like 'stakeholder update', 'executive summary', 'status report', 'communication plan', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'stakeholder communication template' is fairly specific and unlikely to conflict with unrelated skills, but without describing what it actually does, it could overlap with other communication or template-related skills in the Enterprise Workflows category. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is entirely meta-content describing what a skill would do rather than providing any actual stakeholder communication templates, examples, or guidance. It contains no actionable information—no communication templates, no example messages, no formatting guidelines, and no concrete steps for stakeholder communication tasks.
Suggestions
Add actual stakeholder communication templates (e.g., status update, escalation, project kickoff) with concrete examples and fill-in sections
Include specific guidance on communication structure: audience analysis, key message framing, tone guidelines for different stakeholder types
Provide executable examples showing input (project context) and output (formatted communication) for at least 2-3 common scenarios
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with direct, actionable instructions
| 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 explained. | 1 / 3 |
Actionability | There is zero concrete guidance, no code, no commands, no templates, and no actual stakeholder communication examples. The skill describes what it does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or processes for creating stakeholder communications. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to actual content. There are no references to templates, examples, or detailed materials that would contain the real value. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.