avalonia-zafiro-development
Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.
64
Quality
47%
Does it follow best practices?
Impact
93%
2.44xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./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), it fails to describe concrete capabilities or provide explicit trigger conditions. The phrase 'skills, conventions, and behavioral rules' is vague and doesn't help Claude understand when to select this skill.
Suggestions
Add specific concrete actions like 'Create Avalonia controls, implement MVVM patterns, apply Zafiro styling, configure cross-platform layouts'
Add an explicit 'Use when...' clause with trigger terms like 'Avalonia', 'Zafiro', 'cross-platform desktop UI', 'XAML controls', '.NET UI framework'
Replace abstract terms like 'behavioral rules' with specific capabilities that describe what Claude will actually do when this skill is activated
| 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 components', 'style controls', 'implement MVVM patterns'). | 1 / 3 |
Completeness | The description vaguely addresses 'what' (rules for Avalonia/Zafiro development) but provides no 'when' clause or explicit trigger guidance. Missing any 'Use when...' statement entirely. | 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 excels at organization and token efficiency, serving as a clean entry point to a well-structured documentation system. However, it lacks concrete code examples in the main file and the procedural guidance, while clear, doesn't include validation steps or specific commands to execute the workflow.
Suggestions
Add a concrete code example in the main skill showing a minimal Zafiro/Avalonia pattern (e.g., a simple ViewModel with DynamicData)
Expand the 'Procedure Before Writing Code' with specific search commands or validation steps (e.g., 'Search for: `class.*ViewModel` to find existing patterns')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using bullet points and brief descriptions. It assumes Claude understands MVVM, ReactiveUI, and DynamicData without explaining these concepts. | 3 / 3 |
Actionability | The skill provides a clear procedure with 3 steps, but lacks concrete code examples or executable commands. The guidance is directional rather than copy-paste ready. | 2 / 3 |
Workflow Clarity | The 'Procedure Before Writing Code' section provides a clear 3-step sequence, but lacks validation checkpoints or feedback loops for error recovery when implementing patterns. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and well-signaled one-level-deep references to 5 separate guides. Navigation is clear with descriptive link text. | 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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
9c177eb
- 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.