avalonia-zafiro-development

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

50%

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-organized and avoids explaining known concepts, but it relies on abstract directives with no concrete examples and its referenced guide files do not exist in the bundle. It functions as a signpost rather than actionable guidance.

Suggestions

Add concrete, executable guidance — e.g., short code snippets showing a Zafiro Result pattern, a DynamicData operator, or a reusable extension method — instead of abstract directives.

Either supply the referenced guide files (core-technical-skills.md, naming-standards.md, avalonia-reactive-rules.md, zafiro-shortcuts.md, patterns.md) in the bundle or remove the dead links, since all five are currently missing.

Trim the generic "When to Use" and "Limitations" boilerplate and replace it with skill-specific criteria, or remove it to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The Core Pillars and Guides are lean and do not over-explain known concepts, but the generic "When to Use" ("applicable to execute the workflow or actions described in the overview") and boilerplate "Limitations" sections add tokens that do not earn their place.	2 / 3
Actionability	Guidance is directive but abstract ("Search the codebase for similar implementations", "propose a new reusable extension method", "Ensure DynamicData operators are used") with no concrete code, commands, or examples, so it is incomplete rather than fully executable.	2 / 3
Workflow Clarity	"Procedure Before Writing Code" lists a sequenced 1-2-3 process, but the steps are vague and lack any validation checkpoint or feedback loop, matching the steps-present-but-checkpoints-missing anchor.	2 / 3
Progressive Disclosure	The "Guides" section is well-signaled with one-level-deep links and descriptions, but every referenced file (core-technical-skills.md, naming-standards.md, etc.) is absent from the bundle, so the disclosure structure does not resolve to real content.	2 / 3
	Total	8 / 12 Passed

Description

57%

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 identifies a clear, distinctive niche but relies on abstract language and omits an explicit "Use when..." trigger, leaving completeness and trigger-term coverage mid-tier. It is solid but not exemplary.

Suggestions

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

Replace abstract phrasing ("Mandatory skills, conventions, and behavioral rules") with concrete actions the skill performs (e.g., "enforces naming, error-handling, and reactive-pipeline conventions").

Broaden trigger terms to include natural variations users would say, such as cross-platform UI, ReactiveUI, and DynamicData, not just "Avalonia UI" and "Zafiro".

Dimension	Reasoning	Score
Specificity	Names the domain clearly ("Avalonia UI development using the Zafiro toolkit") but the actions are abstract ("Mandatory skills, conventions, and behavioral rules") rather than concrete tasks, so it stops at domain-plus-some-actions.	2 / 3
Completeness	It states what the skill provides (conventions/rules for Avalonia+Zafiro development) but has no "Use when..." clause or explicit trigger guidance, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	"Avalonia UI" and "Zafiro toolkit" are relevant niche keywords a user would say, but common variations like cross-platform, ReactiveUI, or DynamicData are missing.	2 / 3
Distinctiveness Conflict Risk	The Avalonia-UI-plus-Zafiro niche is highly specific and unlikely to trigger for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	9 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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: boisenoise/skills-collections
Commit: f36337d

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.