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 sections for executive summary, data tables, charts, and key findings 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 an analytics report, generate a data summary document, or set up a reporting format.'
Include natural keyword variations users might say, such as 'report', 'template', 'analytics report', 'data report', 'summary report', 'report layout', 'report format'.
| 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 such as 'creates tables', 'formats charts', or 'generates summary sections'. | 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 terms listed are 'report template generator' repeated twice. These are not natural keywords users would say—users are more likely to say 'create a report', 'report template', 'analytics report', 'dashboard', etc. Coverage of natural variations is essentially absent. | 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. There are no distinct triggers 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 essentially a placeholder with no substantive content. It contains no actionable instructions, no code examples, no concrete workflows, and no references to supporting materials. Every section restates the skill name without providing any actual guidance on generating report templates.
Suggestions
Add concrete, executable code examples showing how to generate report templates (e.g., SQL queries for common report structures, Python/Jinja2 template generation, or BI tool configurations).
Define a clear multi-step workflow: e.g., 1) Identify data sources, 2) Define metrics/KPIs, 3) Generate template with specific tool/command, 4) Validate output.
Remove all generic filler text ('Provides step-by-step guidance', 'Follows industry best practices') and replace with specific patterns, schemas, or template examples.
Add references to supporting files (e.g., example templates, SQL snippets, visualization configs) or create bundle files that contain reusable report template assets.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing useful. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vacuous. It explains what triggers are and restates the skill name repeatedly without adding any actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples of report templates, no SQL snippets, no data visualization patterns. The entire content describes rather than instructs, offering only vague promises of capability. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined at all. The skill claims to provide 'step-by-step guidance' but contains no actual steps. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | There are no references to supporting files, no linked resources, and no bundle files. The content is a monolithic block of generic text with no meaningful structure or navigation to deeper material. | 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.