Optimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI.
51
Quality
38%
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 ./.agent/skills/avalonia-viewmodels-zafiro/SKILL.mdQuality
Discovery
32%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, Zafiro, ReactiveUI) which provides some distinctiveness, but fails to explain concrete actions or provide explicit trigger guidance. It reads more like a topic label than a functional skill description that would help Claude choose it from a large skill library.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when creating ViewModels, implementing multi-step wizards, or building Avalonia UI with ReactiveUI bindings'
List specific concrete actions such as 'create reactive ViewModels', 'implement wizard navigation flow', 'set up property bindings', 'handle validation in wizard steps'
Include natural keyword variations users might say: 'MVVM pattern', 'reactive UI', 'step wizard', 'Avalonia app', 'cross-platform desktop UI'
| 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. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'what' is also weak, warranting a 1. | 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 'step-by-step wizard'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Avalonia + Zafiro + ReactiveUI is fairly specific and unlikely to conflict with generic coding skills, but 'ViewModel' and 'Wizard' patterns could overlap with other MVVM or UI framework skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
44%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has excellent structure and conciseness, serving as a clean index to more detailed guides. However, it lacks any actionable content - no code examples, no concrete commands, and no workflow guidance. As a standalone skill body, it provides no executable value.
Suggestions
Add at least one executable code example showing a minimal ViewModel or command creation pattern
Include a quick-start workflow with numbered steps for creating a basic ViewModel using the described patterns
Provide a concrete code snippet demonstrating IEnhancedCommand or SlimWizard usage rather than just naming them
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, listing core principles without over-explaining concepts Claude already knows. No verbose explanations of what ReactiveUI or ViewModels are. | 3 / 3 |
Actionability | No executable code, commands, or concrete examples are provided. The content only describes concepts and points to other files without giving any copy-paste ready guidance. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. The skill lists principles and references but provides no sequenced process for creating ViewModels or Wizards, nor any validation checkpoints. | 1 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-signaled one-level-deep references to specific guides (viewmodels.md, wizards.md, etc.). Navigation is easy and content is appropriately split. | 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 | |
3395991
Table of Contents
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.