CtrlK
BlogDocsLog inGet started
Tessl Logo

avalonia-zafiro-development

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

67

2.44x
Quality

53%

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%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 well-structured and concise as an overview, with clear navigation to sub-guides, but it offers only high-level procedural guidance without concrete examples or validation steps, and every referenced guide file is absent from the bundle.

Suggestions

Add the missing referenced guide files (core-technical-skills.md, naming-standards.md, avalonia-reactive-rules.md, zafiro-shortcuts.md, patterns.md) or remove the dead links so navigation resolves.

Include at least one concrete, executable example in the procedure (e.g., a minimal DynamicData pipeline snippet or a Result-type usage) to lift actionability.

Add a validation checkpoint to the pre-code workflow (e.g., 'Confirm no existing Zafiro helper covers this before proposing a new extension') so the sequence has an explicit gate.

DimensionReasoningScore

Conciseness

The body is largely lean (terse Core Pillars, a Guides list, a short procedure) and avoids explaining concepts Claude already knows, with only minor padding such as 'These rules prioritize maintainability, correctness, and a functional-reactive approach', matching 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

The procedure gives directional steps ('Search the codebase for similar implementations', 'propose a new reusable extension method', 'Ensure DynamicData operators are used') but no concrete code, commands, or specific examples, fitting 'some concrete guidance but incomplete; missing key details'.

3 / 5

Workflow Clarity

The 'Procedure Before Writing Code' is a sequenced 3-step list, but there are no validation checkpoints or feedback loops, matching 'steps listed but validation gaps; checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The Guides section clearly signals one-level-deep references with labeled links, but the referenced files (core-technical-skills.md, naming-standards.md, avalonia-reactive-rules.md, zafiro-shortcuts.md, patterns.md) are not present in the bundle, so the navigation points to missing material, capping the score at 3.

3 / 5

Total

13

/

20

Passed

Description

48%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 identifies a narrow niche (Avalonia UI with the Zafiro toolkit) but is abstract about actions and omits any explicit trigger/Use-when guidance, capping completeness. It is distinguishable yet not maximally trigger-friendly.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when building or modifying Avalonia UI apps with the Zafiro toolkit, ReactiveUI, or DynamicData pipelines').

Replace the abstract 'skills, conventions, and behavioral rules' framing with 2-3 concrete actions the skill drives (e.g., 'structure ViewModels, wire reactive pipelines, reuse Zafiro helpers').

Include natural synonyms users say (Avalonia, Zafiro, MVVM, ReactiveUI, DynamicData, cross-platform) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Avalonia UI development using the Zafiro toolkit") but lists no concrete actions, describing what the skill contains ("skills, conventions, and behavioral rules") rather than what it does, matching the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

It gives a clear-ish 'what' (mandatory conventions and rules for Avalonia/Zafiro development) but entirely lacks a 'when'/Use-when clause, so per the missing-trigger-guidance cap completeness cannot exceed 3.

3 / 5

Trigger Term Quality

It includes relevant niche terms a user would say ("Avalonia UI", "Zafiro toolkit", "development") but misses common variations/synonyms that appear in the body (MVVM, ReactiveUI, DynamicData, cross-platform), fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The Avalonia-plus-Zafiro-toolkit niche is fairly distinct with limited overlap risk against generic skills, though the generic word 'development' leaves minor overlap with broad coding skills, matching 'mostly distinct; minor overlap risk'.

4 / 5

Total

12

/

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.