CtrlK
BlogDocsLog inGet started
Tessl Logo

with-tanstack-query

Compose Solid Query reactive options with Solid Table manual server processing. Load for tracked query-key signals, query result getters, server row counts, keepPreviousData, and avoiding React Query patterns or duplicated data state.

66

Quality

80%

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

82%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, code-first skill that assumes Claude's competence and delivers executable patterns plus high-value wrong/correct mistake pairs. Its main weakness is minor executability gaps from undefined placeholder values and an all-inline structure that could split some detail into references.

Suggestions

Define or stub the placeholder identifiers (columns, fetchPeople, sorting) so the Setup example runs as-is.

Consider moving the Common Mistakes detail into a references file linked from SKILL.md to strengthen progressive disclosure and keep the overview leaner.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding: it assumes Claude knows the libraries and gives only working code, terse pattern notes, and pointed wrong/correct pairs, with every token earning its place.

5 / 5

Actionability

Provides copy-paste-ready Setup code and concrete wrong/correct pairs, but references undefined context values (columns, fetchPeople, sorting) leaving minor gaps for full executability.

4 / 5

Workflow Clarity

Clear sectioned organization (Setup, Core Patterns, Common Mistakes, API Discovery) makes the composition action unambiguous; no validation checkpoints are needed since the skill is non-destructive, so it sits just below a full explicit-workflow 5.

4 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers and no nested references; at ~130 lines with everything inline it is good but not the ideal split-overview-with-references shape of a 5.

4 / 5

Total

17

/

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, third-person description that clearly carves out a narrow composition niche and provides explicit 'Load for' trigger guidance. It is strong on distinctiveness but the trigger phrasing is technical rather than natural user language.

Suggestions

Add a 'Use when...' clause phrased in natural user terms (e.g., 'Use when combining @tanstack/solid-query with @tanstack/solid-table for server-side pagination') to lift completeness and trigger quality.

Include package names or synonyms (tanstack, solid-query, solid-table) so the description matches how users actually refer to the libraries.

DimensionReasoningScore

Specificity

Lists several concrete items (tracked query-key signals, query result getters, server row counts, keepPreviousData, avoiding React Query patterns) under a single composition action, with minor gaps rather than a full set of distinct actions.

4 / 5

Completeness

States a clear 'what' (compose Solid Query options with Solid Table manual server processing) and an explicit 'when' via 'Load for...' trigger conditions, but the when is a list of technical conditions rather than natural user-facing triggers.

4 / 5

Trigger Term Quality

Good on-domain keyword coverage (Solid Query, Solid Table, query-key signals, keepPreviousData, React Query patterns) a user would name, though it leans technical and omits natural synonyms like 'tanstack' or file/package names.

4 / 5

Distinctiveness Conflict Risk

Targets a very specific niche (Solid Query + Solid Table manual server processing composition) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
TanStack/table
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.