CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-sequenced build guide with explicit validation checkpoints and feedback loops. The main weaknesses are mild repetition of the core build.cmd warning and a monolithic structure that could offload the parameter reference to a bundled file.

DimensionReasoningScore

Conciseness

The body is mostly lean commands, tables, and flags with no padding of concepts Claude already knows, but the build.cmd-vs-dotnet-build warning is restated across three blockquotes (TENET, §2, §3), which is minor redundancy that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready commands (\Restore.cmd, \build.cmd, \build -clean, dotnet build <csproj>), a full Build.ps1 parameter surface, a flags table, and concrete examples covering the common build cases.

5 / 5

Workflow Clarity

Sequences are clearly numbered (§2.1 clean-then-build, §4/§5 IDE workflows) with explicit validation (the TENET re-verify-with-build.cmd requirement), a progress/failure reporting feedback loop, and a troubleshooting section for error recovery.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with easy navigation and no nested references, but it is a single self-contained ~220-line document with no one-level-deep references, so it sits below the anchor requiring well-signaled split-out references.

4 / 5

Total

18

/

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, third-person description that concretely names five actions and pairs a clear what with an explicit when clause. Its only gap is the absence of file extensions and a few synonyms in the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "restore NuGet packages", "build the full solution", "build a single project", "create packages", "troubleshoot build errors" — giving comprehensive coverage of the WinForms build domain, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

Explicitly answers what ("Instructions for restoring and building the WinForms repository") and when ("Use when asked how to restore NuGet packages, build the full solution, build a single project, create packages, or troubleshoot build errors") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like "restore NuGet packages", "build the full solution", and "troubleshoot build errors" give good coverage, but file extensions (.sln, .csproj) and common synonyms (e.g. "compile") are absent, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The "WinForms repository" niche plus specific build/restore triggers make it clearly distinct with minimal overlap risk against other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dotnet/winforms
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.