CtrlK
BlogDocsLog inGet started
Tessl Logo

avalonia-viewmodels-zafiro

Optimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI.

35

Quality

31%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agent/skills/avalonia-viewmodels-zafiro/SKILL.md

The canonical home for this skill is avalonia-viewmodels-zafiro in sickn33/antigravity-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

22%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a table of contents with no substantive content. It references four guide files that don't exist in the bundle, provides no executable code examples, and offers only abstract descriptions of patterns. While the structure and progressive disclosure intent are reasonable, the complete absence of actionable content and supporting files makes this skill non-functional.

Suggestions

Add at least one concrete, executable code example for each core pattern (ViewModel creation, EnhancedCommand usage, SlimWizard setup) directly in the SKILL.md.

Include the referenced guide files (viewmodels.md, wizards.md, navigation_sections.md, composition.md) in the bundle so the progressive disclosure structure actually works.

Add a quick-start workflow with numbered steps showing how to create a basic ViewModel with commands, including validation checkpoints (e.g., 'verify DI registration compiles').

Replace the vague 'Core Principles' section with a concise code snippet showing the minimal boilerplate for a Zafiro ViewModel, which is the novel information Claude needs.

DimensionReasoningScore

Conciseness

The content is relatively brief but includes some unnecessary explanation of core principles that Claude would already understand (e.g., 'Functional-Reactive Approach: Use ReactiveUI... to handle state and logic'). The descriptions are somewhat padded but not egregiously verbose.

2 / 3

Actionability

The skill provides no concrete code, commands, or executable examples. It describes concepts and points to external files but gives no copy-paste ready guidance. The 'Example Reference' section names files but provides no actual code snippets or patterns.

1 / 3

Workflow Clarity

There are no multi-step workflows, sequences, or validation checkpoints described. The content is purely a high-level overview with no procedural guidance on how to actually create ViewModels, Wizards, or manage navigation.

1 / 3

Progressive Disclosure

The skill has a clear structure with well-signaled references to four guide files (viewmodels.md, wizards.md, navigation_sections.md, composition.md). However, no bundle files are provided, meaning all referenced files are missing, making the references non-functional. The overview itself contains almost no substantive content, making it entirely dependent on files that don't exist.

2 / 3

Total

6

/

12

Passed

Description

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 patterns) but falls short on completeness by lacking any 'Use when...' guidance and on specificity by not listing concrete actions. It reads more like a topic label than a functional skill description.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about creating ViewModels, implementing wizard flows, or building Avalonia UI with Zafiro and ReactiveUI.'

List specific concrete actions such as 'Generates ViewModel boilerplate, scaffolds multi-step wizard navigation, configures reactive property bindings, and sets up Zafiro dependency injection.'

Include additional natural trigger terms like 'MVVM', 'reactive bindings', 'wizard steps', 'navigation flow', or 'cross-platform desktop UI' to improve discoverability.

DimensionReasoningScore

Specificity

Names the domain (ViewModel and Wizard creation) and specific frameworks (Avalonia, Zafiro, ReactiveUI), but doesn't list 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 familiar with these frameworks would use, but misses common variations like 'MVVM', 'step-by-step wizard', 'reactive UI patterns', or 'WPF alternative'.

2 / 3

Distinctiveness Conflict Risk

The combination of Avalonia + Zafiro + ReactiveUI + ViewModel/Wizard patterns is highly specific and unlikely to conflict with other skills, as this is a very narrow technology stack niche.

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
Dokhacgiakhoa/antigravity-ide
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.