CtrlK
BlogDocsLog inGet started
Tessl Logo

avalonia-viewmodels-zafiro

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

45

Quality

48%

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 ./skills/avalonia-viewmodels-zafiro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

32%Weight 40%Scale 1-5

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 clean, readable overview hub, but it is a pointer document whose pointers are broken: all four referenced guide files are missing from the bundle, and no code or concrete guidance is inlined as a fallback. Combined with filler sections ("When to Use", "Limitations"), the skill as bundled gives Claude names of APIs but nothing executable.

Suggestions

Ship the four referenced guide files (viewmodels.md, wizards.md, navigation_sections.md, composition.md) in the bundle, or inline their key patterns into SKILL.md — as delivered, every guide link is broken.

Add at least one concrete, executable example in the body (e.g., a minimal ViewModel with ReactiveObject/WhenAnyValue or a WizardBuilder snippet) so the skill is actionable without the missing guides.

Remove the circular "When to Use" filler sentence and the generic boilerplate limitations; replace with the actual conditions under which the Zafiro/ReactiveUI patterns apply.

DimensionReasoningScore

Conciseness

The body is short and mostly efficient, but contains padding: "leveraging the power of", a circular "When to Use" section ("This skill is applicable to execute the workflow or actions described in the overview") that adds no information, and boilerplate limitations. Not a 2 because the core list of principles is genuinely terse and there is no explanation of concepts Claude already knows.

3 / 5

Actionability

The body only names APIs ("SlimWizard", "WizardBuilder", "[Section]", "IEnhancedCommand", "DataTypeViewLocator") with high-level hints like "use ReactiveUI to handle state and logic" but no code, commands, or specific steps. It is above the score-1 anchor because it does identify concrete tools and points to guides, but the guidance needed to execute anything is missing.

2 / 5

Workflow Clarity

"Core Principles" is a concept list, not a sequenced process; there is no ordered workflow and no validation checkpoints anywhere in the body. It is not a 1 because the content is coherent and the guides section implies where to find procedures, but no actual sequence is written.

2 / 5

Progressive Disclosure

The four guide links (viewmodels.md, wizards.md, navigation_sections.md, composition.md) are clearly signaled with one-line descriptions, but none of these files exist in the bundle — there is no references/ directory and no bundle files at all. Scoring against the actual bundle structure, the navigation leads nowhere, which is worse than the score-3 anchor's "references present but not clearly signaled"; it is not a 1 because the SKILL.md itself is well structured with no nesting.

2 / 5

Total

9

/

20

Passed

Description

65%Weight 40%Scale 1-5

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 strongly distinctive and uses the right niche vocabulary, but it reads as a topic label rather than an operational description. It states what the skill covers without listing several concrete actions and without any explicit "when to use" trigger guidance.

Suggestions

Add an explicit trigger clause, e.g., "Use when creating or refactoring ViewModels, wizards, or navigation in Avalonia apps built on Zafiro/ReactiveUI."

Replace the generic "Optimal ... creation patterns" framing with several concrete actions (e.g., "Build ViewModels with ReactiveObject, compose multi-step wizards with SlimWizard, wire views via DataTypeViewLocator").

Include natural trigger variations such as "MVVM" and "multi-step flow" to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ("ViewModel and Wizard creation patterns for Avalonia") which counts as 1-2 concrete actions, but "Optimal ... patterns" is generic and there is no broader action coverage. It does not list several specific actions, so it sits below the score-4 anchor.

3 / 5

Completeness

The "what" is clear (creation patterns for ViewModels and Wizards with Zafiro/ReactiveUI), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the "what" is concrete rather than vague.

3 / 5

Trigger Term Quality

"Avalonia", "Zafiro", "ReactiveUI", "ViewModel", and "Wizard" are exactly the natural terms a user in this ecosystem would say. A few common variations (e.g., "MVVM", "multi-step flow") are missing, keeping it below the comprehensive score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

"Avalonia using Zafiro and ReactiveUI" carves out a clear niche with distinct triggers that no generic skill would match, so conflict risk is minimal.

5 / 5

Total

15

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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
sickn33/agentic-awesome-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.