CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

data-client-rest-setup

Set up and migrate to @data-client/rest for REST APIs. Detects existing HTTP patterns (axios, fetch, ky, superagent, got) and migrates them. Creates custom RestEndpoint base class with common behaviors. Use when adopting @data-client/rest in a new or existing project.

64

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%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, highly actionable setup guide with excellent progressive disclosure and a clear detection-driven workflow. The main weakness is the absence of validation checkpoints after batch migration steps (the codemod), and templates referencing undefined helper functions.

Suggestions

Add a validation checkpoint after migrations, e.g. "After running the codemod, run typecheck/tests and fix remaining errors before proceeding to base class setup" — this batch operation currently has no verify step, capping workflow clarity.

Define or flag the placeholder helpers in the code templates (getValidToken(), getCsrfToken(), parseCSV(), AuthContext) as project-specific stubs so the snippets are fully copy-paste runnable.

Trim the "Full Example with Multiple Overrides" section, which largely duplicates the individual lifecycle override snippets shown just above it.

DimensionReasoningScore

Conciseness

The body is dense and efficient — detection table, terse code blocks, pointed notes like "Use `body: {} as BodyType` (truthy value)" — with only minor trimmable redundancy, mainly the "Full Example with Multiple Overrides" re-presenting overrides already shown individually. Fits anchor 4 rather than anchor 5's every-token-earns-its-place, and is far from anchor 3's unnecessary explanation.

4 / 5

Actionability

Concrete install commands for three package managers, detection regexes, an executable codemod command, and copy-paste-ready TypeScript templates cover the common cases. Minor gaps: helpers like getValidToken(), getCsrfToken(), and parseCSV() are referenced but undefined, so the templates are not fully self-contained — anchor 4 rather than 5.

4 / 5

Workflow Clarity

Steps are clearly sequenced (install → detect/migrate → base class → usage) with checklists and ambiguity handling ("ask the user" with a script), but the workflow includes batch operations — the jscodeshift codemod over the whole src/ tree — with no validation checkpoint such as a typecheck or test run after migration. Per the rubric's cap for batch operations without validation, this fits anchor 3 (sequence present, checkpoints missing) despite the strong sequencing.

3 / 5

Progressive Disclosure

SKILL.md is a clear overview; per-library migrations are split into separate reference files, each annotated with what it covers; references are one level deep (no references/ links inside the reference files) and all linked paths exist on disk; the Vue variant convention is stated and the .vue.md files exist. This matches anchor 5's well-signaled one-level-deep structure with no organization gaps found.

5 / 5

Total

16

/

20

Passed

Description

80%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 description: third-person voice, explicit "Use when..." clause, and concrete actions naming all five detectable HTTP libraries. Main gaps are a when-clause that misses migration-specific triggers and slightly thin synonym coverage.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Set up and migrate to @data-client/rest", "Detects existing HTTP patterns (axios, fetch, ky, superagent, got)", "Creates custom RestEndpoint base class" — with all five source libraries named, giving comprehensive coverage of the skill's scope rather than the minor gaps of anchor 4.

5 / 5

Completeness

Both "what" (setup, detection, migration, base class creation) and "when" ("Use when adopting @data-client/rest in a new or existing project") are answered explicitly, but the when-clause only echoes "adopting" and omits concrete migration triggers like "migrating from axios/fetch", fitting anchor 4's "when could be more explicit or specific".

4 / 5

Trigger Term Quality

Natural terms a user would say are present ("REST APIs", "axios", "fetch", "ky", "superagent", "got", "migrate"), but a few common synonyms like "HTTP client", "data fetching", or "Data Client" without the package name are missing, fitting anchor 4 rather than the synonym-level comprehensiveness of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (@data-client/rest setup and migration with named source libraries), but the skill body reveals sibling skills ("data-client-rest", "data-client-schema", "data-client-react/vue") covering adjacent resource and endpoint patterns, creating minor overlap risk with closely related skills per anchor 4.

4 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

reactive/data-client

Path

.agents/skills/data-client-rest-setup/SKILL.md

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.