CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

avalonia-viewmodels-zafiro

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

1.94x
Quality

59%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/avalonia-viewmodels-zafiro/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

36%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 SKILL.md body is a well-organized, concise index, but the entire substance it promises lives in four guide files that are missing from the bundle, and the body itself contains no executable guidance. The circular "When to Use" placeholder section compounds the impression of an unfinished skill.

Suggestions

Add the four referenced guide files (viewmodels.md, wizards.md, navigation_sections.md, composition.md) or inline their key content — currently every detailed reference in the Guides section is a broken link.

Replace the placeholder sentence "This skill is applicable to execute the workflow or actions described in the overview" with concrete applicability conditions (e.g. when to choose SlimWizard vs. plain ViewModels).

Add a minimal executable snippet for the most common case (e.g. a ViewModel using ReactiveObject with an IEnhancedCommand) so the skill carries some standalone value.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's familiarity with Avalonia/ReactiveUI, never explaining basics; it lists specific APIs without padding. Not 5 because "leveraging the power of ReactiveUI and the Zafiro toolkit" is fluff and the "When to Use" section is circular filler that adds no information.

4 / 5

Actionability

The Core Principles name real APIs (IEnhancedCommand, SlimWizard, WizardBuilder, [Section], DataTypeViewLocator) but provide no code, commands, or concrete steps — only high-level direction pointing to guide files that don't exist. Fits anchor 2 (high-level hints, missing specific steps to execute), not 3 since there is no executable concrete detail at all.

2 / 5

Workflow Clarity

There is no sequence or process to follow; the skill is an index of principles with no steps, checkpoints, or guidance on how to apply the patterns to a real task. Not 1 because the principles themselves are coherent and individually well-defined, but gaps dominate.

2 / 5

Progressive Disclosure

The Guides section cleanly links to viewmodels.md, wizards.md, navigation_sections.md, and composition.md, but none of these files exist (no references/, scripts/, or assets/ directories are present in the bundle). Every detailed reference is a dead end, making the skill an empty shell that is impossible to navigate in practice — the worst form of progressive disclosure.

1 / 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 distinctive and uses genuinely natural keywords for its niche, but it reads as a title rather than a trigger: it has a clear "what" with no "when" clause, and "Optimal" adds marketing flavor without adding capability information.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating ViewModels, wizards, or navigation flows in Avalonia applications built with Zafiro and ReactiveUI."

Drop the marketing word "Optimal" and instead enumerate the additional concrete capabilities the skill covers (command creation, section-based navigation, View-ViewModel wiring/DI).

Include synonyms users might type such as "multi-step flow" for wizards or "ReactiveUI commands" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain (Avalonia) and two concrete artifacts ("ViewModel and Wizard creation"), but "Optimal ... patterns" is a buzzword wrapper and coverage is not comprehensive (navigation, commands, and DI are unmentioned). Fits anchor 3: domain plus 1-2 concrete actions; not 4 because it doesn't list several specific actions.

3 / 5

Completeness

Has a clear "what" (ViewModel/Wizard creation patterns for Avalonia with Zafiro and ReactiveUI) but no "Use when ..." clause or equivalent trigger guidance; the missing 'when' explicitly caps this dimension at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural terms users of this stack would actually say: "ViewModel", "Wizard", "Avalonia", "Zafiro", "ReactiveUI". Good keyword coverage, though a few natural terms covered by the body (navigation, sections, commands, composition/DI) are missing. Not 3 because multiple relevant natural keywords are present, not just one generic one.

4 / 5

Distinctiveness Conflict Risk

Tightly scoped to the Avalonia + Zafiro + ReactiveUI niche with distinct trigger terms; virtually no overlap risk with generic UI or document skills. Clear match to anchor 5.

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/avalonia-viewmodels-zafiro/SKILL.md

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.