report-generator
Report Generator - Auto-activating skill for Business Automation. Triggers on: report generator, report generator Part of the Business Automation skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill report-generatorOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is severely underdeveloped and would perform poorly in skill selection. It lacks any concrete actions, meaningful trigger terms, explicit usage guidance, and distinctive characteristics. The description reads more like a placeholder or auto-generated stub than a functional skill description.
Suggestions
Add specific concrete actions describing what reports this generates (e.g., 'Generates sales reports, financial summaries, and performance dashboards from business data')
Add a 'Use when...' clause with natural trigger terms like 'create report', 'generate summary', 'business analytics', 'quarterly report', 'data visualization'
Specify the domain or report types to distinguish from other potential reporting skills (e.g., 'financial reports', 'marketing analytics', 'inventory reports')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only 'Report Generator' as a name and 'Auto-activating skill for Business Automation' which is vague abstract language. No specific capabilities like 'generates sales reports', 'creates charts', or 'analyzes data' are mentioned. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no specific actions) and 'when should Claude use it' (no 'Use when...' clause or explicit trigger guidance). Only states it's part of Business Automation category. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'report generator, report generator' (duplicated). This misses natural variations users would say like 'create report', 'generate report', 'business report', 'analytics', 'summary', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'Business Automation' is extremely generic and could conflict with many other skills. 'Report Generator' without specifics (what kind of reports? what format? what data?) provides no clear niche to distinguish it from other reporting or business tools. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is a placeholder template with no actual content. It describes capabilities in abstract terms without providing any concrete guidance, code examples, or workflows for report generation. The skill would need to be completely rewritten with actual implementation details to be useful.
Suggestions
Add concrete, executable code examples showing how to generate reports (e.g., using pandas, openpyxl, or reporting libraries)
Define a clear workflow with specific steps: data gathering, transformation, template selection, output generation, and validation
Include specific report formats and templates (PDF, Excel, HTML) with actual code for each
Remove all generic boilerplate text and replace with actionable instructions that assume Claude's competence
| 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 | No concrete code, commands, or specific instructions are provided. The entire skill describes what it does in abstract terms ('provides step-by-step guidance', 'generates production-ready code') without actually providing any of that guidance or code. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for generating reports. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no examples to link to, and no organization beyond generic section headers. There's nothing to progressively disclose because there's no substantive 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 | |
- 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.