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

73%

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

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.

The body is highly actionable with comprehensive executable examples and a clear sequenced workflow ending in a validation checklist. It is concise and well-structured, with only minor over-framing and no external bundle to progressively disclose.

Dimension	Reasoning	Score
Conciseness	Mostly efficient: code-heavy and rule-driven with minimal preamble, though section 1.4 and the golden-rule block carry a little explanatory framing that could be trimmed.	4 / 5
Actionability	Fully executable copy-paste-ready code blocks cover defaults, round-trips, handle-state, event firing/idempotency, OnXxx, custom EventArgs, and ICommand binding, with concrete test-data attributes and a checklist.	5 / 5
Workflow Clarity	A clear numbered section sequence (structure -> naming -> creation -> SubControl -> data -> required categories -> custom types -> command binding) culminating in an explicit checklist of validation checkpoints, including build.cmd CI-parity verification feedback loop.	5 / 5
Progressive Disclosure	Well-organized single-file structure with clear section headers and a summary checklist, with light cross-skill pointers; no bundle files exist so there is nothing to offload, but the inline reference tables keep it at good rather than fully split.	4 / 5
	Total	18 / 20 Passed

Description

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

The description clearly names the domain and enumerates specific test categories, giving good specificity and distinctiveness. It lacks an explicit 'Use when...' trigger clause, which caps completeness, and the trigger terms are domain-technical rather than natural user phrasings.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when adding new public properties, methods, or events to a WinForms control and needing the accompanying unit tests.'

Broaden trigger-term coverage with natural user phrases and synonyms (e.g. 'WinForms control tests', 'API unit tests', 'round-trip tests').

Lead with the most concrete verbs (verify, round-trip, assert) before the category list to sharpen specificity from 4 toward 5.

Dimension	Reasoning	Score
Specificity	Lists several specific actions ('property tests, event tests, OnXxx method tests, SubControl patterns, data attributes, and handle-state verification') covering the testing domain comprehensively, though some are category names rather than fully concrete verbs.	4 / 5
Completeness	Has a clear 'what' (instructions for writing unit tests covering enumerated categories) but no explicit 'when'/'Use when...' clause, so per the guideline 'when' is missing and completeness caps at 3.	3 / 5
Trigger Term Quality	Contains relevant domain terms ('unit tests', 'public APIs', 'WinForms controls and components') but lacks natural user phrasings or synonyms a person would actually say, and omits common variations.	3 / 5
Distinctiveness Conflict Risk	The narrow focus on 'unit tests for new public APIs on WinForms controls and components' is a clear niche with only minor overlap risk against sibling skills like new-control-api.	4 / 5
	Total	14 / 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/control-api-tests/SKILL.md
Commit: b0a7c95

Reviewed: 1 day 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.