avalonia-layout-zafiro
Guidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy.
63
Quality
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 best practices, but lacks concrete actions and completely omits trigger guidance. Without a 'Use when...' clause, Claude cannot reliably determine when to select this skill over others.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'Avalonia project', 'Zafiro styles', '.axaml files', or 'cross-platform desktop UI'.
List specific concrete actions such as 'create reusable styles', 'build generic DataTemplates', 'structure Views and ViewModels', or 'apply Zafiro themes'.
Include common user phrases like 'desktop app UI', 'XAML styling', or 'Avalonia components' to improve trigger term coverage.
| 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 (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 files', 'desktop UI', 'cross-platform UI', or 'WPF-like'. | 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 conciseness, providing a well-structured overview with clear navigation to detailed content. However, it lacks concrete executable XAML examples that would make the guidance immediately actionable. The anti-patterns section is helpful but would benefit from before/after code comparisons.
Suggestions
Add concrete XAML code examples showing correct usage of semantic containers like HeaderedContainer and EdgePanel
Include before/after code snippets in the Anti-Patterns section to illustrate the difference between bad and good practices
Add a simple validation step or visual checklist for verifying layout correctness after implementation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and checklists to convey information quickly. No unnecessary explanations of concepts Claude would already know. | 3 / 3 |
Actionability | Provides clear guidelines and anti-patterns but lacks concrete executable code examples. The checklist items describe what to do but don't show how with actual XAML snippets. | 2 / 3 |
Workflow Clarity | The checklist provides a sequence of considerations but lacks explicit validation steps or feedback loops. For a layout skill, there's no guidance on how to verify the layout is correct. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear content map table pointing to one-level-deep references. The selective reading rule and organized file breakdown make navigation easy. | 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
3395991
- 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.