avalonia-zafiro-development
Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.
Install with Tessl CLI
npx tessl i github:boisenoise/skills-collections --skill avalonia-zafiro-developmentOverall
score
61%
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
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 identifies the technology domain (Avalonia UI, Zafiro), it fails to specify concrete capabilities or provide explicit trigger conditions for when Claude should use this skill. The phrase 'Mandatory skills, conventions, and behavioral rules' describes meta-information about the skill rather than what it actually helps accomplish.
Suggestions
Replace abstract terms with concrete actions: e.g., 'Creates Avalonia UI components, implements MVVM patterns, applies Zafiro styling and controls'
Add an explicit 'Use when...' clause: e.g., 'Use when building cross-platform desktop applications with Avalonia, working with XAML layouts, or implementing Zafiro UI components'
Include natural trigger terms users would say: 'Avalonia', 'Zafiro', 'XAML', 'cross-platform desktop', '.axaml files', 'WPF alternative'
| 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 'Use when...' guidance for Claude to know when to select this skill. | 1 / 3 |
Trigger Term Quality | Contains domain-specific terms 'Avalonia UI' and 'Zafiro toolkit' which users familiar with these technologies would mention, but lacks common variations or related terms like 'XAML', 'cross-platform UI', 'desktop app', or '.NET UI'. | 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
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill demonstrates strong organization and appropriate progressive disclosure, serving as an effective index to detailed implementation guides. However, the main file lacks concrete code examples and the workflow section could benefit from explicit validation checkpoints. The content respects token efficiency while providing clear navigation to deeper materials.
Suggestions
Add a minimal executable code example in the main file 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 explicit validation steps, such as 'Verify no existing helper covers your use case before proposing a new extension'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting only essential information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | The skill provides a clear procedure and references to detailed guides, but lacks concrete code examples or executable commands in the main file. The actionable content is deferred to linked documents rather than demonstrated here. | 2 / 3 |
Workflow Clarity | The 'Procedure Before Writing Code' section provides a clear 3-step sequence, but lacks validation checkpoints or feedback loops. There's no explicit verification step to confirm the search was adequate or that the proposed extension is appropriate. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and well-signaled one-level-deep references to detailed guides. Each linked document has a clear purpose and the navigation is intuitive. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
91%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.