testing

Implementation details for EF Core test infrastructure. Use when changing test fixtures, SQL baseline assertions, test helpers, the test class hierarchy, or when adding new tests.

Quality

91%

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

Quality

Content

90%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 a concise, highly actionable reference with concrete code, commands, and a clear test-adding workflow supported by an error-recovery pitfalls table. Structure is good and self-contained, with only minor room for splitting detailed reference material out.

Suggestions

Add an explicit inline validation checkpoint in the 'Adding New Tests' workflow (e.g., 'Verify Check_all_tests_overridden passes before capturing baselines') to lift workflow clarity to the top anchor.

Consider moving the TestHelpers/Fixtures detail into a separate references file referenced from SKILL.md to improve progressive disclosure now that the body exceeds ~90 lines.

Dimension	Reasoning	Score
Conciseness	The body is lean and dense — tables, terse hierarchy diagrams, and concrete method/command references — assuming Claude's knowledge of EF Core with no padding or explanation of basic concepts, so every token earns its place.	5 / 5
Actionability	Provides copy-paste-ready code (the provider override pattern) and a complete `dotnet exec` command with exact flags, plus specific method names, paths, and env vars covering the common cases of adding and running tests.	5 / 5
Workflow Clarity	The 'Adding New Tests' workflow is a clear 6-step sequence with baseline capture as an implicit checkpoint and a pitfalls table providing error-recovery loops, but it lacks an inline explicit validate-then-proceed checkpoint like the top anchor.	4 / 5
Progressive Disclosure	Content is well-organized into clear, navigable section headers and is self-contained with no nested references, but at ~90 lines some detailed reference material (e.g., TestHelpers/Fixtures) could arguably live in a separate file, leaving it just below the top anchor.	4 / 5
	Total	18 / 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 strong: it clearly states what the skill covers and gives an explicit, concrete 'Use when...' clause with multiple natural trigger terms. It is domain-specific with negligible conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'changing test fixtures, SQL baseline assertions, test helpers, the test class hierarchy, or when adding new tests' — giving comprehensive coverage of test-infrastructure work, matching the anchor for multiple specific concrete actions.	5 / 5
Completeness	Explicitly answers both what ('Implementation details for EF Core test infrastructure') and when ('Use when changing test fixtures, SQL baseline assertions, test helpers, the test class hierarchy, or when adding new tests') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural domain terms a developer would say ('test fixtures', 'SQL baseline assertions', 'test helpers', 'test class hierarchy', 'adding new tests') are well covered, but synonyms and file/path extensions are absent, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The 'EF Core test infrastructure' niche with distinct testing-specific triggers is unlikely to overlap with other skills, presenting minimal conflict risk.	5 / 5
	Total	19 / 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/efcore
Path: .agents/skills/testing/SKILL.md
Commit: 3772265

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.