Manage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
86
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific capabilities with concrete API features, includes a comprehensive 'Use when' clause with multiple trigger scenarios, and uses highly distinctive terminology that clearly differentiates it from other React or data fetching skills. The description is concise yet information-dense.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and features: 'useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions' along with specific migration issues like 'object syntax, gcTime, isPending, keepPreviousData'. | 3 / 3 |
Completeness | Clearly answers both what (manage server state with TanStack Query v5, covering specific features) AND when (explicit 'Use when' clause covering data fetching setup, migration errors, and SSR/hydration debugging). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'TanStack Query', 'React', 'data fetching', 'v4→v5 migration', 'SSR/hydration', 'streaming server components', 'offline/PWA', plus specific API terms like 'useMutationState', 'gcTime', 'isPending'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically TanStack Query v5 in React context, with version-specific migration details (v4→v5) and unique API terms that wouldn't conflict with general React or other data fetching libraries. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive TanStack Query v5 skill with excellent actionability - every pattern has executable code examples and the migration guidance is thorough with before/after comparisons. The main weakness is length; the 16 documented issues section, while valuable, makes the file quite long and could benefit from being split into a separate reference file. The content successfully covers v5 new features, critical rules, and common pitfalls.
Suggestions
Extract the 16 Known Issues into a separate MIGRATION_ISSUES.md file and reference it from the main skill, keeping only the top 3-4 most common issues inline
Condense the before/after code examples in the issues section - many could be reduced to single-line diffs rather than full code blocks
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | While the skill provides valuable v5-specific information, it's quite lengthy (~800 lines) with extensive issue documentation that could be condensed. Some sections like the 16 documented issues include verbose before/after examples that could be more compact. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all hooks, patterns, and migrations have copy-paste ready TypeScript/TSX code. The before/after migration examples are particularly actionable with clear syntax differences. | 3 / 3 |
Workflow Clarity | Clear setup sequence (install → provider → hooks), explicit validation through the 'Always Do/Never Do' checklists, and well-structured issue prevention with specific error messages and solutions. The Quick Setup section provides numbered steps. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in a single monolithic file. The extensive Known Issues section (16 issues with full examples) could be split into a separate MIGRATION_ISSUES.md file. External references are provided at the end but inline content is heavy. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
68%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1059 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
abde401
Table of Contents
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.