report-generator
Report Generator - Auto-activating skill for Business Automation. Triggers on: report generator, report generator Part of the Business Automation skill category.
30
0%
Does it follow best practices?
Impact
81%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/report-generator/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 placeholder with no substantive content. It fails on all dimensions: it provides no concrete actions, no natural trigger terms beyond the skill name repeated, no explicit 'when to use' guidance, and is so generic it would conflict with many other skills. It reads like auto-generated boilerplate rather than a crafted skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates formatted business reports from data sources including sales summaries, financial statements, and KPI dashboards.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a report, generate a summary, build a business dashboard, or produce analytics from data.'
Remove the duplicate trigger term 'report generator' and expand with varied natural language terms users would actually say, such as 'create report', 'weekly summary', 'business analytics', 'generate PDF report'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. 'Report Generator' is a label, not a description of capabilities. There is no mention of what kind of reports, what data sources, or what specific operations are performed. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. The description only states it's a 'Report Generator' in the 'Business Automation' category with no explicit trigger guidance or functional detail. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'report generator' repeated twice. This misses natural variations users would say like 'generate a report', 'create report', 'summary report', 'analytics', 'dashboard', etc. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic — 'report generator' and 'Business Automation' could overlap with virtually any data analysis, dashboard, spreadsheet, or document generation skill. There is nothing to distinguish this from other reporting or business-related skills. | 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—a placeholder that describes what a report generator skill would do without actually providing any instructions, code, examples, or workflows. It contains no actionable content whatsoever and would provide zero value to Claude when attempting to help a user with report generation tasks.
Suggestions
Replace the meta-description with actual report generation instructions: include concrete code examples (e.g., generating PDF/Excel reports using Python libraries like openpyxl, reportlab, or pandas) with executable, copy-paste-ready snippets.
Define a clear workflow for report generation: e.g., 1) gather data source, 2) transform/aggregate data, 3) generate report in target format, 4) validate output—with specific commands or code at each step.
Add concrete examples showing input data and expected report output, including at least one complete end-to-end example.
Remove all self-referential content ('This skill activates when...', 'Example Triggers', 'Related Skills') which belongs in frontmatter metadata, not in the skill body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or actionable content. Every token is wasted on describing the skill rather than teaching anything. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific steps, no examples of report generation. Phrases like 'Provides step-by-step guidance' and 'Generates production-ready code' are claims about the skill, not actual guidance or code. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints—just vague bullet points describing capabilities without any process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to detailed materials, no references to other files, and no meaningful organization of content for discovery. | 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.