Name: csharp-azure-spector-coverage-gaps
Rating: 72 (1 reviews)
Author: Azure

csharp-azure-spector-coverage-gaps

Discovers and implements gaps in Spector test coverage for the Azure C# HTTP client emitter. Use when asked to find missing Spector scenarios, add Spector test coverage, or implement a specific Spector spec for the Azure C# emitter. Can also compare coverage between the Azure dashboard and the Standard (TypeSpec core) dashboard.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%

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 executable code and a clear, validated multi-step workflow, but it carries recurring redundancy about stubbed generation and is monolithic with no progressive disclosure into reference files.

Suggestions

Consolidate the stubbed-vs-unstubbed explanation into one location and reference it from the other steps to remove the triple repetition.

Move the large existing-test-directory listings and the multi-pattern C# test catalog into a reference file (e.g. REFERENCES.md) and link to it from SKILL.md to improve progressive disclosure.

Trim the dashboard-comparison prose and the duplicated 'Note' blocks under Steps 1 and 3, keeping only the forward pointer to Test-Spector.ps1.

Dimension	Reasoning	Score
Conciseness	The body is dense with executable commands and tables, but it is long and repeats the stubbed/unstubbed note in three places (Workflow, Step 1, Step 3) plus the Notes section, which could be tightened.	2 / 3
Actionability	Provides fully executable PowerShell and C# examples with concrete filters, paths, and copy-paste test templates (e.g. 'pwsh eng/scripts/Generate.ps1 -filter "http/encode/duration" -Stubbed $false').	3 / 3
Workflow Clarity	Clear 8-step sequence with an explicit checklist, validation checkpoints ('Validate all tests pass', 'Verify generation succeeded', 'Verify the spec is not in the failing specs list'), and feedback loops for regenerating/re-running on failure.	3 / 3
Progressive Disclosure	Sections are well organized, but the skill is a single monolithic file with all content inline and no bundle files or one-level-deep references to split out the lengthy spec/directory listings or test-pattern catalog.	2 / 3
	Total	10 / 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.

The description is third person, specific, and complete — it names concrete actions, includes explicit 'Use when' trigger guidance, and occupies a distinct niche. It matches the strongest anchor on every dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'Discovers and implements gaps', 'find missing Spector scenarios, add Spector test coverage', and 'compare coverage between the Azure dashboard and the Standard dashboard' — rather than vague language.	3 / 3
Completeness	Clearly answers both 'what' (discovers and implements Spector coverage gaps for the Azure C# emitter) and 'when' via an explicit 'Use when...' clause listing the triggering requests.	3 / 3
Trigger Term Quality	Natural phrasings a user would actually say ('find missing Spector scenarios', 'add Spector test coverage', 'implement a specific Spector spec', 'compare coverage') with good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (Azure C# Spector test coverage) with distinct, specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (564 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: Azure/azure-sdk-for-net
Path: .github/skills/csharp-azure-spector-coverage-gaps/SKILL.md
Commit: 0afb185

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