stakeholder-update
Write a weekly stakeholder update on a core pillar or initiative — metrics, bets in progress, customer quotes, and highlights. Use when you need to keep leadership and cross-functional partners informed on what's shipping and what's moving.
67
60%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./execution-skills/skills/stakeholder-update/SKILL.mdQuality
Discovery
85%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 is a strong description that clearly defines both the output (weekly stakeholder update with specific components) and the trigger context (keeping leadership informed). The main weakness is that trigger terms could be broader to capture more natural user phrasings like 'status report' or 'progress update'. Minor note: the 'Use when' clause uses second person ('you need') which slightly deviates from the third-person voice guideline but doesn't significantly harm clarity.
Suggestions
Expand trigger terms to include common synonyms users might say: 'status report', 'progress update', 'executive summary', 'weekly recap', or 'team update'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions/components: metrics, bets in progress, customer quotes, and highlights. Also specifies the output format (weekly stakeholder update) and the audience (leadership and cross-functional partners). | 3 / 3 |
Completeness | Clearly answers both what ('Write a weekly stakeholder update... metrics, bets in progress, customer quotes, and highlights') and when ('Use when you need to keep leadership and cross-functional partners informed on what's shipping and what's moving'). | 3 / 3 |
Trigger Term Quality | Includes some natural keywords like 'stakeholder update', 'metrics', 'leadership', 'shipping', but misses common variations users might say such as 'status report', 'weekly update email', 'progress report', 'executive summary', or 'team update'. | 2 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche — weekly stakeholder updates with specific components (metrics, bets, customer quotes). This is distinct enough to avoid confusion with general writing skills or other reporting skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable template structure for weekly stakeholder updates with good section definitions and one concrete metric example. However, it is significantly over-explained for Claude's capabilities — much of the content describes basic communication principles and product leadership norms that Claude already knows. It would benefit greatly from trimming the explanatory prose, adding a complete before/after example, and including a validation checkpoint.
Suggestions
Cut the preamble and rules that explain basic communication principles Claude already knows (e.g., 'skimmable above all', 'honest over polished', 'keep it energetic') — reduce to just the structural template and format-specific conventions.
Add one complete input/output example showing raw messy context transformed into a finished update, so Claude can pattern-match on the expected transformation.
Add a validation step after generation: 'Verify all metrics match source data, customer quotes are accurately attributed, and no metric movements are stated without directional context.'
Link to or properly reference the 'daily-brief' and 'weekly-brief' skills mentioned in Tips, or remove the references if they don't exist in the bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is very verbose, explaining concepts Claude already knows (what a stakeholder update is, why skimmability matters, what 'honest over polished' means). The entire prompt template is padded with explanations of basic communication principles. The preamble ('You own a pillar...') and many of the rules are things Claude inherently understands. | 1 / 3 |
Actionability | The skill provides a concrete structure and formatting examples (e.g., the WAU metric example), which is helpful. However, it's essentially a prompt template with placeholder variables rather than executable guidance — there are no complete input/output examples showing raw context transformed into a finished update. | 2 / 3 |
Workflow Clarity | The update structure (Metrics → Bets → Customer Signal → Highlights) is clearly sequenced, but there's no validation or review step. For a communication artifact going to leadership, there should be a checkpoint like 'review for accuracy of metrics' or 'verify customer quotes are attributed correctly' before sending. | 2 / 3 |
Progressive Disclosure | The Tips section references 'daily-brief' and 'weekly-brief' skills but doesn't link to them. The content is monolithic — the detailed prompt template, rules, and tips are all inline. The rules and detailed section guidance could be separated into a reference file, with SKILL.md serving as a concise overview. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- amplitude/builder-skills
- Commit
221ffaa
- 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.