CtrlK
BlogDocsLog inGet started
Tessl Logo

avalonia-zafiro-development

Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.

59

2.44x
Quality

40%

Does it follow best practices?

Impact

93%

2.44x

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-claude/skills/avalonia-zafiro-development/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 serves primarily as a well-organized hub document with good progressive disclosure to detailed guides. However, the main file itself is light on actionable, concrete guidance—the Core Pillars are abstract principles rather than executable instructions, and the pre-coding procedure lacks specificity and validation steps. The 'When to Use' section is a vacuous placeholder that should be removed or replaced with concrete trigger conditions.

Suggestions

Remove or replace the 'When to Use' section with specific trigger conditions (e.g., 'Apply when working on any .axaml or ViewModel file in this repository').

Add a concrete, executable quick-start example showing a minimal Zafiro ViewModel or DynamicData pipeline to make the skill immediately actionable.

Enhance the 'Procedure Before Writing Code' with validation checkpoints, e.g., 'Verify the chosen Zafiro helper's signature matches your use case by checking zafiro-shortcuts.md before proceeding.'

DimensionReasoningScore

Conciseness

Mostly efficient but the 'Core Pillars' section is somewhat abstract and tells Claude things it could infer. The 'When to Use' section is a meaningless tautology that wastes tokens. The 'Functional-Reactive MVVM' descriptions are brief but add little actionable value.

2 / 3

Actionability

The 'Procedure Before Writing Code' section provides some concrete guidance (search first, propose extensions, use DynamicData operators), but lacks executable examples, specific commands, or concrete code. The core content is mostly directional rather than instructional.

2 / 3

Workflow Clarity

The 'Procedure Before Writing Code' provides a 3-step sequence but lacks validation checkpoints or feedback loops. There's no guidance on what to do if a search yields no results or how to verify that the correct Zafiro helper was chosen.

2 / 3

Progressive Disclosure

Excellent structure with a concise overview and well-signaled one-level-deep references to five separate guide files. Each linked file has a clear descriptive label making navigation easy and content appropriately split.

3 / 3

Total

9

/

12

Passed

Description

22%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 relies heavily on naming two specific technologies (Avalonia UI, Zafiro toolkit) but fails to describe any concrete actions, capabilities, or trigger conditions. It reads more like a category label than a functional skill description, making it difficult for Claude to know when to select it or what it actually provides.

Suggestions

Add specific concrete actions the skill covers, e.g., 'Creates Avalonia UI views, configures dependency injection with Zafiro, implements MVVM patterns, sets up styling and theming.'

Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when the user is building desktop or cross-platform apps with Avalonia, mentions XAML layouts, Zafiro DI, or Avalonia controls.'

Replace vague terms like 'mandatory skills, conventions, and behavioral rules' with concrete descriptions of what rules or conventions are enforced (e.g., 'Enforces MVVM architecture, proper use of ReactiveUI bindings, and Zafiro service registration patterns').

DimensionReasoningScore

Specificity

The description mentions 'Avalonia UI development' and 'Zafiro toolkit' as the domain but lists no concrete actions—only vague terms like 'skills, conventions, and behavioral rules' which are abstract and non-specific.

1 / 3

Completeness

The description vaguely addresses 'what' (conventions and rules for Avalonia/Zafiro) but provides no explicit 'when' clause or trigger guidance. The 'what' itself is also very weak—'mandatory skills, conventions, and behavioral rules' doesn't explain what the skill actually does.

1 / 3

Trigger Term Quality

It includes 'Avalonia UI' and 'Zafiro toolkit' which are relevant domain-specific keywords a user might mention, but lacks common variations or natural phrases like 'XAML', 'desktop app', 'cross-platform UI', or specific task-related terms.

2 / 3

Distinctiveness Conflict Risk

The mention of 'Avalonia UI' and 'Zafiro toolkit' provides some distinctiveness since these are specific technologies, but the vague framing as 'conventions and behavioral rules' could overlap with any general coding standards or UI development skill.

2 / 3

Total

6

/

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.