CtrlK
BlogDocsLog inGet started
Tessl Logo

query-layer

Query boundaries with TanStack Query and Wellcrafted Results. Use when editing createQuery, createMutation, resultQueryOptions, resultMutationOptions, defineQuery, defineMutation, defineKeys, shared cache identity, mutation lifecycle, or service-to-TanStack adapters.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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.

The body is a well-structured, actionable reference: executable code examples, decision tables, and well-signaled one-level-deep bundle references keep it navigable and concrete. It is occasionally a touch verbose (diagrams and restated relationships) but otherwise earns its tokens.

DimensionReasoningScore

Conciseness

The body is largely efficient — rules, tables, and lean code samples that assume Claude's competence — with only minor instances that could be trimmed (e.g., the ASCII architecture diagram and some explanatory sentences restating relationships already implied by the code); it does not over-explain basic concepts, so it sits above the midpoint but not fully lean.

4 / 5

Actionability

It provides concrete, copy-paste-ready TypeScript and Svelte examples covering the common cases (defineKeys, createAudioQueries, createQuery/createMutation with .options, imperative .fetch()/.ensure()), plus a decision table mapping each adapter surface to a specific pattern, matching the fully-executable top anchor.

5 / 5

Workflow Clarity

Dependency direction, adapter-boundary placement, and the reactive-vs-imperative choice are clearly sequenced with a comparison table and concrete guidance; however the skill has no destructive/batch-cap concern and the key rules are stated as principles rather than an ordered validate-fix-retry checklist, so it is just below the explicit-checkpoint 5.

4 / 5

Progressive Disclosure

The SKILL.md is a focused overview that points to three clearly-signaled one-level-deep references in references/ (error-transformation-patterns.md, runtime-dependency-injection.md, advanced-query-patterns.md), each real files with concrete scoped content and no nested indirection, matching the clear-overview top anchor.

5 / 5

Total

18

/

20

Passed

Description

76%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 states a clear 'what' and an explicit 'Use when ...' trigger clause with many concrete API identifiers, fully satisfying completeness. Its main gap is that trigger terms are codebase-specific jargon rather than the natural-language synonyms a user might voice.

Suggestions

Add a few natural-language trigger phrases alongside the API names (e.g., 'data fetching', 'cache invalidation', 'optimistic updates') so users who phrase needs conversationally still match.

Tighten the long identifier list into capability-level actions (e.g., 'define shared queries and mutations, manage cache identity, adapt Result-returning services to TanStack') to read as actions rather than a noun inventory.

DimensionReasoningScore

Specificity

The description lists many concrete API targets — 'createQuery, createMutation, resultQueryOptions, resultMutationOptions, defineQuery, defineMutation, defineKeys, shared cache identity, mutation lifecycle' — so it enumerates several specific actions; it is a touch below a 5 because these are concrete nouns/identifiers rather than a comprehensive set of clearly distinct capability actions.

4 / 5

Completeness

It explicitly answers both 'what' ('Query boundaries with TanStack Query and Wellcrafted Results') and 'when' via the explicit 'Use when editing ...' clause enumerating concrete trigger targets, matching the top anchor for both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

The triggers are the actual API identifiers a developer working in this codebase would name ('createQuery', 'defineMutation', 'resultQueryOptions'), which are relevant but technical-jargon-heavy; it lacks the common natural-language phrasings and synonyms a user might more casually say, leaving some natural variations missing.

3 / 5

Distinctiveness Conflict Risk

The combination of TanStack Query + Wellcrafted Results plus the named factories carves a fairly distinct niche with minimal conflict risk against unrelated skills, but it could overlap with sibling skills like 'services-layer' or 'svelte' mentioned in the body, keeping it just below the clearest-niche 5.

4 / 5

Total

16

/

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
EpicenterHQ/epicenter
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.