avalonia-layout-zafiro
Guidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy.
58
41%
Does it follow best practices?
Impact
86%
1.22xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-avalonia-layout-zafiro/SKILL.mdQuality
Discovery
40%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 and distinctive technology niche (Avalonia UI with Zafiro.Avalonia) which helps differentiation, but it reads more like a topic label than an actionable skill description. It lacks explicit trigger guidance ('Use when...') and concrete actions, making it harder for Claude to know precisely when to select this skill or what specific tasks it enables.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when building or modifying Avalonia UI views, creating XAML layouts, or working with .axaml files in projects using Zafiro.Avalonia.'
Replace 'Guidelines for' with specific concrete actions, e.g., 'Creates and refactors Avalonia UI layouts, defines reusable styles and control templates, configures Zafiro.Avalonia themes, and eliminates XAML redundancy through shared resources.'
Add common trigger term variations such as '.axaml', 'desktop UI', 'cross-platform', 'control templates', 'theming', and 'data templates' to improve keyword coverage.
| 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 (guidelines for Avalonia UI layout) but has no explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is entirely missing, which per the rubric should cap completeness at 2, and since the 'what' is also somewhat vague ('guidelines' rather than concrete actions), 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 framework', 'desktop app', 'cross-platform UI', or 'theming'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Avalonia UI', 'Zafiro.Avalonia', and 'XAML' creates a very specific niche that is unlikely to conflict with other skills. This is a clearly distinct technology stack. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at progressive disclosure with a well-organized content map and clear navigation to sub-files. However, it critically lacks actionability—there are no concrete XAML examples, no executable code snippets, and no specific implementation patterns. The content reads more like a table of contents with guidelines than an actionable skill that Claude can follow to produce correct output.
Suggestions
Add at least 2-3 concrete XAML code examples showing correct usage of key patterns (e.g., HeaderedContainer, EdgePanel, Icon extension, shared styles) so Claude can produce copy-paste-ready code.
Replace the vague 'When to Use' section with a minimal working example showing a before/after comparison of a layout refactored using these guidelines.
Add a brief step-by-step workflow for creating a new view (e.g., 1. Define styles in theme file, 2. Choose semantic container, 3. Add content, 4. Verify no anti-patterns) with concrete validation criteria.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some filler like the 'Selective Reading Rule' banner, emoji decorations, and the vague 'When to Use' section at the end that adds no value. The checklist and anti-patterns are reasonably tight. | 2 / 3 |
Actionability | No concrete code examples, no executable XAML snippets, no specific commands. Everything is described at a high level ('Use semantic containers', 'Use {Icon fa-name}') without showing actual implementation. The skill tells Claude what to do but never shows how. | 1 / 3 |
Workflow Clarity | The checklist provides a reasonable sequence of considerations for building layouts, and the anti-patterns give useful guardrails. However, there's no step-by-step workflow for creating a layout, no validation steps, and no feedback loop for checking correctness. | 2 / 3 |
Progressive Disclosure | Excellent content map table with clear file references, descriptions, and 'When to Read' guidance. References are one level deep and well-signaled. The overview is concise and points to detailed materials appropriately. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
90%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
f1697b6
- 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.