avalonia-zafiro-development
Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.
38
36%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/avalonia-zafiro-development/SKILL.mdQuality
Discovery
22%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 narrow technology domain (Avalonia UI + Zafiro toolkit) but fails to specify any concrete actions or explicit trigger conditions. It reads more like a category label than a functional skill description, making it difficult for Claude to know precisely when to select it over other skills.
Suggestions
Add concrete actions the skill covers, e.g., 'Enforces naming conventions, project structure, MVVM patterns, and XAML best practices for Avalonia UI projects using the Zafiro toolkit.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user is building or modifying an Avalonia UI application with the Zafiro toolkit, or asks about Avalonia conventions, controls, or project setup.'
Include natural trigger terms users might say, such as 'Avalonia', 'Zafiro', 'XAML', 'cross-platform desktop', 'MVVM', '.axaml' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'Avalonia UI development' and 'Zafiro toolkit' as domain identifiers, but does not list any concrete actions. Terms like 'skills, conventions, and behavioral rules' are abstract and do not describe what the skill actually does. | 1 / 3 |
Completeness | The 'what' is extremely vague ('skills, conventions, and behavioral rules') and there is no explicit 'when' clause or trigger guidance. Both dimensions are weak or missing. | 1 / 3 |
Trigger Term Quality | It includes 'Avalonia UI' and 'Zafiro toolkit' which are relevant domain-specific keywords a user might mention, but lacks common variations or natural phrases users would say (e.g., 'XAML', 'cross-platform UI', 'desktop app', 'MVVM', specific file types). | 2 / 3 |
Distinctiveness Conflict Risk | 'Avalonia UI' and 'Zafiro toolkit' provide some distinctiveness from generic UI or coding skills, but the description is so vague that it could overlap with any Avalonia-related skill or general UI development conventions skill. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as a table of contents pointing to detailed guides, which is a reasonable structural choice but leaves the SKILL.md itself with limited standalone actionability. The content includes some generic boilerplate ('When to Use', 'Limitations') that doesn't add value, and the core pillars are abstract principles rather than concrete instructions. The referenced guides likely contain the real substance, but without bundle files to verify, the skill body alone provides limited executable guidance.
Suggestions
Add at least one concrete, executable code example in the SKILL.md itself (e.g., a minimal ViewModel setup using Zafiro + ReactiveUI + DynamicData) to make the overview actionable on its own.
Remove or significantly trim the generic 'When to Use' and 'Limitations' sections — these are boilerplate that Claude doesn't need and waste tokens.
Add a validation checkpoint to the 'Procedure Before Writing Code' workflow, e.g., 'Confirm with the user that no existing helper was found before creating a new one' to create a proper feedback loop.
Replace the abstract 'Core Pillars' descriptions with brief, concrete rules (e.g., 'Never throw exceptions for expected failures — return Result<T> instead' rather than 'Explicit error handling with Result types').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary sections like 'When to Use' and 'Limitations' that are generic boilerplate adding little value. The 'Core Pillars' section is somewhat descriptive rather than instructive, and phrases like 'This skill defines the mandatory conventions...' are filler. | 2 / 3 |
Actionability | The 'Procedure Before Writing Code' section provides some concrete guidance (search first, propose extensions, use DynamicData operators), but lacks executable examples, specific commands, or concrete code snippets. The core pillars are abstract principles rather than actionable instructions. | 2 / 3 |
Workflow Clarity | The 3-step procedure before writing code provides a basic sequence but lacks validation checkpoints or feedback loops. There's no explicit verification step (e.g., 'confirm no existing helper exists before proceeding') and no error recovery guidance if steps fail. | 2 / 3 |
Progressive Disclosure | The Guides section provides well-signaled one-level-deep references to five separate files, which is good structure. However, since no bundle files were provided, we cannot verify these references exist or contain meaningful content, and the skill itself is thin — it's essentially just a table of contents with minimal standalone value. | 2 / 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
- sickn33/antigravity-awesome-skills
- Commit
8854d4e
- 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.