dashboard-layout-planner
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill dashboard-layout-plannerDashboard Layout Planner - Auto-activating skill for Data Analytics. Triggers on: dashboard layout planner, dashboard layout planner Part of the Data Analytics skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with no substantive content. It names the skill and category but provides zero information about capabilities, use cases, or meaningful trigger terms. The repeated trigger phrase suggests auto-generated or template content that was never properly filled in.
Suggestions
Add specific capabilities: describe what the skill does (e.g., 'Arranges dashboard components, recommends widget placement, optimizes chart layouts for readability').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when designing dashboards, arranging visualizations, planning chart layouts, or organizing analytics displays').
Remove the redundant duplicate trigger term and replace with varied natural language keywords like 'dashboard design', 'widget arrangement', 'visualization layout', 'analytics display'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only names itself ('Dashboard Layout Planner') without describing what it actually does. There are no verbs or capabilities listed. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no capabilities listed) and 'when should Claude use it' (no explicit use-case guidance beyond the redundant trigger phrase). Both components are missing. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('dashboard layout planner, dashboard layout planner'). No natural user language like 'arrange widgets', 'design dashboard', 'chart placement', or 'visualization layout' is included. | 1 / 3 |
Distinctiveness Conflict Risk | While 'dashboard layout' is somewhat specific to a niche, the lack of detail means it could overlap with general data visualization, charting, or UI design skills. The category mention 'Data Analytics' provides some context but is insufficient. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is an empty template that provides no actual value for dashboard layout planning. It contains only meta-descriptions of what the skill claims to do without any concrete guidance, examples, layout patterns, or actionable instructions. The content fails on all dimensions because it's entirely placeholder text rather than genuine skill content.
Suggestions
Add concrete dashboard layout patterns with visual descriptions or ASCII diagrams (e.g., F-pattern, Z-pattern, grid layouts for different use cases)
Include specific examples of widget placement rules, sizing guidelines, and information hierarchy principles for dashboards
Provide a step-by-step workflow for planning a dashboard: 1) Identify KPIs, 2) Group related metrics, 3) Apply layout pattern, 4) Validate with stakeholder checklist
Add code examples for common dashboard frameworks (e.g., Plotly Dash, Streamlit, Tableau) showing how to implement recommended layouts
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual dashboard layout planning information. It explains what the skill does in abstract terms without providing any concrete guidance, wasting tokens on meta-description rather than actionable content. | 1 / 3 |
Actionability | No concrete code, commands, examples, or specific instructions are provided. The content only describes what the skill claims to do ('provides step-by-step guidance') without actually providing any guidance, layouts, or dashboard planning techniques. | 1 / 3 |
Workflow Clarity | No workflow is defined. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or processes for planning dashboard layouts. No validation checkpoints or decision points are included. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, examples, or related documentation. There's nothing to progressively disclose because there's no substantive content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.