avalonia-layout-zafiro

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

Quality

30%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

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 + Zafiro.Avalonia) which helps with distinctiveness, but it reads more like a summary of design principles than an actionable skill description. It lacks concrete actions, explicit trigger conditions, and a 'Use when...' clause, making it difficult for Claude to reliably select this skill at the right time.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user is building Avalonia UI views, working with .axaml files, or asking about Zafiro.Avalonia styling and layout.'

List specific concrete actions the skill covers, such as 'Creates reusable control templates, defines shared resource dictionaries, structures view hierarchies, and applies Zafiro theme styles.'

Include additional natural trigger terms users might say, such as '.axaml', 'desktop app UI', 'Avalonia controls', 'data templates', or 'cross-platform 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 'build responsive layouts'.	2 / 3
Completeness	The description addresses '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 the rubric, a missing 'Use when...' clause 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', 'Zafiro.Avalonia', 'XAML', 'layout', 'styles', and 'generic components' which users might mention. However, it misses common variations like '.axaml', 'UI controls', 'data templates', 'styling', or 'desktop app UI'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Zafiro.Avalonia' specifically is fairly distinctive and narrows the niche, but 'UI layout', 'shared styles', and 'generic components' are broad enough to potentially overlap with other UI framework skills. The Zafiro.Avalonia reference prevents a score of 1.	2 / 3
	Total	7 / 12 Passed

Implementation

27%

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

This skill is essentially a table of contents pointing to supporting files that don't exist in the bundle, with a checklist and anti-patterns list that lack concrete examples. The absence of any executable code, XAML snippets, or specific implementation guidance makes it largely non-actionable. The structure is reasonable but the content is too thin to be useful on its own.

Suggestions

Add at least one concrete XAML example for each key concept (e.g., show a HeaderedContainer usage vs. the anti-pattern Border approach, show an EdgePanel layout vs. nested Grid/StackPanel).

Include the referenced bundle files (themes.md, containers.md, icons.md, behaviors.md, components.md) or inline the essential content from them into the SKILL.md.

Replace the generic 'When to Use' and 'Limitations' boilerplate sections with specific scope boundaries relevant to Avalonia/Zafiro development.

Add a concrete quick-start workflow showing how to set up a new view from scratch using the recommended patterns, with validation steps (e.g., checking that DynamicResources resolve correctly).

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	The checklist provides a reasonable sequence of considerations for building clean layouts, and the anti-patterns section gives clear do/don't guidance. However, there's no step-by-step workflow for actually creating a layout, and no validation checkpoints for verifying correctness.	2 / 3
Progressive Disclosure	The content map references five supporting files (themes.md, containers.md, icons.md, behaviors.md, components.md) but no bundle files are provided, meaning all referenced paths are broken. The SKILL.md itself contains almost no substantive content, delegating everything to non-existent files.	1 / 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: boisenoise/skills-collections
Commit: 431bfad

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.