create-dashboard
Create observability dashboards from OTEL metrics, logs, and traces using Kopai. Use when building metric visualizations, monitoring views, KPI panels, or when the user wants to see their telemetry data in a dashboard — even if they don't say "dashboard" explicitly. Also use when other skills or workflows need to present telemetry data visually (e.g. after root cause analysis).
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 is an excellent skill description that hits all the marks. It provides specific capabilities, comprehensive trigger terms including implicit scenarios, explicit 'Use when' guidance with multiple contexts, and a clear distinctive niche around OTEL observability dashboards with Kopai. The description also thoughtfully addresses cross-skill integration scenarios.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Create observability dashboards', 'metric visualizations', 'monitoring views', 'KPI panels', and specifies the data sources (OTEL metrics, logs, traces) and tool (Kopai). | 3 / 3 |
Completeness | Clearly answers both what (create observability dashboards from OTEL data using Kopai) and when (explicit 'Use when' clause covering multiple trigger scenarios including cross-skill integration like 'after root cause analysis'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'dashboards', 'metrics', 'logs', 'traces', 'visualizations', 'monitoring', 'KPI', 'telemetry data'. Also anticipates implicit requests ('even if they don't say dashboard explicitly'). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific niche: OTEL-based observability dashboards via Kopai. The combination of tool name, data types (OTEL metrics/logs/traces), and specific use cases (KPI panels, monitoring views) makes conflicts unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that efficiently teaches dashboard creation with Kopai. It leverages dynamic content discovery, provides immediately executable examples, includes clear validation steps with error recovery, and appropriately delegates detailed rules to separate files. The component compatibility table adds practical value without bloating the main content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, assuming Claude's competence with CLI tools and JSON structures. No unnecessary explanations of what dashboards or metrics are—jumps straight to actionable content. | 3 / 3 |
Actionability | Provides fully executable bash commands, a complete JSON example that's copy-paste ready, and concrete CLI commands for each workflow step. The quick example is immediately runnable. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence with explicit validation checkpoint (step 4 includes error handling with retry loop). The workflow covers discovery, design, creation, and verification with clear feedback loop on failure. | 3 / 3 |
Progressive Disclosure | Well-structured with dynamic schema/metrics discovery at top, concise workflow overview, quick example, component reference table, and clear pointer to detailed rules in separate files. One-level-deep references are clearly signaled. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- kopai-app/kopai-mono
- Commit
d5894e9
- 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.