Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tight, highly actionable instruction skill: executable examples for every pattern, clear scope-placement rules, and a coherent grounding-to-naming flow, with essentially no filler. The only deductions are a version-pinned detail outside a deprecated section and the absence of explicit validation checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and project-specific — every section states non-obvious rules ("So do not call `invalidateQueries` after a write in a component or a mutation callback", "writes refer to reads, never the reverse") with no padding and no explanation of concepts Claude already knows. It misses the 5 anchor because time-sensitive version information ("as installed (0.47)") appears outside any old-patterns/deprecated section, which the guidelines say should penalize conciseness. | 4 / 5 |
Actionability | Guidance is copy-paste ready and covers the common cases: the two-map resultQueries/resultMutations declaration, hook usage ("createQuery(() => billingQueries.overview())"), the full MutationCache invalidation rule, the mutationOptions spread with setQueryData, and the imperative runMutation example with error handling. It exceeds the 4 anchor because examples are executable (not pseudocode) and span all of the skill's named patterns. | 5 / 5 |
Workflow Clarity | The sections form a coherent, ordered decision path — ground against installed sources, compose in two maps, install one invalidation rule per client, place behavior by scope via spread, run imperatively — with a grounding checkpoint ("confirm the deciding detail in the installed `@tanstack/query-core` source"). It stops short of 5 because no explicit validation/feedback-loop steps exist, and sits above 3 because the sequence and decision points are clear and no risky operation lacks guidance. | 4 / 5 |
Progressive Disclosure | No bundle files exist, and the single ~157-line body is organized into seven well-labeled sections with clearly signaled one-level-deep pointers (the wellcrafted/query GitHub source, DeepWiki, and related skills services-layer/svelte/error-handling). It fits the 4 anchor of good structure with minor gaps — the length slightly exceeds the ideal single-file overview, and a rationale-heavy passage (the plan-change-preview POST example) could live in a reference — but nothing is buried or nested. | 4 / 5 |
Total | 17 / 20 Passed |