avalonia-zafiro-development
Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.
51
40%
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 ./skills/antigravity-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.
The description identifies a specific technology stack (Avalonia UI + Zafiro) but fails to describe any concrete actions or provide explicit trigger guidance. It reads more like a category label than a functional skill description, making it difficult for Claude to know when to select it over other development-related skills.
Suggestions
Add concrete actions the skill performs, e.g., 'Enforces naming conventions, project structure patterns, and MVVM architecture rules for Avalonia UI projects using the Zafiro toolkit.'
Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when developing Avalonia UI applications, working with Zafiro, writing XAML, or setting up cross-platform desktop projects.'
Include natural keyword variations users might mention, such as 'XAML', 'cross-platform desktop', 'MVVM', '.axaml', or 'Avalonia controls'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'Avalonia UI development' and 'Zafiro toolkit' as domain identifiers, but does not list any concrete actions. Terms like 'skills, conventions, and behavioral rules' are abstract and do not describe what the skill actually does. | 1 / 3 |
Completeness | The 'what' is extremely vague ('skills, conventions, and behavioral rules') and there is no explicit 'when' clause or trigger guidance. The description fails to answer either question clearly. | 1 / 3 |
Trigger Term Quality | It includes 'Avalonia UI' and 'Zafiro toolkit' which are relevant domain-specific keywords a user might mention, but lacks common variations or natural phrases users would say (e.g., 'XAML', 'cross-platform UI', 'desktop app', 'MVVM', specific file types). | 2 / 3 |
Distinctiveness Conflict Risk | 'Avalonia UI' and 'Zafiro toolkit' provide some distinctiveness from generic UI or coding skills, but the vague framing ('conventions and behavioral rules') could overlap with any coding standards or style guide skill. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill serves well as a hub/overview document with strong progressive disclosure to detailed guides. However, the main file itself lacks concrete, executable guidance—relying entirely on linked files for actionable content. The 'When to Use' section is meaningless filler, and the 'Core Pillars' section explains concepts at a level Claude doesn't need.
Suggestions
Remove the 'When to Use' section entirely—it adds no information and wastes tokens.
Add a concrete code example in the overview (e.g., a minimal ViewModel skeleton following the conventions) to make the skill immediately actionable without requiring navigation to sub-files.
Add a validation checkpoint to the 'Procedure Before Writing Code' workflow, such as 'Verify the chosen approach aligns with Zafiro patterns by checking against zafiro-shortcuts.md before implementing.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Core Pillars' section is somewhat verbose with explanations Claude likely already understands (e.g., 'Pure MVVM logic', 'Strictly Avalonia-independent ViewModels'). The 'When to Use' section is a vacuous tautology that wastes tokens. However, the overall structure is relatively lean. | 2 / 3 |
Actionability | The 'Procedure Before Writing Code' section provides some concrete guidance (search first, propose extensions, use DynamicData operators), but lacks executable examples, specific commands, or concrete code snippets. The actual actionable content is deferred to linked files. | 2 / 3 |
Workflow Clarity | The 3-step procedure before writing code provides a basic sequence but lacks validation checkpoints or feedback loops. There's no explicit verification step (e.g., 'confirm no existing helper exists before proceeding') and no error recovery guidance. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview and well-signaled one-level-deep references to five separate guide files. Each linked file has a descriptive title and brief explanation of its contents, making navigation easy. | 3 / 3 |
Total | 9 / 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 | |
- Repository
- boisenoise/skills-collections
- Commit
f1697b6
- 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.