data-client-manager

Implement @data-client Managers for global/background side effects - websocket, SSE, polling, real-time updates, subscriptions, logging, analytics, metrics/timing, error reporting (Sentry), toast notifications, refetch on window focus or network reconnect, cross-tab sync (BroadcastChannel), offline persistence (localStorage/IndexedDB), auth logout on 401, middleware, intercepting Controller actions, DataProvider managers prop, redux-style action handling. Use when adding cross-cutting store behavior, reacting to dispatched actions, or handling external event streams.

Quality

89%

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

Quality

Content

86%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 guide: a routing table for use cases, three complete executable manager examples, and a clearly signaled one-level-deep reference bundle. It loses only minor points for repeated actionTypes/dispatcher guidance and the absence of explicit verification checkpoints.

Suggestions

Deduplicate the 'Always use actionTypes when comparing action.type' guidance and the actionTypes member list — state each once, ideally in the Actions reference section.

Consolidate the Controller dispatcher and accessor method lists into a single reference rather than repeating them across 'Dispatching actions' and 'Reading and Consuming Actions'.

Add a brief verify/check step for the Usage wiring (e.g., confirm the manager appears in the DataProvider managers array and that init/cleanup fire) to give the implementation path an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	Largely lean — a compact use-case table plus three focused code examples and a usage snippet, with no padding of concepts Claude already knows. Minor redundancy holds it below 5: the 'Always use actionTypes' guidance and the actionTypes member list are each stated twice, and the dispatcher list is duplicated across sections.	4 / 5
Actionability	Provides complete, copy-paste-ready TypeScript classes (TimeManager, LoggingManager, CustomSubsManager) with imports and the full Manager/Middleware shape, concrete dispatcher and accessor method lists, and a 'Key technique' column pinning the exact API call per use case.	5 / 5
Workflow Clarity	The use-case table clearly routes each scenario to a reference and a key technique, and the init()/cleanup() lifecycle is shown in code, giving a clear implementation path. It is not a destructive/batch skill so the validation cap does not apply, but there are no explicit build/verify checkpoints for the pattern, keeping it just below 5.	4 / 5
Progressive Disclosure	SKILL.md is an overview that points to a real one-level-deep reference bundle (Manager, Actions, Controller, LogoutManager, getDefaultManagers, managers — all present in ./references/), with a References section and a use-case table that links to named sections, making navigation easy.	5 / 5
	Total	18 / 20 Passed

Description

92%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 comprehensively lists concrete capabilities and pairs them with an explicit 'Use when' trigger clause, tightly scoped to @data-client Managers. The only weakness is that some listed terms lean toward library jargon rather than the natural phrasings users would say.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete capabilities — 'websocket, SSE, polling, real-time updates, subscriptions, logging, analytics, metrics/timing, error reporting (Sentry), toast notifications, refetch on window focus or network reconnect, cross-tab sync (BroadcastChannel), offline persistence (localStorage/IndexedDB), auth logout on 401, middleware' — giving comprehensive, specific coverage rather than vague abstraction.	5 / 5
Completeness	Explicitly answers both 'what' ('Implement @data-client Managers for global/background side effects - ...') and 'when' with a concrete 'Use when adding cross-cutting store behavior, reacting to dispatched actions, or handling external event streams.' clause.	5 / 5
Trigger Term Quality	Strong natural terms a user would actually say ('websocket', 'SSE', 'polling', 'logging', 'analytics', 'toast notifications', 'refetch on window focus', 'auth logout on 401') with some synonyms, but interleaved with library-specific jargon ('redux-style action handling', 'intercepting Controller actions', 'DataProvider managers prop') that is less natural as a trigger phrase.	4 / 5
Distinctiveness Conflict Risk	Scoped to a specific library's extension mechanism ('@data-client Managers') with niche triggers ('cross-cutting store behavior', 'reacting to dispatched actions', 'external event streams'), giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	19 / 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-manager/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.