avalonia-viewmodels-zafiro
Optimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI.
52
41%
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-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 makes it unlikely to conflict with other skills. However, it lacks specific concrete actions and entirely omits a 'Use when...' clause, making it incomplete for Claude's skill selection process. The description reads more like a topic label than actionable selection guidance.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks about creating ViewModels, implementing wizard flows, or setting up MVVM patterns in Avalonia with Zafiro and ReactiveUI.'
List specific concrete actions the skill covers, e.g., 'Generates ViewModel classes, scaffolds multi-step wizard UIs, configures reactive bindings, and implements navigation between wizard steps.'
Include additional natural trigger terms like 'MVVM', 'reactive bindings', 'step-by-step form', or 'multi-step dialog' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ViewModel and Wizard creation) and the technology stack (Avalonia, Zafiro, ReactiveUI), but doesn't list specific concrete actions like 'generate ViewModels', 'scaffold wizard steps', or 'configure reactive bindings'. | 2 / 3 |
Completeness | Describes what (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 only partially described, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant technical keywords like 'ViewModel', 'Wizard', 'Avalonia', 'Zafiro', and 'ReactiveUI' that users in this niche would naturally use, but misses common variations or related terms like 'MVVM', 'WPF alternative', 'step-by-step UI', or 'reactive patterns'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Avalonia + Zafiro + ReactiveUI + ViewModel/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
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions well as a table of contents with good progressive disclosure, but the main file itself lacks any actionable, executable content. The core principles are abstract descriptions rather than concrete instructions, and the 'When to Use' section is a meaningless placeholder. The skill would benefit greatly from at least one quick-start code example showing a minimal ViewModel or command pattern.
Suggestions
Add a 'Quick Start' section with a minimal, executable code example showing a basic ViewModel with ReactiveUI and an IEnhancedCommand, so the skill is actionable without needing to read linked files.
Remove or replace the 'When to Use' section—its current content ('applicable to execute the workflow or actions described in the overview') adds no value.
Make the Core Principles more concrete by showing brief code snippets or at least specific class/method signatures instead of abstract descriptions like 'Use ReactiveUI (ReactiveObject, WhenAnyValue, etc.)'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary filler like 'This skill provides a set of best practices and patterns for...' and the vague 'When to Use' section. The core principles section explains concepts at a high level that could be tighter. | 2 / 3 |
Actionability | No concrete code examples, no executable commands, no copy-paste ready snippets. Everything is described abstractly ('Use ReactiveUI', 'Utilize IEnhancedCommand') without showing how. All actionable content is deferred to linked files. | 1 / 3 |
Workflow Clarity | The core principles provide a reasonable sequence of concepts, and the guides are logically ordered. However, there are no explicit steps, no validation checkpoints, and no concrete workflow for actually creating a ViewModel or Wizard. | 2 / 3 |
Progressive Disclosure | Clear overview with well-signaled one-level-deep references to four separate guide files. The structure is clean with distinct sections for guides, examples, and usage context. Navigation is straightforward. | 3 / 3 |
Total | 8 / 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.