avalonia-layout-zafiro
tessl i github:sickn33/antigravity-awesome-skills --skill avalonia-layout-zafiroGuidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy.
61%
Overall
Validation
Implementation
Activation
Validation
63%| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md line count is 60 (<= 500) | Pass |
frontmatter_valid | YAML frontmatter is valid | Pass |
name_field | 'name' field is valid: 'avalonia-layout-zafiro' | Pass |
description_field | 'description' field is valid (140 chars) | Pass |
description_voice | 'description' uses third person voice | Pass |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
compatibility_field | 'compatibility' field not present (optional) | Pass |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
metadata_field | 'metadata' field not present (optional) | Pass |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | No unknown frontmatter keys found | Pass |
body_present | SKILL.md body is present | Pass |
body_examples | Examples detected (code fence or 'Example' wording) | Pass |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 10 / 16 Passed |
Implementation
73%This skill excels at organization and conciseness, providing a well-structured overview with clear navigation to detailed documentation. However, it lacks concrete executable XAML examples that would make the guidance immediately actionable. The checklist and anti-patterns are valuable but would benefit from before/after code snippets.
Suggestions
- Add concrete XAML code examples showing correct usage of `HeaderedContainer`, `EdgePanel`, and `IconExtension` - even brief snippets would significantly improve actionability
- Include a minimal 'Quick Start' example showing a complete small layout using the recommended patterns
- Add a before/after code comparison for at least one anti-pattern to make the guidance more concrete
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and checklists to convey information without unnecessary explanation. It assumes Claude knows Avalonia basics and focuses only on Zafiro-specific guidance. | 3 / 3 |
Actionability | Provides clear guidance through checklists and anti-patterns, but lacks concrete executable code examples. The syntax hints like `{Icon fa-name}` are helpful but incomplete without full XAML snippets showing actual usage. | 2 / 3 |
Workflow Clarity | The checklist provides a sequence of considerations, but there's no explicit workflow for creating a layout from scratch. For a layout skill, step-by-step guidance with validation checkpoints would strengthen this. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear content map table directing readers to specific files based on their needs. The selective reading rule and one-level-deep references to themed documentation files demonstrate ideal progressive disclosure. | 3 / 3 |
Total | 10 / 12 Passed |
Activation
33%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 a 'Use when...' clause with explicit triggers like 'Use when building Avalonia desktop applications, working with .axaml files, or implementing Zafiro.Avalonia components'
- List specific concrete actions such as 'Create reusable styles, build generic DataTemplates, structure ViewModels, implement responsive layouts'
- Include natural keyword variations users might say: 'desktop app UI', 'cross-platform .NET UI', 'MVVM layout', '.axaml 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 (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 |
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.