building-code

Instructions for restoring and building the WinForms repository. Use when asked how to restore NuGet packages, build the full solution, build a single project, create packages, or troubleshoot build errors.

Quality

89%

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

Quality

Content

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

Highly actionable, executable guidance with clear workflows and genuine validation checkpoints for a batch operation (re-verify with build.cmd before claiming clean). The main weakness is redundancy: the core build.cmd mandate is stated three times and some bulk reference material is inlined.

Suggestions

State the build.cmd-only mandate once (in the opening TENET block) and have the §2 and §3 notes reference it briefly instead of restating it in full — this alone removes ~15 lines of duplication.

Move the full Build.ps1 parameter list (§2.4) into a references file (e.g. references/build-flags.md) and keep only the common-flags table inline; the parameter surface is discoverable via -help.

Tighten the §2.1 'reporting requirement' paragraph to a two-line instruction (stream output / use -bl and report per-project pass/fail as it happens).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, dense with commands and tables, but the build.cmd-only mandate is repeated three times (the opening TENET block, the §2 note, and the §3 note), and the §2.4 full Build.ps1 parameter list plus the padded §2.1 'reporting requirement' paragraph could be tightened. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' better than the 'several padded sections' anchor.	3 / 5
Actionability	Every section gives copy-paste-ready commands: '.\Restore.cmd', '.\build.cmd -configuration release -pack', 'dotnet build src\System.Windows.Forms\System.Windows.Forms.csproj', plus a flags table, output-location table, and concrete VS/VS Code step sequences. This matches the fully-executable, common-cases-covered top anchor.	5 / 5
Workflow Clarity	Sequences are clear (restore → build; clean → build; VS steps 1-2-3) with explicit validation checkpoints — 'you must re-verify with build.cmd before claiming a change builds cleanly' and the inner-loop 'only after at least one successful .\build.cmd / .\Restore.cmd' precondition — and error-recovery feedback loops in the Troubleshooting section (inspect Build.binlog, SDK mismatch → run Restore.cmd). This matches the explicit-validation-with-feedback-loops anchor.	5 / 5
Progressive Disclosure	Sections are well-organized with clear headers, tables, and easy navigation, but this ~220-line body inlines bulk material that could sit in a reference file — the §2.4 full Build.ps1 parameter list and build-outputs table. This matches 'good structure; most content appropriately placed; minor organization gaps' rather than the clearly-split top anchor.	4 / 5
	Total	17 / 20 Passed

Description

92%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 names the domain, enumerates five concrete capabilities, and pairs them with an explicit, natural 'Use when' trigger clause. The only weakness is modest synonym coverage in its trigger terms.

Dimension	Reasoning	Score
Specificity	The description lists multiple specific concrete actions — 'restore NuGet packages, build the full solution, build a single project, create packages, troubleshoot build errors' — which comprehensively covers the build/restore domain for this repository. It clearly matches the comprehensive-coverage anchor rather than the 'minor gaps' anchor below it.	5 / 5
Completeness	It explicitly answers both 'what' ('Instructions for restoring and building the WinForms repository') and 'when' with a concrete 'Use when asked how to...' trigger list. This matches the anchor for clear, explicit what-and-when with concrete trigger phrases, and is clearly above the level where 'when' is only weakly implied.	5 / 5
Trigger Term Quality	Natural phrases users would say are present ('restore NuGet packages', 'build a single project', 'troubleshoot build errors'), matching 'good keyword coverage; a few natural terms missing'. It falls short of the top anchor because common synonyms and extensions like 'compile', 'msbuild', '.sln', or 'pack' are absent.	4 / 5
Distinctiveness Conflict Risk	The description is tightly scoped to the WinForms repository with distinct triggers ('WinForms repository', 'NuGet packages', 'build the full solution'), giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	19 / 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: dotnet/winforms
Path: .github/skills/building-code/SKILL.md
Commit: a84cf1f

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