Name: csharp-azure-spector-coverage-gaps
Rating: 69.6 (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

85%

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%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 content is highly actionable and clearly sequenced with proper validation, but it is verbose in places and monolithic, inlining substantial reference-style material that would benefit from separation into bundle files.

Suggestions

Move the 'Common test patterns' catalog and the Standard/Azure test-directory tree listings into a references file (e.g. references/test-patterns.md) and link to it from SKILL.md to reduce token load.

Dedupe the 'committed Spector libraries are stubbed' / '[SpectorTest] auto-skip' guidance — state it once in Step 1 and reference it rather than repeating across Step 3 and Notes.

Tighten the 'Common test patterns' section to the 2-3 most representative examples and point to the reference file for the rest.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but repeats the 'committed Spector libraries are stubbed' and '[SpectorTest] auto-skip' notes across Step 1, Step 3, and the Notes section, and the long 'Common test patterns' catalog could be tightened.	3 / 5
Actionability	Provides copy-paste-ready PowerShell commands (e.g. 'pwsh eng/scripts/Generate.ps1 -filter "..." -Stubbed $false') and a complete C# test template plus multiple concrete pattern examples covering the common cases.	5 / 5
Workflow Clarity	An 8-step sequenced workflow with explicit checkpoints ('Verify generation succeeded', 'Validate all tests pass') and feedback loops (regenerate unstubbed, restore stubbed state) for a code-modifying process.	5 / 5
Progressive Disclosure	No bundle files exist and all content is inlined in a ~560-line SKILL.md; the large 'Common test patterns' catalog and full directory tree listings are content that could be split into reference files but are instead inline.	3 / 5
	Total	16 / 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.

The description is specific, well-triggered, and complete, clearly stating both what the skill does and when to invoke it within a well-scoped niche. Only minor room for improvement in trigger-term synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Discovers and implements gaps in Spector test coverage', 'compare coverage between the Azure dashboard and the Standard ... dashboard' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (discover and implement Spector coverage gaps) and 'when' ('Use when asked to find missing Spector scenarios, add Spector test coverage, or implement a specific Spector spec') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'find missing Spector scenarios', 'add Spector test coverage', and 'implement a specific Spector spec' match what a user would say, though synonyms and file extensions are not exhaustively covered.	4 / 5
Distinctiveness Conflict Risk	The niche is tightly scoped to 'Spector test coverage for the Azure C# HTTP client emitter', giving it distinct triggers and minimal overlap with other skills.	5 / 5
	Total	19 / 20 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: bc946a1

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