CtrlK
BlogDocsLog inGet started
Tessl Logo

avalonia-viewmodels-zafiro

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

70

1.94x
Quality

56%

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

51%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 lean and names concrete Zafiro/ReactiveUI APIs, but it provides no executable code, no sequenced workflow, a placeholder 'When to Use' line, and four referenced guide files that do not exist in the skill bundle. This leaves it actionable only at a high level and structurally incomplete.

Suggestions

Add at least one minimal executable ViewModel and WizardBuilder code snippet so the guidance is actionable rather than a list of class names.

Replace the placeholder 'When to Use' line with concrete trigger conditions and a short sequenced workflow for creating a ViewModel or wizard.

Either ship the referenced guide files (viewmodels.md, wizards.md, navigation_sections.md, composition.md) in the bundle or inline the essential content so the progressive-disclosure links resolve.

DimensionReasoningScore

Conciseness

The body is lean and names concrete APIs (ReactiveObject, WhenAnyValue, IEnhancedCommand, SlimWizard, WizardBuilder, [Section]) without explaining concepts Claude already knows; only minor fluff like 'leveraging the power of the Zafiro toolkit' keeps it from a 5.

4 / 5

Actionability

It names concrete classes and APIs but provides no executable code or commands, and the actual how-to is delegated to guide files that are not present, leaving the guidance incomplete rather than vague.

3 / 5

Workflow Clarity

The numbered Core Principles are principles rather than a sequenced workflow, there are no validation checkpoints, and the 'When to Use' line is a meaningless placeholder ('applicable to execute the workflow or actions described in the overview').

2 / 5

Progressive Disclosure

The overview is well-structured with clearly signaled one-level-deep references to four guides, but all four referenced files (viewmodels.md, wizards.md, navigation_sections.md, composition.md) are absent from the bundle, so the disclosure is incomplete rather than functional.

3 / 5

Total

12

/

20

Passed

Description

61%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 clearly names a specific niche (Avalonia + Zafiro + ReactiveUI) with natural domain keywords, but it omits any 'Use when...' trigger clause, which caps completeness at 3 and limits trigger guidance. Specificity is held back by the generic 'creation patterns' phrasing rather than concrete actions.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger situations, e.g. 'Use when building Avalonia ViewModels or multi-step wizards with ReactiveUI and Zafiro.'

Replace the generic 'creation patterns' with concrete actions such as 'create ViewModels, build wizards, wire View-ViewModel navigation, and register UI sections'.

Include common synonyms or file cues users might say (Avalonia UI, .axaml, ReactiveUI commands, Zafiro toolkit) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the Avalonia/Zafiro domain and concrete artifacts (ViewModel, Wizard) plus specific tooling, but the action stays generic ('creation patterns') rather than listing several concrete operations, fitting the 1-2-concrete-actions anchor above the minimal 'names the domain' level.

3 / 5

Completeness

Has a clear 'what' (ViewModel and Wizard creation patterns for Avalonia) but no 'Use when...' clause or equivalent trigger guidance, which the rubric caps at 3.

3 / 5

Trigger Term Quality

Includes good domain keyword coverage a user would naturally say (Avalonia, ViewModel, Wizard, Zafiro, ReactiveUI), noticeably above the midpoint, though it lacks an explicit 'use when' phrasing and common synonyms/file cues that would reach comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear, narrow niche (Avalonia + Zafiro + ReactiveUI) with minimal overlap risk, but the absence of explicit trigger phrases keeps it just below the fully-distinct anchor.

4 / 5

Total

14

/

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.

Validation14 / 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
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.