avalonia-zafiro-development
Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.
48
36%
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 ./skills/antigravity-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 is too vague and abstract, failing to specify what concrete actions the skill performs or when Claude should select it. While the mention of 'Avalonia UI' and 'Zafiro toolkit' provides some domain specificity, the lack of concrete capabilities and explicit trigger conditions makes it difficult for Claude to reliably choose this skill from a pool of alternatives.
Suggestions
Add specific concrete actions the skill covers, e.g., 'Enforces MVVM patterns, configures dependency injection, applies Zafiro conventions for view models, services, and navigation in Avalonia UI projects.'
Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when developing Avalonia UI applications with the Zafiro toolkit, or when the user mentions Avalonia, Zafiro, XAML, cross-platform desktop UI, or .NET UI frameworks.'
Clarify what 'mandatory rules and conventions' entails — list the key areas covered (e.g., project structure, naming conventions, control styling, data binding patterns) to help distinguish this from generic Avalonia skills.
| 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 ('mandatory skills, conventions, and behavioral rules') and there is no explicit 'when' clause or trigger guidance. Both components 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. However, it lacks common variations or natural phrases users would say (e.g., 'XAML', 'cross-platform UI', 'desktop app', 'MVVM', specific Zafiro features). | 2 / 3 |
Distinctiveness Conflict Risk | 'Avalonia UI' and 'Zafiro toolkit' provide some distinctiveness from generic UI or coding skills, but the lack of specific actions means it could overlap with any general Avalonia or UI development 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 serves as a reasonable overview/index page for Avalonia Zafiro development conventions, with clear references to detailed guides. However, it lacks concrete, executable examples and relies heavily on abstract principles and generic boilerplate sections ('When to Use', 'Limitations') that don't add actionable value. The pre-coding procedure is a good idea but needs validation steps and more specificity.
Suggestions
Add at least one concrete, executable code example demonstrating a core pattern (e.g., a minimal DynamicData reactive pipeline or a Result-type error handling snippet) to improve actionability.
Remove or significantly trim the generic 'When to Use' and 'Limitations' sections, which are boilerplate that doesn't add skill-specific value.
Add a validation checkpoint to the 'Procedure Before Writing Code' workflow, such as 'Confirm with the user if no existing helper is found before creating a new one' to create a proper feedback loop.
Include the bundle files (core-technical-skills.md, naming-standards.md, etc.) so the progressive disclosure structure can be fully realized and verified.
| 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 contains boilerplate sections that could be trimmed rather than kept inline. | 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
- boisenoise/skills-collections
- Commit
431bfad
- 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.