Kpi Dashboard Template - Auto-activating skill for Enterprise Workflows. Triggers on: kpi dashboard template, kpi dashboard template Part of the Enterprise Workflows skill category.
34
3%
Does it follow best practices?
Impact
87%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/kpi-dashboard-template/SKILL.mdQuality
Discovery
7%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 extremely weak across all dimensions. It reads as auto-generated boilerplate with no concrete actions, no meaningful trigger terms beyond a single duplicated phrase, and no guidance on when Claude should select this skill. It would be nearly useless for skill selection among a large set of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates KPI dashboard templates with configurable metrics, charts, and performance indicators for business reporting.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a KPI dashboard, metrics report, performance tracking template, business scorecard, or key performance indicator visualization.'
Remove the duplicated trigger term and expand coverage to include natural variations like 'metrics dashboard', 'performance dashboard', 'business KPIs', 'scorecard template', etc.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names a template type ('kpi dashboard template') and a category ('Enterprise Workflows') without describing what the skill actually does—no verbs like 'creates', 'generates', 'configures', etc. | 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 meaningful 'Use when...' clause—only a mechanical 'Triggers on' line with a duplicated term. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'kpi dashboard template' repeated twice. It misses natural variations users might say such as 'KPI report', 'metrics dashboard', 'performance dashboard', 'business metrics', 'key performance indicators', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'kpi dashboard template' provides some specificity that distinguishes it from generic document or code skills, but the lack of detail about what it actually does and the vague 'Enterprise Workflows' category could cause overlap with other dashboard or reporting skills. | 2 / 3 |
Total | 5 / 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 actual content. It consists entirely of generic boilerplate that describes what a skill would do without providing any actionable guidance, code, examples, or workflows for creating KPI dashboards. It adds zero value beyond what Claude already knows.
Suggestions
Add concrete, executable code or configuration examples for creating a KPI dashboard (e.g., a template in HTML/React/Python with specific KPI metrics, chart types, and data binding patterns).
Define a clear multi-step workflow: gather KPI requirements → select metrics → design layout → implement dashboard → validate data accuracy, with specific validation checkpoints.
Include at least one complete, copy-paste-ready example of a KPI dashboard template with sample metrics (e.g., revenue, churn rate, NPS) and their visualization configurations.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers') that describe the skill itself rather than teaching Claude how to perform the task.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance, repeating 'kpi dashboard template' excessively without adding value. | 1 / 3 |
Actionability | There are zero concrete instructions, no code, no commands, no examples, and no specific guidance. Every section describes capabilities in vague terms rather than instructing Claude on what to actually do. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. The skill claims to provide 'step-by-step guidance' but contains none. There are no sequences, no validation checkpoints, and no process to follow. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no references to detailed materials, no linked resources, and no meaningful structure beyond boilerplate section headers. | 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 | |
4dee593
Table of Contents
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.