Content
78%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 well-structured reference skill: executable examples, a precise lifecycle-override table, and exemplary progressive disclosure across a 38-file reference bundle. The main weaknesses are minor — slightly fragmentary code snippets and a little off-topic or explanatory padding.
Suggestions
Make inline code snippets self-contained: define or annotate the identifiers they rely on (Ticker in the getTicker example, { id } in the mutation one-liners) so examples are copy-paste ready.
Remove the off-topic "When asked to browse or navigate to a web address, actual visit the address" bullet and trim the library-intro opening paragraph, which restates what @data-client/rest does.
Add a short ordered workflow at the top (define schema via data-client-schema → define resource/endpoint → wire rendering via data-client-react/vue → handle mutations/optimistic updates) to tie the numbered sections into one explicit sequence.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and earns most of its tokens (tables, terse typing tips, minimal prose), but the opening paragraph restates what the library does and the "When asked to browse or navigate to a web address, actual visit the address" bullet is off-topic padding. Not 5: a few trimmable passages remain; not 3: the verbosity is minor, not pervasive. | 4 / 5 |
Actionability | Provides near copy-paste TypeScript for the common cases — full resource() definition, useSuspense reads, controller mutations, custom RestEndpoint, getOptimisticResponse — plus a precise override table. Not 5: several snippets are fragments referencing undefined identifiers (Ticker, bare { id } in the mutation one-liners), so they are not fully self-contained. | 4 / 5 |
Workflow Clarity | Well-sequenced sections (schemas → resources → custom endpoints → extending → best practices → mistakes) with clear decision guidance ("Override the step that owns the change, never fetch itself") and explicit cross-skill delegation to data-client-schema/react/vue. Not 5: as a multi-topic guide it lacks an explicit end-to-end sequence or checkpoints tying the sections into one workflow; not 3: the per-section sequencing and decision rules are explicit. | 4 / 5 |
Progressive Disclosure | The body is a genuine overview that keeps essential patterns inline and pushes detail to well-signaled, one-level-deep references, all of which exist in references/ and are grouped by purpose (References, Guides, Concepts) with a Vue-variant fallback rule. Not 4: navigation and file placement are clean with no content that clearly belongs elsewhere. | 5 / 5 |
Total | 17 / 20 Passed |