devserver

Build, test, and maintain the Uno DevServer (CLI tool, RemoteControl Host, MCP proxy, add-in discovery). Use when working under src/Uno.UI.DevServer.Cli, src/Uno.UI.RemoteControl.Host, or src/Uno.UI.RemoteControl.DevServer.Tests, or on DevServer CLI commands, the MCP proxy, IDE channel, or add-in resolution.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

90%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.

An exemplary maintenance-oriented skill body: token-efficient, project-specific, and immediately actionable, with per-task verification steps and a clearly signaled references section. The only improvements are structural — splitting the IDE-compatibility and key-file inventories into reference files and adding explicit fix-and-retry loops to maintenance workflows.

Suggestions

Move the per-IDE compatibility contracts (§8) and the key-files inventory (§2) into reference files and keep one-line summaries in SKILL.md, especially since the bundle currently has no references/ directory.

In §7 maintenance tasks, add an explicit feedback loop after each verification step (e.g., 'if tests fail, fix and re-run') to lift workflow clarity to explicit-checkpoint level.

Dimension	Reasoning	Score
Conciseness	The body is dense with project-specific facts Claude cannot know (source map, flags, retry counters, retry counts, IDE entry-point contracts) delivered via tables and terse lists. There is no padding and no explanation of concepts Claude already knows — every token earns its place.	5 / 5
Actionability	Copy-paste-ready build/test commands, exact file responsibilities per maintenance task, and concrete verification commands ("dotnet test src/Uno.UI.RemoteControl.DevServer.Tests/...", "uno-devserver disco --json", "run-devserver-cli-tests.ps1 with -DevServerCliDllPath") cover the common cases.	5 / 5
Workflow Clarity	Section 7 gives per-task sequences each ending in an explicit verification step (test harness, disco --json, MCP client), and guard tests are named (EntryPointRegressionTests.cs). Feedback loops (fix-and-retry on failure) are implicit rather than stated, keeping it below 5; not 3 because checkpoints are explicit and frequent.	4 / 5
Progressive Disclosure	A dedicated References section (§9) lists one-level-deep, clearly signaled paths, and the overview structure (architecture, source map, commands) is well organized. However the bundle ships no references/ files, and detail-heavy blocks (§8 IDE compatibility contracts, the single-line key-files list in §2) are inlined rather than split out — minor organization gaps below the 5 anchor, well above 3.	4 / 5
	Total	18 / 20 Passed

Description

87%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.

A strong description: it states what the skill does with enumerated concrete components and gives an explicit, directory-level 'Use when' clause covering commands and subsystems. Only minor gaps in action-verb specificity and domain synonyms (e.g., hot reload) keep individual dimensions at 4.

Dimension	Reasoning	Score
Specificity	"Build, test, and maintain" plus four enumerated concrete components ("CLI tool, RemoteControl Host, MCP proxy, add-in discovery") lists several specific scopes. Not 5 because the action verbs themselves are somewhat generic compared to a fully enumerated action list; not 3 because coverage clearly exceeds 1-2 actions.	4 / 5
Completeness	Explicitly answers both: what ("Build, test, and maintain the Uno DevServer..." with enumerated components) and when ("Use when working under src/... or on DevServer CLI commands, the MCP proxy, IDE channel, or add-in resolution") with concrete trigger phrases, matching the anchor-5 structure.	5 / 5
Trigger Term Quality	Natural terms users would say — "DevServer", "DevServer CLI commands", "MCP proxy", "add-in", "IDE channel" — plus exact project directory names (src/Uno.UI.DevServer.Cli, etc.). A few domain synonyms (e.g., "hot reload") are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Names a specific product component ("Uno DevServer") with repo-specific project paths as triggers — a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: unoplatform/uno
Path: .claude/skills/devserver/SKILL.md
Commit: e1292e0

Reviewed: 5 days 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.