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.

75

Quality

92%

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

85%

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-structured build guide with concrete commands, explicit re-verification checkpoints, and clear sequencing. Its main weakness is repetition of the 'avoid plain dotnet build' injunction across several sections, which inflates length without adding new information.

Suggestions

Consolidate the 'never build with plain dotnet build' guidance into one authoritative location and reference it from the other sections rather than restating the full rationale each time.

Consider moving the full Build.ps1 parameter list (Section 2.4) into a reference file linked from the body, shortening the main SKILL.md while keeping the detail one level deep.

Trim the TENET block's prose to the essential rule plus a pointer; the elaboration largely repeats points made in Sections 2 and 3.

DimensionReasoningScore

Conciseness

The body is largely lean and command-focused with no concept over-explanation, but the 'never use plain dotnet build' warning is restated across the top TENET, the Section 2 callout, and the Section 3 callout, and the TENET block itself is sizable — it could be tightened without losing clarity.

2 / 3

Actionability

Provides copy-paste-ready commands throughout ('.\Restore.cmd', '.\build.cmd', 'dotnet build src\System.Windows.Forms\...'), a full Build.ps1 parameter surface, flag tables, and concrete examples.

3 / 3

Workflow Clarity

Multi-step processes are clearly sequenced: Section 2.1 prescribes clean-then-build with a progress/error reporting requirement, Section 3 mandates re-verification with build.cmd before claiming a clean build, and Sections 4-5 give numbered IDE workflows.

3 / 3

Progressive Disclosure

A single self-contained file with well-organized, clearly headed sections and no nested external references; no bundle files exist, so the inline structure is appropriate.

3 / 3

Total

11

/

12

Passed

Description

100%

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, well-scoped description: it states concrete capabilities and pairs them with an explicit, multi-trigger 'Use when' clause. It is concise without fluff and clearly distinguishes the skill's niche.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'restore NuGet packages, build the full solution, build a single project, create packages, or troubleshoot build errors' — rather than vague language.

3 / 3

Completeness

Explicitly states what the skill does ('restoring and building the WinForms repository') and when to use it via an explicit 'Use when asked how to...' clause covering several scenarios.

3 / 3

Trigger Term Quality

Triggers mirror natural user phrasings ('restore NuGet packages', 'build the full solution', 'create packages', 'troubleshoot build errors'), giving good coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

Narrowed to the WinForms repository build domain with distinct, specific triggers, making overlap with other skills unlikely.

3 / 3

Total

12

/

12

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.