query-pipeline

Implementation details for EF Core LINQ query translation, SQL generation, and bulk operations (ExecuteUpdate/ExecuteDelete). Use when changing expression visitors, SqlExpressions, QuerySqlGenerator, ShaperProcessingExpressionVisitor, UpdateExpression, DeleteExpression, or related classes.

Quality

78%

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

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An admirably concise, well-organized overview of the query pipeline stages and validation tooling, but the bare stage labels lack actionable detail and validation is not integrated as explicit checkpoints with feedback loops.

Suggestions

Add a one-line description of what each pipeline stage (Preprocessing, Translation, Postprocessing, Compilation, SQL Generation) does so Claude knows where to intervene.

Integrate validation into the workflow as an explicit checkpoint (e.g., "After Translation, run ExpressionPrinter to confirm the tree") rather than listing validation separately.

Add a short feedback-loop note for batch operations, e.g., "If AssertSql() output diverges from the LINQ intent, revise the SqlExpression and re-run the provider functional test."

Dimension	Reasoning	Score
Conciseness	The body is a lean stage list plus three concise validation bullets with no concept explanation or padding; every line carries specific information and assumes Claude's competence.	3 / 3
Actionability	It names concrete tools (ToQueryString(), ExpressionPrinter, AssertSql()) but the five stages are bare labels with no executable detail or examples of what each stage entails, leaving guidance incomplete.	2 / 3
Workflow Clarity	The five stages are clearly sequenced and validation methods are listed, but validation is a separate section rather than integrated checkpoints, and there are no feedback loops despite batch operations (ExecuteUpdate/ExecuteDelete) in scope.	2 / 3
Progressive Disclosure	The skill is well under 50 lines with no external references needed and is organized into clear Stages and Validation sections, satisfying the simple-skill allowance for a top score.	3 / 3
	Total	10 / 12 Passed

Description

85%

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 precise, well-scoped description that clearly answers what the skill covers and when to use it, with a distinctive internal-tooling niche. Its only weakness is trigger terms leaning on internal class-name jargon rather than natural user phrasings.

Suggestions

Add a few natural-language trigger phrases alongside the class names (e.g., "Use when modifying how EF Core translates LINQ to SQL or generating SQL for queries") so users who don't name the exact classes still match.

Consider mentioning broader entry points like "LINQ providers" or "query compilation" to widen natural-language coverage without losing distinctiveness.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete capabilities — "LINQ query translation, SQL generation, and bulk operations (ExecuteUpdate/ExecuteDelete)" — matching the score-3 anchor of multiple specific concrete actions.	3 / 3
Completeness	It explicitly states both what ("Implementation details for EF Core LINQ query translation, SQL generation, and bulk operations") and when ("Use when changing expression visitors, SqlExpressions...") with an explicit trigger clause.	3 / 3
Trigger Term Quality	The "Use when" clause surfaces relevant domain terms (expression visitors, SqlExpressions, QuerySqlGenerator, UpdateExpression, DeleteExpression) but they are internal class-name jargon rather than natural phrasings a user would say, missing common variations.	2 / 3
Distinctiveness Conflict Risk	The EF Core internal query-pipeline niche anchored to specific class names (QuerySqlGenerator, ShaperProcessingExpressionVisitor) is highly specific and unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 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/query-pipeline/SKILL.md
Commit: 61317c9

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