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.
36
Quality
3%
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
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 severely underdeveloped and would be nearly useless for skill selection. It provides no concrete actions, no meaningful trigger terms beyond the skill name, and no guidance on when Claude should select it. The description reads like auto-generated boilerplate rather than a useful skill description.
Suggestions
Add specific actions the skill performs, e.g., 'Designs dashboard layouts, arranges widgets, optimizes visual hierarchy, and plans component placement for data visualizations.'
Include a 'Use when...' clause with natural trigger terms like 'dashboard design', 'arrange widgets', 'layout planning', 'visualization placement', 'dashboard wireframe'.
Remove the duplicate trigger term and expand with variations users would naturally say when needing dashboard layout assistance.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Dashboard Layout Planner') without describing any concrete actions. There are no verbs or specific capabilities listed - it doesn't explain what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no explicit 'when to use' guidance. It only states it's part of Data Analytics category, which is insufficient for skill selection. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('dashboard layout planner, dashboard layout planner'). This is redundant and misses natural variations users might say like 'arrange dashboard', 'widget placement', 'dashboard design', or 'layout visualization'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'dashboard layout' is somewhat specific to a niche, the lack of detail about what distinguishes this from other dashboard or analytics skills creates potential overlap. The category mention helps slightly but isn't enough. | 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 a placeholder template with no substantive content. It describes what a dashboard layout planner skill should do but provides absolutely no actual guidance, examples, code, or methodology for planning dashboard layouts. The entire content could be replaced with actual dashboard layout principles, grid systems, visualization placement strategies, or responsive design patterns.
Suggestions
Add concrete dashboard layout principles (e.g., F-pattern reading, information hierarchy, KPI placement above the fold)
Include executable code examples for common dashboard frameworks (e.g., CSS grid layouts, Plotly Dash, Streamlit column configurations)
Provide a clear workflow: 1) Identify key metrics, 2) Prioritize by user needs, 3) Apply layout grid, 4) Validate with stakeholders
Add visual layout patterns or ASCII diagrams showing common dashboard arrangements (executive summary top, details below, filters sidebar)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | The skill contains zero concrete guidance, no code examples, no specific commands, and no actual instructions for dashboard layout planning. It only describes what it claims to do without showing how. | 1 / 3 |
Workflow Clarity | There is no workflow defined at all. The skill mentions 'step-by-step guidance' but provides none. No sequence, no validation steps, no actual process for creating dashboard layouts. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no examples, and no navigation to actual implementation guidance. It's essentially an empty shell. | 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
0c08951
- 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.