executive-summary-creator
Executive Summary Creator - Auto-activating skill for Enterprise Workflows. Triggers on: executive summary creator, executive summary creator Part of the Enterprise Workflows skill category.
34
0%
Does it follow best practices?
Impact
99%
1.02xAverage 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/executive-summary-creator/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 essentially a skill name repeated as metadata with no substantive content. It lacks concrete actions, natural trigger terms, explicit usage guidance, and any distinguishing details. It would be nearly useless for Claude to select this skill appropriately from a pool of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Condenses lengthy reports, documents, or meeting notes into concise executive summaries with key findings, recommendations, and action items.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to summarize a report, create an executive brief, extract key takeaways, or condense a document for leadership review.'
Include natural keyword variations users might say, such as 'summary', 'summarize', 'executive brief', 'key points', 'TL;DR', 'condense', 'overview for leadership'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the skill ('Executive Summary Creator') but provides no concrete actions. There is no mention of what it actually does—no verbs like 'generates', 'condenses', 'extracts key points', etc. It is essentially just a label repeated with metadata. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent guidance. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'executive summary creator' repeated twice. It misses natural user phrases like 'summarize this report', 'create a summary', 'executive brief', 'key takeaways', 'TL;DR', or 'condense this document'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any summarization, document processing, or writing skill. 'Enterprise Workflows' is a broad category that provides no meaningful differentiation. | 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 placeholder that provides no actionable content whatsoever. It repeatedly names the skill ('executive summary creator') without ever defining what an executive summary should contain, how to create one, what format to use, or any concrete guidance. It fails on every dimension of the rubric.
Suggestions
Add a concrete executive summary template with sections (e.g., Problem Statement, Key Findings, Recommendations, Next Steps) and example content for each section.
Provide at least one complete input-to-output example showing a source document/brief and the resulting executive summary.
Define a clear workflow: e.g., 1) Identify audience and purpose, 2) Extract key points from source material, 3) Draft summary following template, 4) Validate against length/tone constraints.
Remove all generic boilerplate sections (When to Use, Example Triggers, Capabilities) and replace with actual instructional content that teaches Claude how to produce high-quality executive summaries.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'executive summary creator' excessively, and provides zero substantive information about how to actually create executive summaries. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no examples of input/output, no templates, no specific steps. Every section is vague and abstract, describing capabilities without demonstrating them. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There is no sequence, no validation, and no process to follow. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic placeholder with no meaningful structure. There are no references to detailed files, no layered content, and the section headers contain only generic boilerplate rather than organized, navigable information. | 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.