avalonia-viewmodels-zafiro

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

35%

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

The body is a well-structured overview that respects token budget, but it is almost entirely a pointer to guide files that are missing, with no executable code or sequenced workflow. Its value depends entirely on bundle files that are not present.

Suggestions

Provide the referenced guide files (viewmodels.md, wizards.md, navigation_sections.md, composition.md) or inline at least one executable code example for each core principle.

Add a concrete, sequenced workflow for at least one common task (e.g., building a wizard) with an explicit validation/build checkpoint.

Replace the generic 'When to Use' boilerplate with specific trigger conditions tied to the named patterns.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but the generic 'When to Use' and 'Limitations' boilerplate ('applicable to execute the workflow or actions described in the overview') earns few tokens and could be tightened.	2 / 3
Actionability	It names APIs (ReactiveObject, WhenAnyValue, IEnhancedCommand, SlimWizard, WizardBuilder, [Section], DataTypeViewLocator) but provides no executable code, commands, or concrete examples; all real guidance is deferred to guide files that are not present.	1 / 3
Workflow Clarity	It organizes content into labeled Core Principles and Guides giving a navigable structure, but presents no sequenced multi-step workflow with validation checkpoints; the steps are a list of principles rather than an ordered process.	2 / 3
Progressive Disclosure	The overview-to-guides pattern is correct and references are clearly signaled one level deep, but the four referenced guide files (viewmodels.md, wizards.md, navigation_sections.md, composition.md) do not exist in any bundle directory, so navigation is broken.	2 / 3
	Total	7 / 12 Passed

Description

50%

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 is specific to a clear niche and names the relevant stack and actions, but it lacks any 'Use when...' trigger guidance and reads as a coverage statement rather than a concrete action list. It is solid but capped at the mid-level across most dimensions.

Suggestions

Add an explicit 'Use when' trigger clause naming natural user phrases (e.g., 'Use when building Avalonia ViewModels or wizards with ReactiveUI/Zafiro, or when wiring up navigation and DI').

Replace 'Optimal ... creation patterns' with concrete actions (e.g., 'Create ViewModels and commands, build multi-step wizards, register UI sections, and wire Views to ViewModels').

Include common variation terms users might say ('Avalonia UI', 'ReactiveUI commands', 'SlimWizard') to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Avalonia, Zafiro, ReactiveUI) and actions ('ViewModel and Wizard creation patterns'), but 'creation patterns' is a coverage description rather than a list of multiple concrete actions like 'create, navigate, wire up'.	2 / 3
Completeness	Answers 'what' (ViewModel/Wizard creation patterns for Avalonia) but has no 'Use when...' clause or explicit trigger guidance, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	Contains relevant domain keywords a stack user might say ('ViewModel', 'Wizard', 'Avalonia', 'ReactiveUI'), but 'Optimal ... patterns' is framed as jargon with no natural 'Use when' phrasing or common variations.	2 / 3
Distinctiveness Conflict Risk	The Avalonia + Zafiro + ReactiveUI niche is specific and unlikely to conflict broadly, but absent explicit distinct triggers keep it from a 3; it could overlap with general Avalonia/ReactiveUI skills.	2 / 3
	Total	8 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 4 missing	Warning

	Total	14 / 16 Passed

Repository: boisenoise/skills-collections
Commit: f36337d

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.