control-api-tests

Instructions for writing unit tests for new public APIs on WinForms controls and components. Covers test project structure, naming conventions, property tests, event tests, OnXxx method tests, SubControl patterns, data attributes, and handle-state verification.

Quality

80%

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 ./.github/skills/control-api-tests/SKILL.md

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is an excellent, concise, fully actionable instruction set with executable examples and a clear validation checkpoint. Its only gap is progressive disclosure: everything lives inline in one file with no detail offloaded to reference files.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: it does not explain what xUnit, WinForms, or COM interop are, and the CA2016/CS8632 CI-parity section adds genuinely non-obvious knowledge that earns its tokens.	3 / 3
Actionability	It provides fully executable C# examples, concrete file paths, attribute tables, and copy-paste-ready test templates rather than vague or pseudocode direction.	3 / 3
Workflow Clarity	The required test categories are clearly sequenced and capped with an explicit checklist and a validation checkpoint ('Verify with build.cmd (CI parity)'), giving a feedback loop for the testing process.	3 / 3
Progressive Disclosure	Content is well-organized into clear sections, but it is a flat, self-contained single file with no overview-to-detail split or one-level-deep reference files; the only links are cross-skill pointers, so the overview-pointing-to-detailed-materials ideal is only partially met.	2 / 3
	Total	11 / 12 Passed

Description

67%

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 specific and well-scoped to a clear niche, listing many concrete test categories. Its main weakness is the absence of an explicit 'when to use' trigger clause and limited trigger-term variants.

Suggestions

Add an explicit 'Use when writing unit tests for new public APIs on WinForms controls or components' trigger clause to fully answer the 'when' question.

Include a few natural trigger variants a user might say (e.g. 'WinForms control test', 'test a control property/event', 'test OnXxx methods') to broaden trigger-term coverage.

Consider tightening the long list of covered topics into a punchier form so the description stays scannable.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete capabilities: 'test project structure, naming conventions, property tests, event tests, OnXxx method tests, SubControl patterns, data attributes, and handle-state verification' — a comprehensive concrete list rather than vague language.	3 / 3
Completeness	The 'what' is answered thoroughly, but there is no explicit 'Use when...' trigger clause telling Claude when to invoke the skill, which caps completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Natural terms like 'writing unit tests', 'new public APIs', and 'WinForms controls and components' are present, but common user phrasings (e.g. 'test a control property', 'WinForms test', 'test an event') are not covered as trigger variants.	2 / 3
Distinctiveness Conflict Risk	The narrow niche ('writing unit tests for new public APIs on WinForms controls and components') has distinct, specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 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/control-api-tests/SKILL.md
Commit: 4ba3b30

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.