CtrlK
BlogDocsLog inGet started
Tessl Logo

query-patterns

Implement read queries — paginated lists, search/filter/sort, and single-entity fetches — the FSH way (DbContext LINQ + PagedResponse). Use when adding GET endpoints. See also add-feature.

69

Quality

84%

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

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.

A dense, highly actionable pattern reference with executable code and valuable negative-space callouts about what the framework does NOT provide. Structure is clean; the main gap is the absence of explicit feedback-loop guidance for the validator step.

DimensionReasoningScore

Conciseness

Lean and code-dense; assumes knowledge of EF/LINQ/mediator and spends tokens only on non-obvious facts (e.g. 'no generic repository', 'no PaginatedListAsync'), with every line earning its place.

5 / 5

Actionability

Provides complete, executable handler/contract/endpoint code using real APIs (AsNoTracking, EF.Functions.ILike, PagedResponse, RequirePermission) covering both common cases; template placeholders are intentional, not gaps.

5 / 5

Workflow Clarity

Clear contract → handler → endpoint → validator sequence with an explicit checkpoint ('needs a validator ... enforced by Architecture.Tests'), though it is a pattern reference rather than a multi-step workflow.

4 / 5

Progressive Disclosure

Well-organized into focused sections (paginated search, single-entity, endpoints, when to use Specification) with all content appropriately inline and no nested references, though there are no external reference files to signal.

4 / 5

Total

18

/

20

Passed

Description

78%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 specific, well-targeted description that clearly states both capability and trigger, scoped tightly to the FSH query pattern niche. It could broaden the trigger phrasing to cover more natural variations.

Suggestions

Add a few more natural trigger variations to the 'Use when' clause (e.g. 'Use when adding GET endpoints, list/search endpoints, or paginated queries').

Consider mentioning the result type users will see (e.g. 'returns PagedResponse<T>') to strengthen the trigger-term link.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'paginated lists, search/filter/sort, and single-entity fetches' — plus the concrete technical approach ('DbContext LINQ + PagedResponse'), with only minor coverage gaps.

4 / 5

Completeness

Both 'what' (implement read queries the FSH way) and 'when' (Use when adding GET endpoints) are present and explicit, but the 'when' covers a single scenario rather than multiple trigger variations.

4 / 5

Trigger Term Quality

'Use when adding GET endpoints' is a natural trigger phrase and 'read queries'/'search/filter/sort' are user-relevant terms, though a few common variations (e.g. 'list endpoint', 'paging') are missing.

4 / 5

Distinctiveness Conflict Risk

Tightly scoped to the FSH stack with distinctive triggers ('DbContext LINQ + PagedResponse', 'GET endpoints'), giving it a clear niche with minimal conflict risk.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fullstackhero/dotnet-starter-kit
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.