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.
34
0%
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
0%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 critically underdeveloped. It provides no concrete actions, no meaningful trigger terms, no explicit usage guidance, and no distinguishing details. It reads as a placeholder rather than a functional skill description that Claude could use to select the right skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates stakeholder status reports, drafts executive summaries, creates project update emails, and formats communication briefs.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks for stakeholder updates, project status communications, executive briefings, or needs to draft messages for project sponsors.'
Remove the duplicate trigger term and expand with natural keyword variations users would actually say, such as 'status update', 'project communication', 'executive summary', 'stakeholder email', 'progress report'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names no concrete actions whatsoever. It only says 'Stakeholder Communication Template' and 'Auto-activating skill for Enterprise Workflows' without describing what the skill actually does (e.g., drafts emails, creates reports, generates status updates). | 1 / 3 |
Completeness | Neither the 'what does this do' nor the 'when should Claude use it' questions are meaningfully answered. There is no explanation of capabilities and no explicit 'Use when...' clause with actionable triggers. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'stakeholder communication template' repeated twice. There are no natural keyword variations a user might say, such as 'status update', 'executive summary', 'project report', 'stakeholder email', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'Enterprise Workflows' and 'stakeholder communication' could overlap with many other skills involving communication, templates, or enterprise tasks. There is nothing to distinguish this skill's niche. | 1 / 3 |
Total | 4 / 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 an empty shell—it contains only boilerplate meta-descriptions about what it would do without any actual content. There are no templates, no examples, no concrete instructions, and no actionable guidance for stakeholder communication. It fails on every dimension because it describes a skill rather than being one.
Suggestions
Add actual stakeholder communication templates (e.g., project status update, escalation notice, executive summary) with concrete examples showing input context and generated output.
Include a clear workflow: e.g., 1) Identify audience and communication type, 2) Select template, 3) Fill in project-specific details, 4) Review tone/formality, 5) Validate completeness against checklist.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers', 'Capabilities') that merely restate the skill name and replace them with actionable content.
Add specific examples with sample inputs and expected outputs, such as a status report template with placeholders and a completed example.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill supposedly does without ever actually doing it. Every section restates the same vague concept ('stakeholder communication template') without adding any substantive information. | 1 / 3 |
Actionability | There is zero concrete guidance—no templates, no examples, no code, no specific steps, no actual communication formats. The skill claims to provide 'step-by-step guidance' and 'production-ready code' but delivers neither. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The content is purely descriptive metadata about what the skill would theoretically do. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to detailed materials, no linked resources, and no structured navigation to deeper content. | 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
c8a915c
- 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.