data-client-rest

Define REST APIs with @data-client/rest - resource(), RestEndpoint, CRUD (GET/POST/PUT/PATCH/DELETE), HTTP fetch, normalize, cache, urlPrefix, path-to-regexp parameters, searchParams, pagination, extend(), auth/headers, optimistic updates, polling, file download, blob, parseResponse. Use when defining or modifying network endpoints, REST resources, or the HTTP layer.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/data-client-rest/SKILL.md

Quality

Content

67%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.

A well-structured, actionable reference guide with concrete TypeScript examples and clear progressive disclosure to a references/ directory. The weakest dimension is conciseness, due to repeated boilerplate banners and duplicated phrasing.

Suggestions

Remove the repeated 'Always follow these patterns...' banners and the duplicated 'type safety and automatic cache management' phrasing (intro vs. section 1) to tighten conciseness.

Reformat the References section so each referenced file is its own bulleted link instead of semicolon-grouping multiple files on one line, improving navigation clarity.

Make the mutation code snippets self-contained (define `id`/`todo` or note they come from surrounding context) to push actionability toward fully copy-paste-ready examples.

Dimension	Reasoning	Score
Conciseness	The body is mostly code and reference links, but repeats boilerplate banners ('Always follow these patterns...') and restates 'type safety and automatic cache management' in both the intro and section 1, which is unnecessary padding that could be tightened — matching the score-3 anchor.	3 / 5
Actionability	Concrete, executable TypeScript examples cover the common cases (resource() definition, useSuspense rendering, CRUD mutations, RestEndpoint, extend(), getOptimisticResponse()), but individual snippets rely on undefined context variables (e.g. `{ id }`, `todo`), leaving minor gaps versus the fully copy-paste score-5 anchor.	4 / 5
Workflow Clarity	A clear numbered sequence (1 Defining Schemas → 2 Resources → 3 Custom RestEndpoint → 4 Extending → 5 Best Practices → 6 Common Mistakes) plus the explicitly sequenced RestEndpoint lifecycle (fetchResponse → parseResponse → process) gives a clear sequence; no validation checkpoints are present, but none are required for a non-destructive pattern guide, so it sits at score 4 rather than 3.	4 / 5
Progressive Disclosure	Content is well split between inline quick-start examples and one-level-deep references/*.md links, with a categorized References section (API, Guides, Concepts) and clearly signaled inline links; the main gap is cluttered semicolon-grouped link lists (e.g. 'RestEndpoint; _EndpointLifecycle.md; RestEndpoint.js'), keeping it at score 4.	4 / 5
	Total	15 / 20 Passed

Description

88%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.

A strong, third-person description that names the library and a comprehensive set of concrete capabilities, with an explicit 'Use when...' trigger clause. The only soft spot is trigger-term breadth and minor overlap with sibling data-client skills.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete constructs and actions — 'resource(), RestEndpoint, CRUD (GET/POST/PUT/PATCH/DELETE), HTTP fetch, normalize, cache, urlPrefix, ... extend(), auth/headers, optimistic updates, polling, file download, blob, parseResponse' — giving comprehensive coverage of the API surface, matching the score-5 anchor.	5 / 5
Completeness	It explicitly answers both 'what' (Define REST APIs with @data-client/rest, plus the capability list) and 'when' ('Use when defining or modifying network endpoints, REST resources, or the HTTP layer.') with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ('defining or modifying network endpoints, REST resources, or the HTTP layer') alongside CRUD verbs, but a few common synonyms/variations users might say are absent, fitting the score-4 anchor rather than the fully comprehensive score-5 example.	4 / 5
Distinctiveness Conflict Risk	It is tied to a specific library (@data-client/rest) with a clear niche, but the broad trigger ('network endpoints, REST resources, HTTP layer') creates minor overlap risk with closely related sibling data-client skills, placing it at score 4 rather than 5.	4 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: reactive/data-client
Path: .cursor/skills/data-client-rest/SKILL.md
Commit: ef4653f

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.