report-generator
Report Generator - Auto-activating skill for Business Automation. Triggers on: report generator, report generator Part of the Business Automation skill category.
30
Quality
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 repeats the skill name as trigger terms, provides no concrete actions or capabilities, and lacks any guidance on when to use it. The description would be indistinguishable from dozens of potential business-related skills.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Generates sales reports, financial summaries, and performance dashboards from spreadsheet data')
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when user asks to create reports, summarize data, build dashboards, or generate business analytics')
Specify the types of reports, data sources, or output formats to distinguish this from other document or data skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Report Generator' without describing any concrete actions. It doesn't explain what kind of reports, what data sources, or what the skill actually does beyond the generic label. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or explicit guidance on when Claude should select this skill. The 'Triggers on' line is redundant and uninformative. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'report generator' repeated twice. This misses natural variations users would say like 'create report', 'generate summary', 'build report', 'analytics', 'dashboard', or specific report types. | 1 / 3 |
Distinctiveness Conflict Risk | 'Report Generator' and 'Business Automation' are extremely generic terms that could conflict with many other skills involving data analysis, document creation, or business tools. No specific niche is carved out. | 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 a generic template with no actual content. It describes capabilities in abstract terms but provides zero actionable guidance, code examples, or workflows for report generation. The entire body could be replaced with a single sentence without losing information.
Suggestions
Add concrete, executable code examples showing how to generate at least one type of report (e.g., CSV summary, PDF report, Excel workbook)
Define a clear workflow with numbered steps for the report generation process, including data input, transformation, and output validation
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific techniques or patterns for report generation
Include at least one complete input/output example showing what data goes in and what the generated report looks like
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actionable information. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that waste tokens without teaching Claude anything specific. | 1 / 3 |
Actionability | There is no concrete guidance, code, commands, or specific examples. The skill describes what it claims to do but never shows how to actually generate a report. Statements like 'Generates production-ready code' are claims without demonstration. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill mentions 'step-by-step guidance' but provides none. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no examples, and no navigation to supporting documentation. It's essentially a placeholder with no substance to disclose. | 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
0c08951
- 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.