Agent skill

Data Client React

Use @data-client/react hooks for data fetching, mutations, and rendering - useSuspense, useFetch, useQuery, useCache, useLive, useDLE, useSubscription, useController, DataProvider, AsyncBoundary…

Apache-2.0Auto-check passedDevelopment

Install Data Client React

skills CLI

$ npx skills add reactive/data-client --skill data-client-react -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install reactive/data-client data-client-react --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/reactive/data-client.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/data-client-react .claude/skills/data-client-react && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "data-client-react" agent skill from https://github.com/reactive/data-client/tree/master/.agents/skills/data-client-react into .claude/skills/data-client-react/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data-client-react", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/reactive/data-client/tree/master/.agents/skills/data-client-react

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add reactive/data-client --skill data-client-react -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install reactive/data-client data-client-react --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/reactive/data-client.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/data-client-react .agents/skills/data-client-react && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "data-client-react" agent skill from https://github.com/reactive/data-client/tree/master/.agents/skills/data-client-react into .agents/skills/data-client-react/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data-client-react", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add reactive/data-client --skill data-client-react -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install reactive/data-client data-client-react --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/reactive/data-client.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/data-client-react .cursor/skills/data-client-react && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "data-client-react" agent skill from https://github.com/reactive/data-client/tree/master/.agents/skills/data-client-react into .cursor/skills/data-client-react/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data-client-react", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/reactive/data-client.git --path .agents/skills/data-client-react

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add reactive/data-client --skill data-client-react -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install reactive/data-client data-client-react --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/reactive/data-client.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/data-client-react .gemini/skills/data-client-react && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "data-client-react" agent skill from https://github.com/reactive/data-client/tree/master/.agents/skills/data-client-react into .gemini/skills/data-client-react/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data-client-react", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install reactive/data-client data-client-react

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add reactive/data-client --skill data-client-react -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/reactive/data-client.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/data-client-react .github/skills/data-client-react && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "data-client-react" agent skill from https://github.com/reactive/data-client/tree/master/.agents/skills/data-client-react into .github/skills/data-client-react/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data-client-react", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add reactive/data-client --skill data-client-react -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install reactive/data-client data-client-react --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/reactive/data-client.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/data-client-react .opencode/skills/data-client-react && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "data-client-react" agent skill from https://github.com/reactive/data-client/tree/master/.agents/skills/data-client-react into .opencode/skills/data-client-react/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data-client-react", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: data-client-react
GitHub stars: 2k
Token cost: ~1.9k tokens
SKILL.md length: 371 words
Files: 25 (incl. references)
Skills in repo: 17
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Use @data-client/react hooks for data fetching, mutations, and rendering - useSuspense, useFetch, useQuery, useCache, useLive, useDLE, useSubscription, useController, DataProvider, AsyncBoundary…

Reading/rendering remote data
SKILL.md covers Rendering, Mutations, Helpful hooks and Components, plus 5 more sections
Reaches jsonplaceholder.typicode.com
Triggering mutations

What it does

Data Client React is an agent skill from reactive/data-client. Use @data-client/react hooks for data fetching, mutations, and rendering - useSuspense, useFetch, useQuery, useCache, useLive, useDLE, useSubscription, useController, DataProvider, AsyncBoundary, useLoading, useDebounce. Use when reading/rendering remote data, triggering mutations, doing optimistic updates, real-time subscriptions, or wiring Suspense/error boundaries in React.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 26 other files, including reference files (for example `evals/evals.json`, `references.json` and `references/Actions.md`).

It sits in Development, covering React components and Error handling. It works with React. The repository describes itself as: Async State Management without the Management. REST, GraphQL, SSE, Websockets. The licence is Apache-2.0.

When your agent uses it

Reading/rendering remote data
Triggering mutations
Doing optimistic updates
Real-time subscriptions

Example prompts

“/data-client-react”

What it can do on your machine

Read from SKILL.md and the folder at commit 02c0932. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- jsonplaceholder.typicode.com
Also links to:
- dataclient.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Data Client React loads about 1.9k tokens when it runs, and up to ~40k if it reads all its reference files. Until then it costs about 99 tokens; SKILL.md has 371 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~99
When it runs · the whole SKILL.md, loaded when a task matches: ~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~40k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from reactive/data-client at commit 02c0932, republished under its Apache-2.0 licence (© reactive). 371 words, ~1,889 tokens.

Download SKILL.mdSave it as .claude/skills/data-client-react/SKILL.md (or your agent's skills folder). This skill also uses 24 other files; get the full folder from GitHub.

name: data-client-react
description: Use @data-client/react hooks for data fetching, mutations, and rendering - useSuspense, useFetch, useQuery, useCache, useLive, useDLE, useSubscription, useController, DataProvider, AsyncBoundary, useLoading, useDebounce. Use when reading/rendering remote data, triggering mutations, doing optimistic updates, real-time subscriptions, or wiring Suspense/error boundaries in React.
license: Apache 2.0

Rendering

// GET https://jsonplaceholder.typicode.com/todos/5
const todo = useSuspense(TodoResource.get, { id: 5 });
// GET https://jsonplaceholder.typicode.com/todos
const todoList = useSuspense(TodoResource.getList);
// GET https://jsonplaceholder.typicode.com/todos?userId=1
const todoListByUser = useSuspense(TodoResource.getList, { userId: 1 });
// subscriptions with polling, websockets or SSE
const todo = useLive(TodoResource.get, { id: 5 });
// without fetch
const todo = useCache(TodoResource.get, { id: 5 });
const todo = useQuery(Todo, { id: 5 });
// fetch without Suspense - returns { data, loading, error }
const { data, loading, error } = useDLE(TodoResource.get, { id: 5 });
// subscribe without Suspense (use with useSuspense or useDLE)
useSubscription(TodoResource.get, { id: 5 });
// parallel fetches with React.use()
const postPromise = useFetch(PostResource.get, { id });
const commentsPromise = useFetch(CommentResource.getList, { postId: id });
const post = use(postPromise);
const comments = use(commentsPromise);

For API definitions (like TodoResource), apply the skill "data-client-rest".

Mutations

const ctrl = useController();
// PUT https://jsonplaceholder.typicode.com/todos/5
const updateTodo = todo => ctrl.fetch(TodoResource.update, { id }, todo);
// PATCH https://jsonplaceholder.typicode.com/todos/5
const partialUpdateTodo = todo =>
  ctrl.fetch(TodoResource.partialUpdate, { id }, todo);
// POST https://jsonplaceholder.typicode.com/todos
const addTodoToBeginning = todo =>
  ctrl.fetch(TodoResource.getList.unshift, todo);
// POST https://jsonplaceholder.typicode.com/todos?userId=1
const addTodoToEnd = todo => ctrl.fetch(TodoResource.getList.push, { userId: 1 }, todo);
// DELETE https://jsonplaceholder.typicode.com/todos/5
const deleteTodo = id => ctrl.fetch(TodoResource.delete, { id });
// GET https://jsonplaceholder.typicode.com/todos?userId=1&page=2
const getNextPage = (page) => ctrl.fetch(TodoResource.getList.getPage, { userId: 1, page })

Helpful hooks

tsx

const [handleSubmit, loading, error] = useLoading(
  async data => {
    const post = await ctrl.fetch(PostResource.getList.push, data);
    navigateToPost(post.id);
  },
  [ctrl],
);

tsx

const [query, setQuery] = React.useState('');
const handleChange = e => setQuery(e.currentTarget.value);
const [debouncedQuery, isPending] = useDebounce(query, 200);

return (
  <AsyncBoundary fallback={<Loading />}>
    <IssueList query={debouncedQuery} owner="facebook" repo="react" />
  </AsyncBoundary>
)

Components

Prefer using AsyncBoundary for error handling and loading states unless the codebase has a custom AsyncBoundary that already combines Suspense and ErrorBoundary. Its props are fallback, errorComponent, errorClassName, and listen. It can be used to wrap any component that fetches data.

tsx

<AsyncBoundary listen={history.listen}>
  <TodoList />
</AsyncBoundary>

Type-safe imperative actions

Controller is returned from useController(). It has: ctrl.fetch(), ctrl.fetchIfStale(), ctrl.expireAll(), ctrl.invalidate(), ctrl.invalidateAll(), ctrl.setResponse(), ctrl.set(), ctrl.setError(), ctrl.resetEntireStore(), ctrl.subscribe(), ctrl.unsubscribe().

Write many entities without a fetch with one ctrl.set([Entity], rows). Never loop ctrl.set(Entity, args, row) per row, and never add an endpoint or setResponse() just to batch.

Programmatic queries

const queryRemainingTodos = new Query(
  TodoResource.getList.schema,
  entries => entries.filter(todo => !todo.completed).length,
);

const allRemainingTodos = useQuery(queryRemainingTodos);
const firstUserRemainingTodos = useQuery(queryRemainingTodos, { userId: 1 });

const groupTodoByUser = new Query(
  TodoResource.getList.schema,
  todos => Object.groupBy(todos, todo => todo.userId),
);
const todosByUser = useQuery(groupTodoByUser);

Browser Debugging (Chrome DevTools MCP)

To inspect store state, track dispatched actions, or invoke Controller methods from a browser MCP (user-chrome-devtools), see devtools-debugging. Uses globalThis.__DC_CONTROLLERS__ available in dev mode.

Managers

Custom Managers allow for global side effect handling. This is useful for websockets, SSE, logging, etc. Always use the skill "data-client-manager" when writing managers.

Best Practices & Notes

useDebounce(query, timeout) when rendering async data based on user field inputs
[handleSubmit, loading, error] = useLoading() when tracking async mutations
Prefer smaller React components that do one thing
Co-locate data bindings: call useSuspense/useDLE/useCache/useQuery in the component that renders the data — don't prop drill
Don't hide data bindings inside custom hooks: wrapping them obfuscates a component's data dependencies and couples data logic to view code, causing drift. Put tightly coupled data transformations in a Query schema (with the data model, e.g. src/resources/) so they stay reusable and evolve independently of views
For tests, apply the skill "data-client-react-testing"

Show full SKILL.md (114 more words)Show less

References

For detailed API documentation, see the references directory:

useSuspense;_pagination.md - Fetch with Suspense
useFetch - Fetch for React.use() and parallel loading
useQuery - Read from cache without fetch
useCache - Read from cache (nullable)
useLive;_useLive.md - Fetch + subscribe to updates
useDLE - Fetch without Suspense (returns data/loading/error)
useSubscription - Subscribe to updates (polling/websocket/SSE)
useController - Access Controller
Controller - Imperative actions
AsyncBoundary;_AsyncBoundary.md - Error/loading boundary
useLoading;_useLoading.md - Track async mutation state
useDebounce - Debounce values
DataProvider - Root provider
data-dependency - Rendering guide
mutations;_VoteDemo.md - Mutations guide
Actions - Store action types (FETCH, SET, etc.)
devtools-debugging - Debug with Chrome DevTools MCP

ALWAYS follow these patterns and refer to the official docs for edge cases. Prioritize code generation that is idiomatic, type-safe, and leverages automatic normalization/caching via skill "data-client-schema" definitions.

Files

SKILL.md and 24 other files (references) in .agents/skills/data-client-react of reactive/data-client.

SKILL.md
evals/evals.json
references.json
references/Actions.md
references/AsyncBoundary.md
references/Controller.md
references/DataProvider.md
references/_AsyncBoundary.md
references/_VoteDemo.md
references/_pagination.md
references/_useLive.md
references/_useLoading.md
references/data-dependency.md
references/devtools-debugging.md
references/mutations.md
references/useCache.md
references/useController.md
references/useDLE.md
references/useDebounce.md
… and 6 more

Open the folder on GitHubat commit 02c0932

Compare with similar skills

Data Client React next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Data Client React compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Data Client React this skillreactive/data-client	2k	—	~1.9k	Automated safety check: Pass	Apache-2.0	today
React Fetch Cache Patternspproenca/dot-skills	214	—	~3k	Automated safety check: Pass	MIT	1 mo ago
Typescript Rulesshinpr/claude-code-workflows	690	—	~1.8k	Automated safety check: Pass	MIT	6 days ago
React UI State PatternsChrisWiles/claude-code-showcase	6.1k	7 repos	~1.6k	Automated safety check: Pass	None	9 mo ago
@pierre/diffs Code Renderingpierrecomputer/pierre	6.2k	2 repos	~803	Automated safety check: Pass	Apache-2.0	yesterday
OpenTUI Terminal Interfacescline/cline	70k	—	~1.9k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

React Fetch Cache Patterns
pproenca/dot-skills
React data-fetching patterns at scale — recommender carousels, infinite feeds, pages with many parallel fetches, dashboards.
214 GitHub stars~3k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
Typescript Rules
shinpr/claude-code-workflows
React/TypeScript frontend development rules including type safety, component design, state management, and error handling.
690 GitHub stars~1.8k tokensUpdated 6 days ago
Frontend & DesignAuto-check passed
React UI State Patterns
ChrisWiles/claude-code-showcase
Sets patterns for React interfaces: when to show loading spinners or skeletons, how to surface errors, how to disable buttons during async work and how to handle empty lists.
6.1k GitHub starsUsed in 7 repos~1.6k tokens
Frontend & DesignAuto-check passed
@pierre/diffs Code Rendering
pierrecomputer/pierre
Guides an agent through using @pierre/diffs to render syntax-highlighted files and diffs, and to build editing and review surfaces in React or plain JavaScript.
6.2k GitHub starsUsed in 2 repos~803 tokens
DevelopmentAuto-check passed
OpenTUI Terminal Interfaces
cline/cline
Helps build terminal user interfaces with OpenTUI using its core imperative API or its React and Solid reconcilers, with references for layout, keyboard, animation and testing.
70k GitHub stars~1.9k tokensUpdated yesterday
DevelopmentAuto-check passed
Zod
jasonjgardner/blockbench-mcp-plugin
Zod schema validation best practices for type safety, parsing, and error handling.
488 GitHub starsUsed in 3 repos~1.4k tokens
DevelopmentAuto-check passed

Questions about Data Client React

What does Data Client React do?

Use @data-client/react hooks for data fetching, mutations, and rendering - useSuspense, useFetch, useQuery, useCache, useLive, useDLE, useSubscription, useController, DataProvider, AsyncBoundary…. Data Client React is an agent skill from reactive/data-client. Use @data-client/react hooks for data fetching, mutations, and rendering - useSuspense, useFetch, useQuery, useCache, useLive, useDLE, useSubscription, useController, DataProvider, AsyncBoundary, useLoading, useDebounce.

When should I use Data Client React?

Data Client React fits situations like: reading/rendering remote data; triggering mutations; doing optimistic updates; real-time subscriptions.

How do I install Data Client React in Claude Code?

Run `npx skills add reactive/data-client --skill data-client-react -a claude-code`. Or copy the skill folder (.agents/skills/data-client-react in reactive/data-client) into .claude/skills/data-client-react in your project. Claude Code loads it when a task matches its description.

How do I install Data Client React in Codex?

Run `npx skills add reactive/data-client --skill data-client-react -a codex`. Or copy the skill folder (.agents/skills/data-client-react in reactive/data-client) into .agents/skills/data-client-react in your project. Codex loads it when a task matches its description.

Can I use Data Client React in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add reactive/data-client --skill data-client-react -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/data-client-react, .gemini/skills/data-client-react, .github/skills/data-client-react and .opencode/skills/data-client-react in your project.

What does Data Client React need to run?

SKILL.md names no scripts, command-line tools or credentials: Data Client React is instructions for the agent only.

Does Data Client React access the network?

SKILL.md names 2 domains. In commands or code: jsonplaceholder.typicode.com; the agent is likely to contact it when it follows the instructions. As links in the text: dataclient.io. This is read from the text; nothing was executed.

Is Data Client React safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Data Client React use?

Data Client React is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Data Client React use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 38k tokens, read only when the agent opens those files.

What are the alternatives to Data Client React?

Skills that share tags, products or a category with Data Client React: React Fetch Cache Patterns (pproenca/dot-skills, 214 stars), Typescript Rules (shinpr/claude-code-workflows, 690 stars), React UI State Patterns (ChrisWiles/claude-code-showcase, 6.1k stars) and @pierre/diffs Code Rendering (pierrecomputer/pierre, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Data Client React?

reactive (a GitHub organization) maintains it in reactive/data-client, which has 2,037 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 7, 2026.

Source: reactive/data-client on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Data Client React

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Rendering

Mutations

Helpful hooks

Components

Type-safe imperative actions

Programmatic queries

Browser Debugging (Chrome DevTools MCP)

Managers

Best Practices & Notes

References

Files

Compare with similar skills

Similar skills

More from reactive/data-client

Related

Questions about Data Client React