avalonia-viewmodels-zafiro
Optimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI.
35
31%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-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 and distinctive technology niche (Avalonia/Zafiro/ReactiveUI ViewModel and Wizard patterns), which helps with distinctiveness. However, it lacks specific concrete actions and critically omits any 'Use when...' guidance, making it incomplete for Claude's skill selection process. The description reads more like a topic label than an actionable skill description.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about creating ViewModels, wizard flows, or step-by-step UI navigation in Avalonia with ReactiveUI or Zafiro.'
List specific concrete actions such as 'Creates reactive ViewModels, implements multi-step wizard navigation, configures Zafiro dependency injection, and sets up ReactiveUI command bindings.'
Include natural keyword variations users might say, such as 'MVVM', 'reactive bindings', 'wizard steps', 'navigation flow', or 'Avalonia UI patterns'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ViewModel and Wizard creation) and the technology stack (Avalonia, Zafiro, ReactiveUI), but does not list specific concrete actions like 'create wizard steps', 'bind reactive properties', or 'implement navigation logic'. | 2 / 3 |
Completeness | Describes what at a high level (ViewModel and Wizard creation patterns) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant technical keywords like 'ViewModel', 'Wizard', 'Avalonia', 'Zafiro', and 'ReactiveUI' that users familiar with the stack would use, but misses common variations or natural phrases like 'MVVM', 'step-by-step wizard', 'reactive bindings', or 'WPF-like UI'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Avalonia + Zafiro + ReactiveUI + Wizard patterns is a very specific niche that is unlikely to conflict with other skills. These are distinct enough technology-specific triggers. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions as a table of contents rather than an actionable guide. It names patterns and frameworks but provides zero executable code or concrete steps. The referenced sub-guides that would contain the actual content are entirely missing from the bundle, leaving the skill with no standalone utility.
Suggestions
Add at least one concrete, executable code example for each core pattern (e.g., a minimal ViewModel with IEnhancedCommand, a basic SlimWizard setup) directly in SKILL.md.
Include the referenced bundle files (viewmodels.md, wizards.md, navigation_sections.md, composition.md) with detailed, actionable content, or inline the essential guidance if the bundle is not available.
Replace the generic 'When to Use' and 'Limitations' boilerplate sections with skill-specific constraints (e.g., minimum Zafiro version, required NuGet packages, known incompatibilities).
Add a concrete workflow with numbered steps for at least one common task (e.g., creating a new Wizard flow from scratch), including validation or testing checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary filler. The 'When to Use' and 'Limitations' sections are generic boilerplate that add no skill-specific value. The 'Core Principles' section explains concepts at a high level without adding actionable detail, and phrases like 'leveraging the power of' are padding. | 2 / 3 |
Actionability | There is no executable code, no concrete commands, and no specific examples in the body itself. The content describes concepts and patterns abstractly ('Use ReactiveUI', 'Utilize IEnhancedCommand') without showing how. All concrete guidance is deferred to referenced files that don't exist in the bundle. | 1 / 3 |
Workflow Clarity | There is no sequenced workflow, no step-by-step process, and no validation checkpoints. The skill describes patterns and principles but never walks through how to actually implement them. For a skill covering Wizards and multi-step flows, the absence of any workflow sequence is a significant gap. | 1 / 3 |
Progressive Disclosure | The structure attempts good progressive disclosure with clear references to four sub-guides (viewmodels.md, wizards.md, navigation_sections.md, composition.md), which is well-organized. However, none of these referenced files exist in the bundle, so the references are unverifiable and the skill provides almost no standalone value. The 'Example Reference' section points to external project files without paths or URLs. | 2 / 3 |
Total | 6 / 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
e41e34a
- 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.