report-template-generator
Report Template Generator - Auto-activating skill for Data Analytics. Triggers on: report template generator, report template generator Part of the Data Analytics skill category.
33
0%
Does it follow best practices?
Impact
95%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/12-data-analytics/report-template-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 its only trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select this skill. It would be indistinguishable from other data analytics or reporting skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates structured report templates with headers, data tables, summary sections, and chart placeholders for analytics workflows.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a report template, build a report layout, scaffold an analytics report, or generate a data summary document.'
Include natural keyword variations users would actually say, such as 'report layout', 'analytics report', 'create report', 'report scaffold', 'data report template', '.xlsx report', etc.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Data Analytics') and a label ('Report Template Generator') but does not describe any concrete actions. There are no specific capabilities listed like 'creates templates', 'formats tables', or 'generates charts'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line is just the skill name repeated, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'report template generator' repeated twice. It lacks natural variations users would say such as 'create a report', 'report layout', 'analytics template', 'dashboard template', or 'generate report'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'Data Analytics' and 'report template' could overlap with many other skills related to reporting, data visualization, dashboards, or document generation. Nothing distinguishes this skill's niche. | 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 with no substantive content. It repeatedly describes itself in abstract terms ('provides step-by-step guidance,' 'follows best practices') without ever delivering any actual guidance, code, templates, or actionable instructions. It reads like a placeholder or auto-generated stub that was never filled in with real content.
Suggestions
Replace the abstract capability descriptions with actual report template examples (e.g., SQL queries for common report types, Python/Jinja2 template code, or specific configuration files).
Add a concrete workflow with numbered steps for generating a report template, including validation of the output (e.g., schema validation, sample data test).
Include at least one complete, executable code example showing how to generate a report template end-to-end.
Remove all meta-sections like 'When to Use,' 'Example Triggers,' and 'Capabilities' that describe the skill rather than teaching how to perform the task.
| 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 section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific steps, no examples of actual report templates or generation logic. The 'capabilities' section describes what it claims to do but never actually does it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely states it 'provides step-by-step guidance' without actually containing any steps. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no references to external files, no structured sections with real content, and no navigation to deeper materials. The sections that exist are all superficial meta-descriptions. | 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.