Official agent skill

Studio Queries

React Query conventions for data fetching in Supabase Studio.

OfficialApache-2.0Auto-check passedBackend & APIs

Install Studio Queries

skills CLI

$ npx skills add supabase/supabase --skill studio-queries -a claude-code

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

GitHub CLI

$ gh skill install supabase/supabase studio-queries --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/supabase/supabase.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/studio-queries .claude/skills/studio-queries && 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 "studio-queries" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-queries into .claude/skills/studio-queries/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-queries", 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/supabase/supabase/tree/master/.agents/skills/studio-queries

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 supabase/supabase --skill studio-queries -a codex

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

GitHub CLI

$ gh skill install supabase/supabase studio-queries --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/studio-queries .agents/skills/studio-queries && 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 "studio-queries" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-queries into .agents/skills/studio-queries/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-queries", 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 supabase/supabase --skill studio-queries -a cursor

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

GitHub CLI

$ gh skill install supabase/supabase studio-queries --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/studio-queries .cursor/skills/studio-queries && 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 "studio-queries" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-queries into .cursor/skills/studio-queries/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-queries", 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/supabase/supabase.git --path .agents/skills/studio-queries

--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 supabase/supabase --skill studio-queries -a gemini-cli

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

GitHub CLI

$ gh skill install supabase/supabase studio-queries --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/supabase/supabase.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/studio-queries .gemini/skills/studio-queries && 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 "studio-queries" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-queries into .gemini/skills/studio-queries/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-queries", 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 supabase/supabase studio-queries

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 supabase/supabase --skill studio-queries -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/studio-queries .github/skills/studio-queries && 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 "studio-queries" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-queries into .github/skills/studio-queries/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-queries", 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 supabase/supabase --skill studio-queries -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 supabase/supabase studio-queries --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/studio-queries .opencode/skills/studio-queries && 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 "studio-queries" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-queries into .opencode/skills/studio-queries/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-queries", 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: studio-queries
GitHub stars: 111k
Token cost: ~1.3k tokens
SKILL.md length: 223 words
Files: 1
Skills in repo: 22
Repo updated: Oct 8, 2026
First seen: Oct 8, 2026
Licence: Apache-2.0

At a glance

React Query conventions for data fetching in Supabase Studio.

Reviewing query hooks
SKILL.md covers Query Keys, Query Options (preferred…, Using Query Options in… and Imperative Fetching (outside…, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Query keys in apps/studio/data/ — including adding the first fetch

What it does

Studio Queries is an agent skill from supabase/supabase, published by the product's own GitHub organization. React Query conventions for data fetching in Supabase Studio. Use when writing or reviewing query hooks, mutation hooks, or query keys in apps/studio/data/ — including adding the first fetch or mutation for a new API endpoint or resource. Covers queryOptions pattern, keys.ts structure, mutation hook template, and imperative fetching.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering REST APIs. It works with Supabase and TanStack. The repository describes itself as: The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications. The licence is Apache-2.0.

When your agent uses it

Reviewing query hooks
Query keys in apps/studio/data/ — including adding the first fetch
Mutation for a new API endpoint

Example prompts

“/studio-queries”

What it can do on your machine

Read from SKILL.md and the folder at commit 26c838a. 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
No URLs in SKILL.md.
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

Studio Queries loads about 1.3k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 223 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~88
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

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 supabase/supabase at commit 26c838a, republished under its Apache-2.0 licence (© supabase). 223 words, ~1,305 tokens.

Download SKILL.mdSave it as .claude/skills/studio-queries/SKILL.md (or your agent's skills folder).

name: studio-queries
description: React Query conventions for data fetching in Supabase Studio. Use when writing or reviewing query hooks, mutation hooks, or query keys in apps/studio/data/ — including adding the first fetch or mutation for a new API endpoint or resource. Covers queryOptions pattern, keys.ts structure, mutation hook template, and imperative fetching.

Studio Queries & Mutations (React Query)

Follow the patterns in apps/studio/data/. Reference examples:

Query options: apps/studio/data/table-editor/table-editor-query.ts
Mutation hook: apps/studio/data/edge-functions/edge-functions-update-mutation.ts
Keys: apps/studio/data/edge-functions/keys.ts

Query Keys

Define a keys.ts per domain. Export *Keys helpers using array keys with as const. Never inline query keys in components.

export const edgeFunctionsKeys = {
  list: (projectRef: string | undefined) => ['projects', projectRef, 'edge-functions'] as const,
  detail: (projectRef: string | undefined, slug: string | undefined) =>
    ['projects', projectRef, 'edge-function', slug, 'detail'] as const,
}

Query Options (preferred pattern)

Use queryOptions from @tanstack/react-query. This gives type safety and works with both useQuery() and queryClient.fetchQuery().

Rules:

Export XVariables, XData, and XError types (prefixed with the domain name)
Implement a private getX(variables, signal?) function:
- Throws if required variables are missing
- Passes signal for cancellation
- Calls handleError(error) on failure (which throws); returns data on success
- Not exported — use queryClient.fetchQuery(xQueryOptions(...)) for imperative fetching
Export xQueryOptions() using queryOptions
Gate with enabled so the query doesn't run until required variables exist
Platform-only queries: include IS_PLATFORM from lib/constants in enabled
Don't add extra params to xQueryOptions — callers override by destructuring: { ...xQueryOptions(vars), enabled: true }

import { queryOptions } from '@tanstack/react-query'

import { xKeys } from './keys'
import { get, handleError } from '@/data/fetchers'
import { IS_PLATFORM } from '@/lib/constants'
import { ResponseError } from '@/types'

export type XVariables = { projectRef?: string }
export type XError = ResponseError

async function getX({ projectRef }: XVariables, signal?: AbortSignal) {
  if (!projectRef) throw new Error('projectRef is required')
  const { data, error } = await get('/v1/projects/{ref}/x', {
    params: { path: { ref: projectRef } },
    signal,
  })
  if (error) handleError(error)
  return data
}

export type XData = Awaited<ReturnType<typeof getX>>

export const xQueryOptions = ({ projectRef }: XVariables) =>
  queryOptions({
    queryKey: xKeys.list(projectRef),
    queryFn: ({ signal }) => getX({ projectRef }, signal),
    enabled: IS_PLATFORM && typeof projectRef !== 'undefined',
  })

Using Query Options in Components

import { useQuery } from '@tanstack/react-query'

import { xQueryOptions } from '@/data/x/x-query'

const { data, isPending, isError } = useQuery(xQueryOptions({ projectRef: project?.ref }))

Imperative Fetching (outside React or in callbacks)

const queryClient = useQueryClient()
const { data: project } = useSelectedProjectQuery()

const handleClick = useCallback(
  async (id: number) => {
    const data = await queryClient.fetchQuery(xQueryOptions({ id, projectRef: project?.ref }))
    // use data...
  },
  [project?.ref, queryClient]
)

Mutation Hook

Export a Variables type with projectRef, identifiers, and payload
Implement a private updateX(vars) function with required variable validation and handleError
Wrap in useXMutation():
- Accepts UseMutationOptions (omit mutationFn)
- Invalidates list() + detail() keys in onSuccess with await Promise.all([...])
- Defaults to toast.error(...) when onError isn't provided

import { useMutation, UseMutationOptions, useQueryClient } from '@tanstack/react-query'
import { toast } from 'sonner'

import { xKeys } from './keys'

type XUpdateVariables = { projectRef: string; slug: string; payload: XPayload }

export const useXUpdateMutation = ({
  onSuccess,
  onError,
  ...options
}: UseMutationOptions<XData, XError, XUpdateVariables> = {}) => {
  const queryClient = useQueryClient()
  return useMutation({
    mutationFn: updateX,
    async onSuccess(data, variables, context) {
      await Promise.all([
        queryClient.invalidateQueries({
          queryKey: xKeys.detail(variables.projectRef, variables.slug),
        }),
        queryClient.invalidateQueries({ queryKey: xKeys.list(variables.projectRef) }),
      ])
      await onSuccess?.(data, variables, context)
    },
    async onError(error, variables, context) {
      if (onError === undefined) toast.error(`Failed to update: ${error.message}`)
      else onError(error, variables, context)
    },
    ...options,
  })
}

Component Usage

Use React Query v5 flags: isPending for initial load, isFetching for background refetches
Render states explicitly in order: pending → error → success

Files

Just SKILL.md in .agents/skills/studio-queries of supabase/supabase.

Open the folder on GitHubat commit 26c838a

Compare with similar skills

Studio Queries 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.

Studio Queries compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Studio Queries this skillsupabase/supabase	111k	—	~1.3k	Automated safety check: Pass	Apache-2.0	today
API Endpointopenathleteorg/openathlete	100	—	~682	Automated safety check: Pass	AGPL-3.0	yesterday
Shadmin CLIahaodev/shadmin	174	—	~1.1k	Automated safety check: Notes	MIT	6 days ago
Supabase APImajiayu000/claude-skill-registry	666	1 repos	~2k	Automated safety check: Pass	MIT	yesterday
Security Reviewjewbetcha/opentrace	116	18 repos	~3.1k	Automated safety check: Notes	MIT	4 mo ago
Add Backendahpxex/open-dashboard	146	—	~3.6k	Automated safety check: Pass	MIT	3 mo ago

Similar skills

API Endpoint
openathleteorg/openathlete
Add or change an OpenAthlete API endpoint end to end, from the shared Zod schema to the NestJS controller and service, the web API client, the React Query hook and the UI, with tests.
100 GitHub stars~682 tokensUpdated yesterday
Backend & APIsAuto-check passed
Shadmin CLI
ahaodev/shadmin
A skill your agent uses when the user asks to query Shadmin admin platform resources (users, roles, menus, registered API resources) from a terminal — for example "list shadmin users", "show shadmin…
174 GitHub stars~1.1k tokensUpdated 6 days ago
Backend & APIsAuto-check: notes
Supabase API
majiayu000/claude-skill-registry
Supabase JavaScript client API and REST API usage. An agent skill from majiayu000/claude-skill-registry.
666 GitHub starsUsed in 1 repo~2k tokens
Backend & APIsAuto-check passed
Security Review
jewbetcha/opentrace
A skill your agent uses when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features.
116 GitHub starsUsed in 18 repos~3.1k tokens
SecurityAuto-check: notes
Add Backend
ahpxex/open-dashboard
Everything about the data layer — pick one of six ready-to-run backend templates (TanStack Start + Drizzle + better-auth, Hono + Drizzle + better-auth, Hono + Prisma + better-auth, Hono + Drizzle +…
146 GitHub stars~3.6k tokensUpdated 3 mo ago
DatabasesAuto-check passed
Security Review
affaan-m/ECC
Kimlik doğrulama eklerken, kullanıcı girdisi işlerken, secret'larla çalışırken, API endpoint'leri oluştururken veya ödeme/hassas özellikler uygularken bu skill'i kullanın.
275k GitHub starsUsed in 1 repo~3.2k tokens
SecurityAuto-check: notes

More from supabase/supabase

All 22 skills in this repo

Vercel Composition Patterns
supabase/supabase
Official
React composition patterns that scale. An agent skill from supabase/supabase.
111k GitHub starsUsed in 59 repos~726 tokens
Auto-check passed
Clickhouse Logs Queries
supabase/supabase
Official
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).
111k GitHub stars~2.4k tokensUpdated today
Auto-check passed
Review The Docs
supabase/supabase
Official
Review Supabase docs changes locally in your supabase/supabase checkout — either an open PR (triage, classify, verify) or your own branch before opening a PR (local self-review).
111k GitHub stars~4.6k tokensUpdated today
Auto-check passed
Vitest
supabase/supabase
Official
Vitest API and config reference (Jest-compatible) — mocking with vi., spies, fake timers, coverage configuration, fixtures, snapshots, and test filtering.
111k GitHub starsUsed in 12 repos~1.1k tokens
Auto-check passed
Safe SQL Execution
supabase/supabase
Official
A skill your agent uses whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix…
111k GitHub stars~4.2k tokensUpdated today
Auto-check passed
Studio E2E Tests
supabase/supabase
Official
Write and run Playwright E2E tests for Supabase Studio (e2e/studio).
111k GitHub stars~2.8k tokensUpdated today
Auto-check passed

Works with

Questions about Studio Queries

What does Studio Queries do?

React Query conventions for data fetching in Supabase Studio. Studio Queries is an agent skill from supabase/supabase, published by the product's own GitHub organization. React Query conventions for data fetching in Supabase Studio.

When should I use Studio Queries?

Studio Queries fits situations like: reviewing query hooks; query keys in apps/studio/data/ — including adding the first fetch; mutation for a new API endpoint.

How do I install Studio Queries in Claude Code?

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

How do I install Studio Queries in Codex?

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

Can I use Studio Queries 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 supabase/supabase --skill studio-queries -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/studio-queries, .gemini/skills/studio-queries, .github/skills/studio-queries and .opencode/skills/studio-queries in your project.

What does Studio Queries need to run?

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

Does Studio Queries access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Studio Queries 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 Studio Queries use?

Studio Queries is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Studio Queries use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Studio Queries?

Skills that share tags, products or a category with Studio Queries: API Endpoint (openathleteorg/openathlete, 100 stars), Shadmin CLI (ahaodev/shadmin, 174 stars), Supabase API (majiayu000/claude-skill-registry, 666 stars) and Security Review (jewbetcha/opentrace, 116 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Studio Queries?

supabase (a GitHub organization, an official publisher) maintains it in supabase/supabase, which has 111,222 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 8, 2026.

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

Install Studio Queries

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

Studio Queries & Mutations (React Query)

Query Keys

Query Options (preferred pattern)

Using Query Options in Components

Imperative Fetching (outside React or in callbacks)

Mutation Hook

Component Usage

Files

Compare with similar skills

Similar skills

More from supabase/supabase

Related

Questions about Studio Queries