avalonia-zafiro-development
tessl i github:sickn33/antigravity-awesome-skills --skill avalonia-zafiro-developmentMandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.
Validation
75%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 12 / 16 Passed | |
Implementation
73%This is a well-structured skill that excels at progressive disclosure and conciseness, serving as an effective index to detailed guides. However, it lacks concrete code examples demonstrating the 'Core Pillars' and the workflow section could benefit from explicit validation steps to verify adherence to the conventions.
Suggestions
Add a brief executable code snippet demonstrating one of the Core Pillars (e.g., a minimal DynamicData pipeline or Result type usage) to improve actionability
Add a validation step to the procedure, such as 'Verify your implementation follows the patterns in patterns.md before committing'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting only essential information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | The skill provides clear procedural guidance in the 'Procedure Before Writing Code' section, but lacks concrete code examples or executable commands. The guidance is specific but abstract rather than copy-paste ready. | 2 / 3 |
Workflow Clarity | The 3-step procedure is clearly sequenced, but lacks validation checkpoints or feedback loops. For a skill governing development practices, there's no explicit verification step to confirm compliance with the rules. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and well-signaled one-level-deep references to detailed guides. The navigation is clear with descriptive link text explaining what each referenced file contains. | 3 / 3 |
Total | 10 / 12 Passed |
Activation
22%This description is too abstract and lacks actionable detail. While it identifies the technology stack (Avalonia UI, Zafiro), it fails to specify concrete capabilities or provide explicit trigger conditions for when Claude should use this skill. The phrase 'mandatory skills, conventions, and behavioral rules' describes meta-information about the skill rather than what it actually helps accomplish.
Suggestions
Replace abstract terms with concrete actions (e.g., 'Creates Avalonia views, implements MVVM patterns, configures Zafiro styling and navigation').
Add an explicit 'Use when...' clause with trigger terms like 'Avalonia', 'Zafiro', 'cross-platform desktop UI', 'XAML views', or '.axaml files'.
Specify the scope more clearly to distinguish from general UI or .NET development skills (e.g., mention specific Zafiro features like dependency injection setup or theme configuration).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract language like 'skills, conventions, and behavioral rules' without listing any concrete actions. It doesn't specify what Claude actually does (e.g., 'create views', 'implement MVVM patterns', 'style components'). | 1 / 3 |
Completeness | The description vaguely addresses 'what' (rules for Avalonia/Zafiro development) but provides no 'when' clause or explicit triggers. There's no guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes domain-specific terms 'Avalonia UI' and 'Zafiro toolkit' which users familiar with these technologies would mention, but lacks common variations or related terms users might say (e.g., 'cross-platform UI', 'XAML', 'desktop app'). | 2 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'Avalonia UI' and 'Zafiro toolkit' provides some distinctiveness, but 'development' is generic and could overlap with other coding or UI development skills. | 2 / 3 |
Total | 6 / 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.