Name: avalonia-ui-setup
Rating: 49.6 (1 reviews)
Author: trackdubllc

Blog Docs Log in Get started

avalonia-ui-setup

Set up Avalonia UI project with cross-platform XAML for Windows, macOS, and Linux

Quality

54%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/avalonia-ui-setup/SKILL.md

The canonical home for this skill is avalonia-ui-setup in trackdubllc/Babel-Player-Alpha

Quality

Content

55%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 well-structured and concise, but it describes capabilities rather than providing the executable scaffolding/config/build commands a setup skill needs, and it lacks a sequenced workflow with validation checkpoints.

Suggestions

Add the actual scaffolding and config commands (e.g. `dotnet new avalonia.app`, ReactiveUI/MVVM package references, theme setup, `dotnet publish` per platform) so the guidance is copy-paste executable.

Present setup as an explicit numbered workflow (scaffold → configure MVVM → theme → build → verify) with a build/run verification checkpoint.

Tighten the intro sentence to avoid restating the description's marketing framing ('true cross-platform desktop development... with a single codebase').

Dimension	Reasoning	Score
Conciseness	The body is efficient with short capability bullets, a schema, a tree, and one XAML snippet, assuming Claude's competence; only minor trimming is needed (the intro sentence repeats the description with mild marketing flavor), so anchor 4 rather than 5.	4 / 5
Actionability	Concrete artifacts exist (input schema, project tree, one executable MainWindow.axaml) but the core setup actions (scaffolding commands, MVVM/ReactiveUI config, theme config, build/publish commands) are only described as bullets, not given as executable guidance, matching anchor 3's 'some concrete guidance but incomplete'.	3 / 5
Workflow Clarity	There is no explicit sequenced workflow — only a capabilities bullet list giving a rough implicit order — and no validation/verification checkpoints for the multi-step setup, fitting anchor 2's 'rough sequence present but many gaps; validation absent'; not a 3 because no steps are presented as a workflow.	2 / 5
Progressive Disclosure	The skill is self-contained (no bundle files exist) and well-organized into clear sections, fitting anchor 4; it is not a 5 because it sits slightly over the 50-line simple-skill threshold and all content is inline with no reference structure.	4 / 5
	Total	13 / 20 Passed

Description

53%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 clearly states what the skill does but omits any 'when to use it' trigger guidance, which caps completeness. Trigger terms are relevant but technical rather than natural user phrasing.

Suggestions

Add a 'Use when...' clause naming natural user triggers, e.g. 'Use when creating an Avalonia desktop app or scaffolding cross-platform XAML for Windows, macOS, and Linux.'

Broaden trigger terms with natural synonyms users would say (e.g. 'Avalonia app', '.axaml', 'desktop app') rather than only technical jargon.

Add a second concrete action (e.g. 'scaffold, configure MVVM, and publish') to lift specificity toward a 4.

Dimension	Reasoning	Score
Specificity	Names the domain (Avalonia UI, cross-platform XAML) and one concrete action ('Set up... project'), matching anchor 3's '1-2 concrete actions'; it is not a 4 because only a single action is given rather than several.	3 / 5
Completeness	A clear 'what' is stated but 'when' trigger guidance is entirely absent, so per the guideline completeness is capped at 3, matching anchor 3 exactly.	3 / 5
Trigger Term Quality	Relevant domain terms ('Avalonia UI', 'cross-platform XAML', platform names) are present but jargon-heavy with no 'Use when...' phrasing or natural synonyms, fitting anchor 3's 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	'Avalonia UI' with cross-platform framing is a mostly distinct niche with only minor overlap risk against the related wpf-xaml-style-generator; not a 5 because no explicit trigger disambiguates it from WPF.	4 / 5
	Total	13 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: trackdubllc/Babel-Player-Alpha
Path: .codex/skills/avalonia-ui-setup/SKILL.md
Commit: 2237ca2

Reviewed: 7 hours ago

Table of Contents

Discovery Implementation Validation

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.