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 critically underdeveloped. It functions as little more than a label, providing no concrete actions, no meaningful trigger terms, and no guidance on when Claude should select this skill. It would be nearly impossible for Claude to reliably choose this skill from a pool of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates formatted business reports from data sources including sales summaries, financial statements, and performance dashboards.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to generate a report, create a business summary, produce analytics output, or build a dashboard.'
Remove the duplicate trigger term ('report generator' listed twice) and expand with varied natural language terms users might say, such as 'create report', 'business summary', 'weekly report', 'data report', 'export report'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It only names itself ('Report Generator') and its category ('Business Automation') without describing what it actually does—no mention of specific report types, data sources, formats, or operations. | 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 trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'report generator' repeated twice. This misses natural user phrases like 'generate a report', 'create report', 'business report', 'summary', 'analytics', or any domain-specific keywords users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Report Generator' and 'Business Automation' could overlap with virtually any reporting, analytics, or business-related skill. There are no distinct triggers or niche identifiers to differentiate it. | 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 with no actionable content. It consists entirely of generic boilerplate that describes what a report generator skill would do without providing any actual instructions, code, examples, or workflows. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for generating reports (e.g., Python scripts using pandas/openpyxl to create Excel reports, or Jinja2 templates for HTML reports).
Define a clear multi-step workflow: gather data → transform/aggregate → generate report → validate output, with specific commands and validation checkpoints at each stage.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill meta-information rather than teaching how to generate reports.
Include at least one complete, copy-paste-ready example showing input data and the resulting report output, with specific format details (CSV, Excel, PDF, etc.).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'report generator' excessively, and provides zero domain-specific information. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no specific steps, no examples of report formats, no tool usage. The 'capabilities' section describes what the skill claims to do but never actually does it. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to supporting files, no structured navigation, and no bundle files to support it. There is nothing to progressively disclose because there is no substantive content. | 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
3a2d27d
- 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.