avalonia-layout-zafiro

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

Quality

27%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/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 UI with Zafiro.Avalonia) which provides some distinctiveness, but it reads more like a document title than a skill description. It lacks concrete actions, explicit trigger conditions, and a 'Use when...' clause, making it difficult for Claude to reliably select this skill from a larger pool.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user is building Avalonia UI applications with Zafiro.Avalonia, creating XAML views, or asking about styling and layout in Avalonia.'

List specific concrete actions the skill covers, e.g., 'Guides creation of reusable UserControls, defines shared styles and themes, structures .axaml files, and configures Zafiro icon packs and design tokens.'

Include more natural trigger terms and file extensions users might mention, such as '.axaml', 'Avalonia styling', 'Avalonia theming', 'MVVM views', or 'cross-platform desktop UI'.

Dimension	Reasoning	Score
Specificity	Names the domain (Avalonia UI layout with Zafiro.Avalonia) and mentions some actions/concepts (shared styles, generic components, avoiding XAML redundancy), but these are more like principles than concrete actions. It doesn't list specific tasks like 'create views', 'define templates', or 'configure themes'.	2 / 3
Completeness	Describes 'what' at a high level (guidelines for Avalonia UI layout) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric rules, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Avalonia UI', 'Zafiro.Avalonia', 'XAML', 'shared styles', and 'generic components' which are terms a developer might use. However, it misses common variations like '.axaml', 'UserControl', 'styling', 'theming', 'data templates', or 'layout panels'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Zafiro.Avalonia' specifically is fairly distinctive and narrows the niche, but 'layout', 'shared styles', and 'generic components' could overlap with general UI or XAML skills. The specificity of the framework helps but the broad phrasing introduces some conflict risk.	2 / 3
	Total	7 / 12 Passed

Implementation

22%

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

This skill functions primarily as a table of contents and checklist for Avalonia UI layout with Zafiro.Avalonia, but lacks the concrete, executable guidance needed to be truly useful. It tells Claude what to do and what not to do at a high level, but never shows how with actual XAML or C# code examples. The referenced supporting files (themes.md, containers.md, etc.) are not provided in the bundle, leaving the skill as an abstract overview without substance.

Suggestions

Add concrete, executable XAML code examples for at least the most common patterns (e.g., a HeaderedContainer usage, an EdgePanel layout, an Icon extension usage) to dramatically improve actionability.

Define a clear workflow sequence for building a layout from scratch, such as: 1) Set up theme resources, 2) Choose semantic containers, 3) Apply shared styles, 4) Validate visual output — with specific commands or steps at each stage.

Provide the referenced bundle files (themes.md, containers.md, icons.md, behaviors.md, components.md) or inline the most critical content so the skill is self-contained enough to be useful.

Remove the generic 'When to Use' and 'Limitations' boilerplate sections that add no skill-specific value.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with a clean content map and checklist format, but the 'When to Use' and 'Limitations' sections are generic boilerplate that add no value. The emoji-heavy headers and 'Selective Reading Rule' add minor bloat.	2 / 3
Actionability	The skill provides no concrete code examples, no executable XAML snippets, and no specific commands. It describes what to do at a high level (use semantic containers, use shared styles) but never shows how. The checklist and anti-patterns are abstract guidance without concrete implementations.	1 / 3
Workflow Clarity	There is no sequenced workflow or multi-step process described. The checklist is a static verification list, not a workflow with steps, validation checkpoints, or feedback loops. There's no guidance on the order of operations for building a layout.	1 / 3
Progressive Disclosure	The content map table with five referenced files (themes.md, containers.md, icons.md, behaviors.md, components.md) is well-structured with clear 'When to Read' guidance. However, no bundle files are provided, so the referenced files don't actually exist, making the progressive disclosure structure hollow. The references are one-level deep and clearly signaled, which is good structurally.	2 / 3
	Total	6 / 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: sickn33/antigravity-awesome-skills
Commit: 8854d4e

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.