avalonia-layout-zafiro

Guidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy.

1.22x

Quality

52%

Does it follow best practices?

Impact

86%

1.22x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-avalonia-layout-zafiro/SKILL.md

Quality

Discovery

32%

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 specific technology stack (Avalonia with Zafiro.Avalonia) and mentions key concepts, but reads more like a topic summary than actionable skill guidance. It lacks explicit trigger conditions and concrete actions, making it difficult for Claude to know precisely when to select this skill over other UI-related skills.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when building Avalonia desktop applications, working with .axaml files, or when the user mentions Zafiro, Avalonia styling, or cross-platform .NET UI'.

Replace 'Guidelines for' with concrete actions like 'Creates Avalonia UI layouts, defines reusable styles, builds generic components using Zafiro.Avalonia patterns'.

Include common user terms and file extensions like '.axaml', 'desktop app UI', 'cross-platform .NET', or 'MVVM layout' to improve trigger matching.

Dimension	Reasoning	Score
Specificity	Names the domain (Avalonia UI layout) and mentions some concepts (shared styles, generic components, avoiding XAML redundancy), but doesn't list concrete actions like 'create layouts', 'define styles', or 'build components'.	2 / 3
Completeness	Describes what the skill covers (guidelines for Avalonia UI layout) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant technical terms like 'Avalonia', 'Zafiro.Avalonia', 'XAML', and 'UI layout', but missing common variations users might say like '.axaml', 'desktop app', 'cross-platform UI', or 'WPF-like'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Zafiro.Avalonia' specifically adds some distinctiveness, but 'UI layout' and 'shared styles' are generic enough to potentially overlap with other UI framework skills.	2 / 3
	Total	7 / 12 Passed

Implementation

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill excels at organization and progressive disclosure with its clear content map and selective reading guidance. However, it functions more as a reference checklist than an actionable guide, lacking concrete XAML code examples that would make it immediately executable. The anti-patterns section is valuable but would benefit from before/after code snippets.

Suggestions

Add concrete XAML code examples showing proper usage of `HeaderedContainer`, `EdgePanel`, and `IconExtension` syntax

Include a before/after code comparison for at least one anti-pattern to make the guidance more actionable

Add a brief 'Quick Start' section with a minimal complete example of a clean layout using the recommended patterns

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, using tables, checklists, and bullet points without explaining concepts Claude already knows. Every section serves a clear purpose with no padding.	3 / 3
Actionability	Provides good guidance through checklists and anti-patterns, but lacks concrete executable code examples. References like `{Icon fa-name}` hint at syntax but don't show complete, copy-paste ready XAML snippets.	2 / 3
Workflow Clarity	The checklist provides a sequence of considerations, but there's no explicit step-by-step workflow for creating layouts. It's more of a reference guide than a procedural workflow with validation checkpoints.	2 / 3
Progressive Disclosure	Excellent structure with a clear content map table showing exactly when to read each referenced file. References are one level deep and well-signaled with descriptions and use cases.	3 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: boisenoise/skills-collections
Commit: 5c5ae21

Reviewed: 3 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.