CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

78%

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 ./.cursor/skills/data-client-rest/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable API modeling guide with excellent code examples and clean progressive disclosure. The main drag is conciseness: redundant directive repetition, an out-of-place instruction, and a duplicated reference index.

Suggestions

Remove the misplaced line 159 directive ("When asked to browse or navigate to a web address, actual visit the address") - it is unrelated to REST resource modeling.

De-duplicate the reference listings: either keep the inline links in the body or the trailing categorized index, not both, since they point to the same files.

Consolidate the repeated "Always follow these patterns..." imperatives (lines 9, 16, and 191) into a single concise directive to reduce token overhead.

DimensionReasoningScore

Conciseness

The core is lean (code, bullet field lists), but there is padding: repeated bold imperatives ("Always follow these patterns..." at lines 9 and 191), a misplaced irrelevant directive ("When asked to browse or navigate to a web address, actual visit the address" at line 159), and a trailing reference index that duplicates the inline links already present in the body.

2 / 3

Actionability

Provides fully executable, copy-paste-ready TypeScript examples for resource() definition, useSuspense rendering, mutations, custom RestEndpoint, getOptimisticResponse, and extend(), plus concrete typing tips anchored to real APIs.

3 / 3

Workflow Clarity

Content is organized into numbered sections with a "Common Mistakes to Avoid" guardrail, but there are no validation checkpoints or explicit sequencing beyond section numbers; the section order is logical but loosely connected.

2 / 3

Progressive Disclosure

A concise overview body links to one-level-deep reference files inline, and a categorized trailing index (References / Guides / Concepts) maps to real symlinked bundle files, giving easy navigation; content is appropriately split between SKILL.md and references.

3 / 3

Total

10

/

12

Passed

Description

85%

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, capability-dense description with an explicit use-when clause and a clear niche. Its main weakness is over-reliance on API-symbol jargon that users would rarely say verbatim when asking for help.

DimensionReasoningScore

Specificity

Lists many concrete capabilities - "resource(), RestEndpoint, CRUD (GET/POST/PUT/PATCH/DELETE), HTTP fetch, normalize, cache, ... optimistic updates, polling, file download" - matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (the long capability list) and when via the "Use when defining or modifying network endpoints, REST resources, or the HTTP layer" trigger clause.

3 / 3

Trigger Term Quality

Natural terms like "REST APIs", "REST resources", "network endpoints", and "HTTP layer" are present, but the list is front-loaded with library-internal symbols users would not naturally say ("path-to-regexp parameters", "parseResponse", "urlPrefix", "blob"), so coverage is mixed rather than fully natural.

2 / 3

Distinctiveness Conflict Risk

Targets a distinct niche (@data-client/rest resource modeling) with explicit trigger language, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
reactive/data-client
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.