dashboard
Use when reading, editing, or creating files in dlt/_workspace/helpers/dashboard/ or tests/workspace/helpers/dashboard/ or tests/e2e/
63
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 lacking as it only specifies file paths without explaining what the skill actually does or what capabilities it provides. It reads more like a file path filter than a skill description, leaving Claude unable to understand when this skill would be genuinely useful beyond matching directory names.
Suggestions
Add concrete actions describing what the skill does (e.g., 'Creates and maintains dashboard components, configures visualization widgets, manages dashboard layouts').
Include natural trigger terms users would say (e.g., 'dashboard', 'visualization', 'charts', 'metrics display', 'e2e tests').
Add a clear 'Use when...' clause that explains the purpose beyond file paths (e.g., 'Use when building dashboard interfaces, adding new dashboard widgets, or writing end-to-end tests for dashboard functionality').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('reading, editing, or creating files') without specifying any concrete actions or capabilities. It only mentions file paths without explaining what the skill actually does. | 1 / 3 |
Completeness | The description only partially addresses 'when' (file paths) but completely fails to explain 'what' the skill does. There's no explanation of the skill's purpose or capabilities. | 1 / 3 |
Trigger Term Quality | Contains only technical file paths rather than natural keywords users would say. Users wouldn't naturally mention 'dlt/_workspace/helpers/dashboard/' in their requests. | 1 / 3 |
Distinctiveness Conflict Risk | The specific file paths provide some distinctiveness and would prevent conflicts with general file-handling skills, but the lack of domain context means it could still overlap with other dashboard or testing-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong reference skill that efficiently documents the dashboard codebase structure, conventions, and testing approach. It excels at actionability with clear placement tables and concrete commands. The main weakness is the lack of explicit validation workflows for development tasks like adding new cells or modifying utils.
Suggestions
Add a brief workflow section with validation steps for common tasks (e.g., 'After adding a new cell: 1. Run test-all-cells, 2. Verify dependencies, 3. Check marimo renders')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting file layouts, architecture, and conventions without explaining concepts Claude already knows. Every section provides actionable reference information without padding. | 3 / 3 |
Actionability | Provides concrete file paths, specific commands (make test-workspace-dashboard), clear tables mapping tasks to locations, and explicit coding conventions like underscore-prefixed variables. Copy-paste ready commands and clear placement guidance. | 3 / 3 |
Workflow Clarity | While the 'Where to Put New Code' table provides clear guidance, the skill lacks explicit validation steps or feedback loops for development workflows. No verification steps for testing new cells or confirming changes work correctly. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Overview, File Layout, Architecture, Testing). Content is appropriately structured for a reference skill with logical groupings and easy navigation via headers. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.