dashboard-layout-planner
Dashboard Layout Planner - Auto-activating skill for Data Analytics. Triggers on: dashboard layout planner, dashboard layout planner Part of the Data Analytics skill category.
34
0%
Does it follow best practices?
Impact
100%
1.00xAverage 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/dashboard-layout-planner/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 'Use when...' guidance. It would be nearly useless for Claude to differentiate this skill from others in a multi-skill environment.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Plans and arranges dashboard components, organizes chart placement, recommends widget sizing and grid layouts for data dashboards.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about dashboard design, arranging charts, laying out widgets, organizing data visualizations, or planning a dashboard grid.'
Include varied natural keywords users might say, such as 'dashboard design', 'chart layout', 'widget arrangement', 'data visualization layout', 'KPI placement', and 'dashboard grid'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Data Analytics') and a label ('Dashboard Layout Planner') but describes no concrete actions. There are no verbs indicating what the skill actually does—no mention of arranging widgets, designing layouts, organizing charts, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond its name and completely lacks a 'when should Claude use it' clause. There is no explicit trigger guidance or use-case description. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the redundant 'dashboard layout planner' repeated twice. There are no natural user keywords like 'dashboard design', 'widget placement', 'chart arrangement', 'layout', or 'data visualization'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to distinguish this skill from other data analytics or dashboard-related skills. 'Data Analytics' is extremely broad and 'Dashboard Layout Planner' without further specifics could overlap with many visualization or reporting skills. | 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 consists entirely of boilerplate meta-descriptions that repeat 'dashboard layout planner' without ever providing actual instructions, code examples, layout patterns, or any concrete guidance for planning dashboard layouts. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable content such as dashboard layout grid systems, component placement patterns, or code examples (e.g., CSS grid layouts, Plotly Dash configurations, or Grafana JSON templates).
Define a clear workflow for planning a dashboard layout, e.g.: 1) Identify KPIs, 2) Choose layout pattern (F-pattern, Z-pattern), 3) Assign components to grid positions, 4) Validate information hierarchy.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual instructional content.
Include specific examples of dashboard layouts with visual hierarchy principles, such as placing key metrics in the top-left quadrant and detail views below the fold.
| 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 concrete guidance. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no specific steps, no examples of dashboard layouts, no concrete guidance whatsoever. It only describes what the skill would do rather than actually doing it. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. There are no references to detailed materials, no linked resources, and the sections all repeat the same vague information without progressive depth. | 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
4dee593
- 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.