CtrlK
BlogDocsLog inGet started
Tessl Logo

avalonia-layout-zafiro

Guidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy.

71

1.22x
Quality

61%

Does it follow best practices?

Impact

86%

1.22x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/avalonia-layout-zafiro/SKILL.md

The canonical home for this skill is avalonia-layout-zafiro in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-organized with a useful content map and concrete checklist, but it lacks any executable examples and references five bundle files that are not present, undermining both actionability and progressive disclosure. Supplying the missing reference files or inlining their key guidance would most improve the score.

Suggestions

Provide the referenced bundle files (themes.md, containers.md, icons.md, behaviors.md, components.md) or inline their essential guidance so the content map does not dead-end.

Add at least one executable axaml snippet per topic (e.g. a HeaderedContainer/EdgePanel example and an {Icon} usage) so guidance is copy-paste ready.

Replace the tautological "When to Use" line with concrete trigger conditions, and add a short sequenced workflow (identify challenge -> read relevant file -> apply checklist -> verify against anti-patterns).

DimensionReasoningScore

Conciseness

The body is lean checklists and a content map with no padding about what Avalonia is; only minor trim is possible (the tautological "When to Use" line and emoji headers).

4 / 5

Actionability

Names concrete components and patterns (HeaderedContainer, EdgePanel, {Icon fa-name}, IconOptions, DynamicResource, Interaction.Behaviors) but provides no executable axaml/code examples, and the referenced detail files (themes.md, etc.) do not exist.

3 / 5

Workflow Clarity

No explicitly sequenced multi-step workflow; the content map's "When to Read" gives a loose decision flow and the checklist/anti-patterns imply a process, but checkpoints are not explicit.

3 / 5

Progressive Disclosure

The content map is well-signaled and one level deep, but the five referenced files (themes.md, containers.md, icons.md, behaviors.md, components.md) are absent, leaving dangling references that break navigation.

3 / 5

Total

13

/

20

Passed

Description

65%Weight 40%Scale 1-5

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 specific to a clear niche and carries good trigger terms, but it states what the guidelines emphasize rather than what Claude does, and omits an explicit "Use when..." trigger clause. Adding a concrete when-to-use clause and action verbs would lift completeness and specificity.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when building or refactoring Avalonia UI layouts with Zafiro.Avalonia, organizing themes, or reducing XAML duplication."

Reframe as concrete actions in third person, e.g. "Structures Avalonia views with semantic containers, shared styles, and generic components to reduce XAML redundancy."

Add natural trigger synonyms such as "axaml", "views", and "UserControl" to broaden keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ("modern Avalonia UI layout using Zafiro.Avalonia") and concrete emphases ("shared styles, generic components, and avoiding XAML redundancy"), but frames them as guidelines rather than listing multiple concrete actions Claude performs.

3 / 5

Completeness

Gives a clear "what" (guidelines for Avalonia/Zafiro layout) but no "Use when..." trigger clause, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms a user would say ("Avalonia UI", "layout", "XAML", "Zafiro.Avalonia", "shared styles"); a few natural variants ("axaml", "view") are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear, narrow niche (Avalonia UI layout via the specific Zafiro.Avalonia library) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.