Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.
56
47%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/avalonia-zafiro-development/SKILL.mdQuality
Discovery
22%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 too abstract and lacks actionable detail. While it names the specific technologies (Avalonia UI, Zafiro toolkit), it fails to describe concrete capabilities or provide explicit trigger conditions for when Claude should use this skill. The phrase 'Mandatory skills, conventions, and behavioral rules' is vague and doesn't help Claude understand what actions this skill enables.
Suggestions
Add specific concrete actions the skill enables, such as 'Create Avalonia UI controls, implement MVVM patterns, apply Zafiro styling and themes'
Add an explicit 'Use when...' clause with trigger terms like 'Avalonia', 'Zafiro', 'cross-platform desktop UI', 'XAML controls', '.axaml files'
Replace abstract terms like 'behavioral rules' with specific capabilities that describe what Claude can actually do with this skill
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract language like 'skills, conventions, and behavioral rules' without listing any concrete actions. It doesn't specify what Claude actually does (e.g., 'create controls', 'style components', 'implement MVVM patterns'). | 1 / 3 |
Completeness | The description vaguely addresses 'what' (rules for Avalonia/Zafiro development) but provides no 'when' clause or explicit triggers. There's no guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes domain-specific terms 'Avalonia UI' and 'Zafiro toolkit' which users familiar with these technologies would mention, but lacks common variations or related terms users might say (e.g., 'cross-platform UI', 'XAML', 'desktop app'). | 2 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'Avalonia UI' and 'Zafiro toolkit' provides some distinctiveness, but 'development' is generic and could overlap with other UI or .NET development skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill demonstrates excellent organization and progressive disclosure, serving as a clean entry point to a comprehensive Avalonia/Zafiro development guide. However, it lacks concrete code examples in the main file and could benefit from validation steps in its workflow. The content appropriately delegates details to linked files while maintaining a useful overview.
Suggestions
Add a minimal executable code example demonstrating a core pattern (e.g., a simple DynamicData pipeline or Result type usage) to improve actionability
Enhance the 'Procedure Before Writing Code' section with validation checkpoints, such as 'If no similar implementation found, check Zafiro documentation at [link]' or criteria for when to proceed vs. ask for guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations of concepts Claude already knows. Every section serves a clear purpose without padding or verbose descriptions. | 3 / 3 |
Actionability | The skill provides clear procedural guidance in the 'Procedure Before Writing Code' section, but lacks concrete code examples or executable commands. The guidance is specific but abstract rather than copy-paste ready. | 2 / 3 |
Workflow Clarity | The 3-step procedure is clearly sequenced, but lacks validation checkpoints or feedback loops. There's no guidance on what to do if searches fail or how to verify that the chosen approach is correct. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-signaled one-level-deep references to detailed guides. Each linked file has a descriptive title indicating its content, making navigation easy. | 3 / 3 |
Total | 10 / 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 | |
332e58b
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.