avalonia-viewmodels-zafiro
Optimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI.
66
Quality
48%
Does it follow best practices?
Impact
99%
1.94xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/avalonia-viewmodels-zafiro/SKILL.mdQuality
Discovery
40%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 clear technical niche with specific framework names (Avalonia, Zafiro, ReactiveUI), making it distinctive. However, it lacks explicit trigger guidance ('Use when...') and doesn't enumerate the specific actions or patterns it covers, limiting Claude's ability to know when to select it.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when creating ViewModels in Avalonia', 'implementing multi-step wizards', or 'using ReactiveUI patterns'
List specific concrete actions such as 'create reactive ViewModels', 'implement wizard step navigation', 'bind observable properties', 'handle validation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Avalonia, Zafiro, ReactiveUI) and mentions 'ViewModel and Wizard creation patterns' as actions, but doesn't list specific concrete actions like 'create reactive commands', 'implement wizard navigation', or 'bind properties'. | 2 / 3 |
Completeness | Describes what (ViewModel and Wizard patterns) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms (ViewModel, Wizard, Avalonia, Zafiro, ReactiveUI) that users familiar with these frameworks would use, but missing common variations like 'MVVM', 'reactive programming', 'WPF alternative', or 'cross-platform UI'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Avalonia + Zafiro + ReactiveUI is a very specific niche that is unlikely to conflict with other skills; these are distinct framework names that clearly identify the skill's purpose. | 3 / 3 |
Total | 8 / 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.
The skill has excellent organization and progressive disclosure with clear references to detailed guides, but critically lacks actionable content. It reads more like a table of contents than a skill that teaches Claude how to do something. The core principles are abstract descriptions rather than concrete, executable guidance.
Suggestions
Add at least one concrete, executable code example for each core principle (e.g., a minimal ReactiveObject ViewModel, an IEnhancedCommand usage)
Include a 'Quick Start' section with copy-paste ready code showing the most common pattern
Replace the vague 'When to Use' section with specific trigger conditions or use cases that would invoke this skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations of concepts Claude would already know. Every section serves a clear purpose without padding. | 3 / 3 |
Actionability | The skill provides no concrete code examples, commands, or executable guidance. It only describes what to use (e.g., 'Use ReactiveUI', 'Utilize IEnhancedCommand') without showing how. | 1 / 3 |
Workflow Clarity | The guides section provides a logical structure for learning, but there are no explicit steps, validation checkpoints, or sequences for implementing the patterns described. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-signaled one-level-deep references to separate guide files. Navigation is easy and content is appropriately split. | 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
- 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.