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.

63

Quality

76%

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

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.

The body is a tight, highly actionable composition guide with executable code and well-chosen Wrong/Correct mistake patterns. It scores slightly lower on workflow clarity and progressive disclosure because it is a reference-style skill without explicit validation checkpoints or bundle files for deeper detail.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a compact Setup block, two short Core Patterns, terse Wrong/Correct snippets, and an API Discovery pointer, with every line carrying non-obvious domain guidance and no padding about what Vue or libraries are.

5 / 5

Actionability

Provides fully executable, copy-paste-ready TypeScript in both Setup and the Wrong/Correct pairs, covering the common composition cases concretely rather than with pseudocode.

5 / 5

Workflow Clarity

The core composition action is shown unambiguously and the body is well-sequenced (Setup → Core Patterns → Common Mistakes → API Discovery), but it is a pattern/reference skill without explicit validation checkpoints; it sits above the implicit-sequence anchor at 3 but lacks the feedback-loop structure of 5.

4 / 5

Progressive Disclosure

Content is well-organized into clearly signaled sections and the only external pointers are to installed package .d.ts files (appropriate), but at ~110 lines all API detail is inlined with no bundle reference files to offload deeper material, leaving minor organization gaps versus the clean one-level-deep reference structure at 5.

4 / 5

Total

18

/

20

Passed

Description

62%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 distinctive, naming a precise Vue Query + Vue Table composition niche with concrete technical actions. Its main weakness is the absence of an explicit 'Use when' trigger clause and somewhat jargon-heavy trigger terms.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when composing TanStack Query with Vue Table manual pagination').

Include common synonyms users actually say, such as 'TanStack Query' and 'useQuery', alongside 'Vue Query'.

Lead with the highest-frequency user phrasing before the technical composition detail to improve trigger matching.

DimensionReasoningScore

Specificity

Names several concrete actions — 'Compose reactive Vue Query keys and results', 'manual row processing, refs/computed state, server counts, and already-processed pages', 'without duplicating query data into a drifting local ref' — with only minor coverage gaps, fitting the 'lists several specific actions' anchor rather than the comprehensive multi-action anchor at 5.

4 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant terms like 'Vue Query', 'Vue Table', 'refs/computed', and 'server counts' appear but lean technical rather than natural user phrasing, and common synonyms ('TanStack Query', 'useQuery') are missing, matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The exact composition of Vue Query with Vue Table manual row processing is a clear niche with distinct triggers and minimal conflict risk against other skills.

5 / 5

Total

15

/

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.