CtrlK
BlogDocsLog inGet started
Tessl Logo

avalonia-viewmodels-zafiro

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

61

1.94x
Quality

41%

Does it follow best practices?

Impact

99%

1.94x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./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

42%Scale 1-3

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 to sub-files, but the main file itself lacks any actionable, executable content. The core principles section is too abstract and descriptive without concrete examples. The 'When to Use' section is a meaningless placeholder that wastes tokens.

Suggestions

Add at least one concrete, executable code example in the main file (e.g., a minimal ViewModel with ReactiveUI and IEnhancedCommand) to demonstrate the core pattern before linking to detailed guides.

Remove the 'When to Use' section entirely—it adds no information. Replace it with a quick-start snippet showing the most common pattern.

Replace the abstract Core Principles descriptions with terse, pattern-oriented statements that show rather than tell (e.g., show a 3-line WhenAnyValue binding instead of saying 'Use ReactiveUI to handle state and logic').

DimensionReasoningScore

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 guides are listed in a logical sequence (ViewModels → Wizards → Navigation → Composition), but there are no concrete steps, no validation checkpoints, and no workflow sequences in the skill itself. The actual workflows are entirely deferred to sub-files.

2 / 3

Progressive Disclosure

Clear overview with well-signaled one-level-deep references to four specific guide files. The content is appropriately split between a concise overview and detailed sub-documents, with clear navigation links and descriptive labels.

3 / 3

Total

8

/

12

Passed

Description

40%Scale 1-3

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) but is too terse to be effective for skill selection. It lacks explicit trigger guidance ('Use when...') and doesn't enumerate the specific actions or patterns it covers, making it hard for Claude to know when to select it over other skills.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks about creating ViewModels, wizards, or multi-step dialogs in Avalonia with ReactiveUI or Zafiro.'

List specific concrete actions the skill covers, e.g., 'Creates reactive ViewModels, implements multi-step wizard navigation, configures Zafiro dependency injection, sets up ReactiveUI bindings.'

Include additional natural trigger terms users might say, such as 'MVVM', 'reactive bindings', 'step-by-step UI', 'dialog wizard', or '.NET desktop app'.

DimensionReasoningScore

Specificity

Names the domain (ViewModel and Wizard creation) and the technology stack (Avalonia, Zafiro, ReactiveUI), but doesn't list specific concrete actions like 'create wizard steps', 'bind reactive properties', or 'implement navigation logic'.

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 weak, so this scores 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 + ViewModel/Wizard patterns is a very specific niche that is unlikely to conflict with other skills. The technology stack combination creates clear distinctiveness.

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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.