CtrlK
BlogDocsLog inGet started
Tessl Logo

with-tanstack-query

Compose reactive Vue Query keys and results with Vue Table manual row processing, refs/computed state, server counts, and already-processed pages without duplicating query data into a drifting local ref.

62

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/vue-table/skills/with-tanstack-query/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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 content is an exemplar of lean, executable guidance: runnable code, tight wrong/correct mistake pairs, and no padding or over-explanation. The only minor gap is the absence of an explicit validation feedback loop, which is not strictly required for this non-destructive pattern skill.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what Vue, Vue Query, or TanStack Table are, and every line is either runnable code or a directly useful pattern/mistake.

5 / 5

Actionability

The Setup block is fully executable copy-paste TypeScript, and the Common Mistakes section pairs concrete wrong/correct snippets covering the main failure modes (unwrapping early, mirroring data, omitting server counts).

5 / 5

Workflow Clarity

A clear sequence runs from Setup through Core Patterns to Common Mistakes and API Discovery; the destructive/batch validation cap does not apply to this composition-pattern skill, but there is no explicit validate→fix→retry feedback loop, keeping it just below 5.

4 / 5

Progressive Disclosure

This is a short, single-purpose skill with no bundle files and no need for external references; its well-organized sections (Setup, Core Patterns, Common Mistakes, API Discovery) satisfy the simple-skill exception for a top progressive_disclosure score.

5 / 5

Total

19

/

20

Passed

Description

55%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 highly specific and occupies a distinct niche, but it is written in technical jargon that lacks natural user trigger phrases and omits any explicit 'Use when...' guidance. Adding a trigger clause and user-friendly keywords would substantially raise its score.

Suggestions

Append a 'Use when...' clause naming natural triggers, e.g. 'Use when wiring @tanstack/vue-query into @tanstack/vue-table with manual/server-side pagination.'

Add natural-language keywords users actually say (Vue Table, TanStack Query, server-side pagination, cached pages) alongside the technical jargon.

Lead with the concrete outcome ('keep server-fetched table data in sync with Vue Query cache') before the internal mechanism details.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Compose reactive Vue Query keys', 'manual row processing', 'refs/computed state', 'server counts', and 'already-processed pages' — but some read as abstract composition concepts rather than crisp discrete actions, leaving minor coverage gaps.

4 / 5

Completeness

It clearly answers 'what' the skill does but provides no 'Use when...' clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

The phrasing is technical-jargon heavy ('reactive Vue Query keys', 'manual row processing', 'already-processed pages') and omits the natural phrases a user would actually say (e.g. 'Vue Table', 'server-side pagination', 'TanStack Query').

2 / 5

Distinctiveness Conflict Risk

The niche is extremely specific — combining Vue Query with Vue Table manual pagination and avoiding query-data duplication — making it clearly distinguishable with minimal conflict risk against other skills.

5 / 5

Total

14

/

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.