Executive Summary Creator - Auto-activating skill for Enterprise Workflows. Triggers on: executive summary creator, executive summary creator Part of the Enterprise Workflows skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill executive-summary-creatorOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is essentially a placeholder with no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would say, and provides no guidance on when to use the skill. The redundant trigger term and vague category reference offer no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Condenses lengthy reports into concise executive summaries, extracts key findings, highlights action items, and formats for C-suite audiences.'
Include a 'Use when...' clause with natural trigger terms: 'Use when user asks to summarize reports, create briefs, extract key points, write TL;DR, or prepare documents for executives.'
Specify the input types and contexts to distinguish from general summarization: 'Works with business reports, meeting notes, quarterly reviews, and strategic documents.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only names the skill ('Executive Summary Creator') without describing what it actually does (e.g., condenses reports, extracts key points, generates bullet summaries). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no capabilities listed) and 'when should Claude use it' (no explicit use-case guidance). The 'Triggers on' line just repeats the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('executive summary creator' listed twice) and represent the skill name rather than natural user phrases. Missing terms users would actually say like 'summarize', 'key points', 'brief overview', 'TL;DR', or 'condense report'. | 1 / 3 |
Distinctiveness Conflict Risk | Very generic - 'Enterprise Workflows' is broad and 'executive summary' could overlap with any summarization, report generation, or document processing skill. No distinguishing features or specific file types/contexts mentioned. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no substantive content. It describes what an executive summary creator skill would do without providing any actual guidance, examples, templates, or workflows for creating executive summaries. The content is entirely meta-description rather than actionable instruction.
Suggestions
Add a concrete executive summary template with sections (e.g., Key Findings, Recommendations, Financial Impact, Timeline) and examples of good vs. poor summaries
Include a clear workflow: 1) Identify source document type, 2) Extract key metrics/decisions, 3) Structure summary by audience, 4) Validate completeness against checklist
Provide specific examples showing input documents and their corresponding executive summaries with different lengths (1-page, half-page, bullet-point formats)
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual instructions Claude can execute
| 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 meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | The skill contains zero concrete guidance, no code examples, no specific commands, and no actual instructions on how to create an executive summary. It only describes what it claims to do without showing how. | 1 / 3 |
Workflow Clarity | There is no workflow defined at all. The skill mentions 'step-by-step guidance' but provides none. No sequence, no validation steps, no actual process for creating executive summaries. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague marketing-style text with no structure pointing to detailed materials, no references to other files, and no organized sections with actual content. | 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 | |
Table of Contents
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.