avalonia-viewmodels-zafiro
tessl i github:sickn33/antigravity-awesome-skills --skill avalonia-viewmodels-zafiroOptimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI.
Validation
75%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 12 / 16 Passed | |
Implementation
57%This skill is well-organized as a navigation hub with good progressive disclosure and concise writing. However, it critically lacks actionability - there are no code examples, concrete patterns, or executable guidance in the main skill file itself. The skill reads more like a table of contents than instructional content.
Suggestions
Add at least one concrete, executable code example showing a basic ViewModel pattern with ReactiveUI and Zafiro (e.g., a minimal ViewModel with IEnhancedCommand)
Include a quick-start code snippet demonstrating the most common use case before directing to detailed guides
Add a brief example of the [Section] attribute usage to make the 'Automatic Section Discovery' principle actionable
| 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 concepts and points to other files without demonstrating any actual implementation patterns. | 1 / 3 |
Workflow Clarity | The core principles provide a logical sequence of concepts, but there are no explicit steps, validation checkpoints, or workflows for actually implementing these patterns. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-signaled one-level-deep references to detailed guides. Navigation is easy with clearly labeled links to specific topics. | 3 / 3 |
Total | 9 / 12 Passed |
Activation
40%The description identifies a clear technical niche with specific frameworks but fails to provide explicit usage triggers and lacks detailed concrete actions. The specificity to Avalonia/Zafiro/ReactiveUI stack makes it distinctive, but the absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when creating ViewModels, implementing wizard flows, or building Avalonia UI with ReactiveUI patterns'
Expand concrete actions to include specific capabilities like 'create reactive commands, implement wizard step navigation, set up property bindings, configure dependency injection'
Include common term variations users might say such as 'MVVM', 'reactive UI', 'cross-platform desktop app', or 'wizard dialog'
| 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 + ViewModel/Wizard patterns creates a very specific niche that is unlikely to conflict with other skills; these are distinct framework-specific triggers. | 3 / 3 |
Total | 8 / 12 Passed |
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.