CtrlK
BlogDocsLog inGet started
Tessl Logo

avalonia-zafiro-development

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

71

2.44x
Quality

60%

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

67%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 concise, well-organized overview that signals progressive disclosure cleanly, but it carries little actionable detail itself and relies entirely on guide files that are not included in the bundle.

Suggestions

Add at least one short, executable example inline (e.g. a DynamicData pipeline snippet or a Result-type usage) so the skill is actionable without the missing guide files.

Replace the tautological "When to Use" line with concrete trigger conditions for when this skill should apply.

Ensure the referenced guide files (core-technical-skills.md, naming-standards.md, avalonia-reactive-rules.md, zafiro-shortcuts.md, patterns.md) are present in the bundle so the navigation is not broken.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with bullet-style pillars and a short procedure; the only padding is the tautological "When to Use" line ('applicable to execute the workflow or actions described in the overview'), matching 'efficient; minor instances of over-explanation'; not a 5 because of that filler.

4 / 5

Actionability

It states concrete rules (use DynamicData operators over plain Rx, Avalonia-independent ViewModels, Result types for errors) but provides no executable code or commands and delegates all detail to referenced files, fitting 'some concrete guidance but incomplete; missing key details'; not a 4 because nothing here is copy-paste actionable.

3 / 5

Workflow Clarity

"Procedure Before Writing Code" gives a clear three-step sequence (search, propose reusable extensions, build reactive pipelines); this is non-destructive so validation checkpoints are not required, matching 'clear sequence with most checkpoints present; minor validation gaps'; not a 5 because there is no guidance for edge cases like 'where applicable' or what to do when search finds nothing.

4 / 5

Progressive Disclosure

The Guides section is a clean overview with one-level-deep links, each given a one-line description, which is well-signaled navigation; it is not a 5 because the referenced guide files (core-technical-skills.md, naming-standards.md, etc.) are not present in the bundle, so the detailed content the skill depends on is effectively dangling.

4 / 5

Total

15

/

20

Passed

Description

52%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 targets a clear niche, but it describes the skill's nature rather than concrete actions and omits any explicit trigger guidance, which limits specificity and completeness.

Suggestions

Add concrete actions, e.g. 'Build cross-platform Avalonia UI apps with the Zafiro toolkit: structure ViewModels with DynamicData/ReactiveUI, handle errors via Result types, and reuse Zafiro helpers.'

Append an explicit trigger clause such as 'Use when developing Avalonia UI applications with the Zafiro toolkit, or when the user mentions Avalonia, Zafiro, ReactiveUI, or DynamicData.'

Include natural synonyms/file cues (MVVM, ReactiveUI, DynamicData, .axaml) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

It names the domain ("Avalonia UI", "Zafiro toolkit") but only describes the skill's contents ("skills, conventions, and behavioral rules") rather than concrete actions, matching the score-2 anchor 'names the domain but actions are minimal or generic'; it is not a 3 because no specific actions are listed.

2 / 5

Completeness

There is a clear "what" (a conventions/behavioral-rules skill), but no "Use when..." trigger clause, which per the judging guidelines caps completeness at 3; not a 4 because the 'when' is entirely missing rather than merely imprecise.

3 / 5

Trigger Term Quality

"Avalonia UI development" and "Zafiro toolkit" are relevant keywords a user would say, but common variations (MVVM, ReactiveUI, DynamicData) are absent, fitting 'some relevant keywords but missing common variations or synonyms'; not a 4 because coverage is thin rather than merely a few terms short.

3 / 5

Distinctiveness Conflict Risk

"Avalonia UI development using the Zafiro toolkit" carves out a clear niche with distinct triggers and minimal overlap with other skills, matching the score-5 anchor.

5 / 5

Total

13

/

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: 5 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.