CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

query-pipeline

Implement and review EF Core query translation, projection visitors, split-query enumeration, and query regression tests. Use when changing query-pipeline code or choosing specification and provider coverage for a query regression.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, expert-level review checklist that assumes competence and concentrates entirely on non-obvious EF Core query-pipeline knowledge, with concrete class and tool names throughout. It falls just short of top marks on actionability and workflow clarity only because the spec-test/override pattern is described but not exemplified, and the material is organized by topic rather than as a sequenced workflow.

Suggestions

Add one minimal inline example of the shared virtual specification test plus a provider override calling the base, since the regression-test ownership rules repeatedly reference that structure without showing it.

Add a short entry-point line indicating the order of application (e.g., locate the change → apply the matching section's checks → run the Validation section's tools) so the topical checklists function as a sequence.

In Validation, show the exact AssertSql()/precompiled-query usage shape (one short snippet) so the verification steps are copy-paste ready rather than named only.

DimensionReasoningScore

Conciseness

Every bullet delivers project-specific knowledge (EF Core internals, test ownership rules, null-semantics compensation) with zero padding and no explanation of concepts Claude already knows — e.g., "SQL UNKNOWN can be filtered like `false` in a predicate but not in a projected value or under negation" is pure non-obvious domain detail. Not 4 because there are no over-explained passages that could be trimmed.

5 / 5

Actionability

Concrete APIs and verification tools are named throughout ("`SplitQueryResultCoordinator`", "`PrecompiledQueryTestHelpers` verifies generation, compilation, and execution", "`ToQueryString()` shows generated SQL without executing"), giving mostly executable guidance. Not 5 because patterns the body governs — the shared virtual spec test and provider override structure — are described but never shown with even a minimal example, leaving a minor gap for instruction-only guidance.

4 / 5

Workflow Clarity

Validation checkpoints are explicit and pervasive ("cover both eligible and rejected shapes with exact result assertions in sync and async", "Test that successful move separately from the subsequent terminal call", "Prove cross-command consistency with a writer transaction and an explicit barrier between reads"), and sections map to the pipeline areas a change touches. Not 5 because the body is a set of topical checklists rather than a sequenced process, so the order in which to apply the sections is implicit.

4 / 5

Progressive Disclosure

The body is under 50 lines, references no external files, and no bundle files exist, so all content is appropriately inline under five well-labeled sections (Regression Test Ownership, Translation, Optimizations, Split Queries, Validation). Per the simple-skill guideline, well-organized sections alone earn the top anchor here.

5 / 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.

A strong description: third-person voice, concrete capability list, and an explicit "Use when..." trigger clause with specific conditions. The only weakness is trigger-term synonym coverage (e.g., "Entity Framework Core", "LINQ") that would broaden natural-match surface area.

DimensionReasoningScore

Specificity

"Implement and review EF Core query translation, projection visitors, split-query enumeration, and query regression tests" lists multiple specific concrete actions covering the skill's domain comprehensively, matching the top anchor; not 4 because coverage of the domain's main capability areas is complete rather than having minor gaps.

5 / 5

Completeness

The description explicitly answers "what" (implement and review query translation, projection visitors, split-query enumeration, regression tests) and "when" with concrete trigger phrases ("Use when changing query-pipeline code or choosing specification and provider coverage for a query regression"). Not 4 because the "when" clause is explicit and specific rather than improvable.

5 / 5

Trigger Term Quality

Terms like "EF Core", "query translation", "split-query enumeration", "query-pipeline code", and "query regression" are natural phrases the target audience would say, but common synonyms and variations such as "Entity Framework Core", "LINQ", or "SQL translation" are missing, which fits the good-but-not-comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

"EF Core query translation, projection visitors, split-query enumeration" carves out a clear niche with distinct domain-specific triggers, giving minimal overlap risk with other skills. Not 4 because the specialized EF Core query-pipeline vocabulary makes triggering for an unrelated skill very unlikely.

5 / 5

Total

19

/

20

Passed

Validation

100%

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/query-pipeline/SKILL.md

Reviewed

Table of Contents

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.