CtrlK
BlogDocsLog inGet started
Tessl Logo

lazy-prefetch-pattern

Use the ChatJS React Query v5 lazy-prefetch pattern without blocking server rendering. Use when prefetching tRPC queries in Next.js Server Components or changing query dehydration and hydration behavior in apps/chat.

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

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 tight, well-structured skill body that gives concrete, actionable guidance with real codebase anchors and no padding. The placeholder query and absence of an explicit validation checkpoint are the only minor gaps.

DimensionReasoningScore

Conciseness

Lean ~15-line body that assumes Claude's competence, explains no background concepts, and has every token earning its place.

5 / 5

Actionability

Concrete guidance with real file paths and component names, but the code example uses a placeholder query (`trpc.foo.bar.queryOptions(...)`) rather than fully copy-paste-ready code.

4 / 5

Workflow Clarity

A clear ordered pattern (prefetch early, await only required data, render through Hydrate client) for a simple non-destructive task, though no explicit verification checkpoint is given.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, with no need for external references; the heading, intro, bulleted steps, and closing caveat are well-organized per the simple-skill exception.

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.

A precise, well-scoped description that clearly states what the skill does and when to use it with concrete codebase-specific triggers. The main limitation is a thin 'what' clause carrying a single action.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('prefetching tRPC queries', 'changing query dehydration and hydration behavior', 'without blocking server rendering'), with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('Use the ChatJS React Query v5 lazy-prefetch pattern without blocking server rendering') and when ('Use when prefetching tRPC queries... or changing query dehydration and hydration behavior'), though the 'what' is a single action rather than a comprehensive list.

4 / 5

Trigger Term Quality

Natural codebase-specific terms ('prefetching tRPC queries', 'Next.js Server Components', 'query dehydration and hydration') match what a developer would say, though a few synonymous phrasings are absent.

4 / 5

Distinctiveness Conflict Risk

A tightly scoped niche ('apps/chat', 'ChatJS React Query v5 lazy-prefetch pattern', 'Next.js Server Components') with distinct triggers and minimal overlap with other skills.

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
FranciscoMoretti/chat-js
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.