avalonia-ui-setup

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

Quality

63%

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 ./.claude/skills/avalonia-ui-setup/SKILL.md

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 a compact, well-organized reference card, but it reads as a spec rather than a runnable workflow: it lacks the scaffolding command, build/publish commands, and any ordered steps or validation. Structure and brevity are solid; actionability and workflow sequencing are the weak spots.

Suggestions

Add the executable setup commands, e.g., `dotnet new avalonia.app -n MyApp` and the NuGet/package steps for ReactiveUI and the Fluent/Simple theme, plus per-platform publish commands (dotnet publish -r win-x64/linux-x64/osx-x64).

Reframe the setup as an ordered workflow (scaffold → configure theme/MVVM → add views → build & run to verify) with an explicit validation checkpoint (e.g., 'run dotnet run and confirm the window opens before proceeding').

Replace the bare Capabilities bullet list (which duplicates description-level info) with the concrete steps themselves, or move it into the description, so the body spends its tokens on executable guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean lists and code with no explanation of concepts Claude already knows, but the opening sentence "Set up Avalonia UI project with cross-platform XAML for true cross-platform desktop development..." merely restates the frontmatter description, a minor instance of trimming-able redundancy. Not a 5 because that duplicated sentence and the bare Capabilities bullets don't each earn their place.	4 / 5
Actionability	The Input Schema, project structure tree, and MainWindow.axaml snippet are concrete, but the core 'set up' action has no executable command (no `dotnet new` scaffolding, no csproj/package references for ReactiveUI or themes) and the claimed 'platform-specific publishing' has no commands at all. Real code exists but key executable details are missing, matching anchor 3.	3 / 5
Workflow Clarity	There is no ordered sequence of setup steps — sections are reference material (schema, structure, sample XAML) rather than a workflow — and no validation checkpoints (e.g., build/run the app, verify per-platform publish) despite capabilities like batch multi-platform publishing. A rough implied order exists, but steps are poorly defined and validation is absent, matching anchor 2.	2 / 5
Progressive Disclosure	The skill is a single well-sectioned file with no bundle directories (references/, scripts/, assets/ all absent), so content is appropriately self-contained and easy to navigate. It falls just short of 5: the body is ~60 lines (above the under-50-line simple-skill exception) and the 'Related Skills' links (wpf-xaml-style-generator, cross-platform-test-matrix) are not verifiable bundle files, a minor organization gap.	4 / 5
	Total	13 / 20 Passed

Description

56%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 short and names a specific framework, but it lists only one action and provides no 'when to use' trigger clause, which the guidelines cap at 3 for completeness. Adding 1-2 more concrete actions and an explicit trigger clause would move it into the good-example range.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g., 'Use when creating a new Avalonia app, adding .axaml views, or setting up cross-platform desktop builds'.

Enumerate 2-3 more concrete actions in the description (e.g., 'scaffold projects with dotnet new, configure Fluent/Simple themes, set up ReactiveUI MVVM, publish per-platform builds') to raise specificity.

Include natural trigger synonyms users would say — '.axaml', '.NET desktop app', 'Avalonia' alone — to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Set up Avalonia UI project" names the domain but contains only a single, generic action verb; the "cross-platform XAML for Windows, macOS, and Linux" phrase adds platform detail rather than additional concrete actions. This matches anchor 2 ('Processes PDF files') better than anchor 3, which expects 1-2 distinct concrete actions.	2 / 5
Completeness	The "what" is clear ("Set up Avalonia UI project"), but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines. It is not a 2 because the "what" is specific rather than vague.	3 / 5
Trigger Term Quality	"Avalonia UI", "cross-platform XAML", and "Windows, macOS, and Linux" are natural terms a user would say when needing this skill. A few natural variations are missing (e.g., ".axaml", ".NET desktop app", "Linux desktop"), so it sits between anchor 3 and anchor 5.	4 / 5
Distinctiveness Conflict Risk	Avalonia is a clearly named niche framework, making this mostly distinct; the shared "cross-platform XAML" vocabulary creates minor overlap risk with WPF/.NET MAUI skills (the body even links a wpf-xaml-style-generator skill). Not a 5 because 'cross-platform XAML' alone could plausibly match neighboring .NET UI skills.	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: .claude/skills/avalonia-ui-setup/SKILL.md
Commit: 2237ca2

Reviewed: 13 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.