CtrlK
BlogDocsLog inGet started
Tessl Logo

data-client-schema

Model data with @data-client schemas (Entity, EntityMixin, Collection, Union, Query, Values, All, Invalidate, Lazy, Scalar) for atomic, consistent, referentially-equal async data via normalization, identity-based caching, and a single source of truth. Use when defining or editing pk, static schema, resource()/RestEndpoint schema, mutable lists/maps (push/unshift/assign/remove/move), polymorphic/discriminated types, memoized selectors / derived data, partial/supplementary entities, relational/nested/joined data, optimistic updates, or cache invalidation across @data-client/rest, /endpoint, /graphql, or /normalizr. Apply proactively when discussing data models, remote data shape, caching, normalization, identity, joins, polymorphism, mutable collections, or store consistency.

80

Quality

100%

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

100%

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

The body is a well-structured, lean reference catalog with executable code, explicit lifecycle ordering, and clean one-level-deep progressive disclosure into a verified references directory. It avoids over-explaining basics and keeps each section tightly scoped.

DimensionReasoningScore

Conciseness

The body is lean: tight bullets, two focused code blocks, and a compact method table, with no explanation of concepts Claude already knows; even the denser §5 pk-routing detail earns its place for a complex library, matching the 'every token earns its place' anchor.

3 / 3

Actionability

Provides real, executable TypeScript (Query, Union with discriminator, Collection with argsKey/nestKey) and a concrete extender method table with exact signatures; remaining placeholders (/* ... */, 'other event types') are clearly illustrative of a polymorphic pattern rather than incomplete guidance.

3 / 3

Workflow Clarity

Sections are clearly sequenced (define schemas -> entity practices -> lifecycle -> unions -> collections -> supplementary -> best practices -> mistakes) and the lifecycle section gives explicit ordered sequences (process() -> pk() -> validate() -> visit nested -> mergeWithStore); as a well-organized reference/catalog skill it satisfies the simple-skills allowance for a 3.

3 / 3

Progressive Disclosure

SKILL.md is an overview with inline links to 20 one-level-deep reference files, all real and present in ./references/, plus a final indexed References section; references are clearly signaled and exactly one level deep, matching the score-3 anchor.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a strong, third-person statement that pairs a precise 'what' with dual explicit 'when' triggers, enumerates concrete capabilities, and names a distinct framework niche. It is somewhat dense but every clause carries a concrete action or trigger.

DimensionReasoningScore

Specificity

Enumerates many concrete actions (pk, static schema, resource()/RestEndpoint schema, mutable lists/maps with push/unshift/assign/remove/move, polymorphic/discriminated types, memoized selectors, partial/supplementary entities, relational/nested/joined data, optimistic updates, cache invalidation), matching the 'lists multiple specific concrete actions' anchor and exceeding the score-3 example in breadth.

3 / 3

Completeness

Explicitly answers both 'what' (model data with @data-client schemas for atomic, consistent, referentially-equal async data) and 'when' via both a 'Use when...' and an 'Apply proactively when...' clause, satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

Includes natural discussion terms users would say ('data models, remote data shape, caching, normalization, identity, joins, polymorphism, mutable collections, store consistency') alongside concrete API terms, giving good coverage of natural trigger language; not merely technical jargon.

3 / 3

Distinctiveness Conflict Risk

Tied to a specific framework niche (@data-client/rest, /endpoint, /graphql, /normalizr) with distinctive triggers, making it unlikely to fire for unrelated skills; clear niche as the score-3 anchor requires.

3 / 3

Total

12

/

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.