avalonia-layout-zafiro
Guidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy.
60
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/avalonia-layout-zafiro/SKILL.mdQuality
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 hints at its purpose, but lacks concrete actions and completely omits trigger guidance. Without a 'Use when...' clause, Claude cannot reliably determine when to select this skill from a larger skill set.
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 XAML UI'.
List specific concrete actions such as 'Creates reusable control templates, defines application-wide styles, structures ViewModels, builds responsive layouts'.
Include natural keyword variations users might say: 'desktop app', 'cross-platform UI', '.axaml', 'MVVM', 'control styling'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Avalonia UI layout with Zafiro.Avalonia) and mentions some actions (shared styles, generic components, avoiding XAML redundancy), but doesn't list concrete specific 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 'WPF-like', 'cross-platform UI', '.axaml', or 'desktop app styling'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Zafiro.Avalonia' specifically helps distinguish it, 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 token efficiency, providing a well-structured overview with clear navigation to detailed content. However, it lacks concrete executable examples - the checklists and anti-patterns tell Claude what to do conceptually but don't show actual XAML code demonstrating proper Zafiro.Avalonia patterns.
Suggestions
Add 1-2 concrete XAML examples showing proper use of semantic containers like `HeaderedContainer` vs the anti-pattern `Border` approach
Include a minimal executable example of `{Icon fa-name}` with `IconOptions` styling
Add a brief workflow showing the typical sequence for creating a new view (e.g., 1. Choose container type, 2. Apply theme styles, 3. Add icons, 4. Verify no anti-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 or unnecessary context. | 3 / 3 |
Actionability | Provides clear guidance through checklists and anti-patterns, but lacks concrete code examples. References like `{Icon fa-name}` hint at syntax but no executable XAML snippets are provided to demonstrate proper usage. | 2 / 3 |
Workflow Clarity | The checklist provides a clear sequence of considerations, but there's no explicit workflow for creating layouts step-by-step. For a layout skill, a simple 'start here, then do this' sequence with validation would strengthen guidance. | 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
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- Dokhacgiakhoa/antigravity-ide
- Commit
332e58b
- 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.