Use this skill when writing or debugging Vizro YAML dashboard configurations — component syntax, data_manager registration, custom function wiring, filter/parameter setup, or AG Grid tables. Activate when the user is building a Vizro app, encountering YAML or runtime errors, or asking about Vizro component patterns.
94
93%
Does it follow best practices?
Impact
92%
1.73xAverage score across 3 eval scenarios
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 a strong skill description that clearly identifies the specific framework (Vizro), lists concrete capabilities, and provides explicit trigger conditions. The only minor issue is the use of second-person imperative voice ('Use this skill when...', 'Activate when...') rather than third-person declarative, but the content quality is excellent across all dimensions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: writing/debugging YAML dashboard configurations, component syntax, data_manager registration, custom function wiring, filter/parameter setup, and AG Grid tables. | 3 / 3 |
Completeness | Clearly answers both 'what' (writing/debugging Vizro YAML dashboard configurations with specific sub-tasks) and 'when' ('Activate when the user is building a Vizro app, encountering YAML or runtime errors, or asking about Vizro component patterns'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Vizro', 'YAML', 'dashboard', 'data_manager', 'filter', 'parameter', 'AG Grid', 'runtime errors', 'component patterns'. These cover both the framework name and common task-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Vizro is a specific framework, and the description narrows scope to YAML dashboard configurations, data_manager, and AG Grid tables within that framework. This is a clear niche unlikely to conflict with generic YAML or dashboard skills. | 3 / 3 |
Total | 12 / 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 well-crafted skill that efficiently delivers Vizro-specific knowledge Claude wouldn't have natively. Its greatest strengths are the concise critical mistakes list and copy-paste-ready YAML patterns. The main weakness is the lack of an explicit end-to-end workflow sequence in the main file, which would help Claude understand the order of operations when building a Vizro app from scratch.
Suggestions
Add a brief 3-5 step workflow summary (e.g., 1. Register data → 2. Define pages/components → 3. Build dashboard → 4. Run) to give Claude a clear sequencing guide without needing to load the reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No explanations of what Vizro is, no padding about YAML basics. The numbered mistakes list is terse but informative, and the quick patterns section provides only essential examples without unnecessary commentary. | 3 / 3 |
Actionability | Provides fully executable YAML patterns and Python imports that are copy-paste ready. The critical mistakes section gives specific, concrete guidance (e.g., exact target format 'component_id.argument_name') rather than vague descriptions. | 3 / 3 |
Workflow Clarity | The skill is primarily a reference/pattern guide rather than a multi-step workflow, but it lacks any explicit sequencing for building a Vizro app (e.g., register data → define pages → build app → run). The 'End-to-End Data Flow' is deferred to the reference file without even a brief summary of the sequence. | 2 / 3 |
Progressive Disclosure | Excellent structure: concise overview in the main file with a clear navigation table pointing to specific sections in yaml-reference.md. References are one level deep and well-signaled with searchable section headers. | 3 / 3 |
Total | 11 / 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.
27d4055
Table of Contents
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.