supabase

Query and mutate Supabase data via the PostgREST API.

4|3|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/qhkm/zeptoclaw-skills --skill supabase-qhkm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase
Source: https://github.com/qhkm/zeptoclaw-skills/tree/main/supabase
Command: npx skills add https://github.com/qhkm/zeptoclaw-skills --skill supabase-qhkm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Query and mutate data in a Supabase project via the PostgREST API, enabling automated administration and data workflows.

Core Features & Use Cases

  • Query data from tables using REST endpoints with filters and ordering.
  • Insert, update, and delete rows to keep datasets in sync with applications.
  • List and manage auth users and perform admin operations when using the service key.

Quick Start

Export your project API keys and invoke REST calls to rest/v1 endpoints to read or modify data.

Frequently Asked Questions about supabase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query Supabase data via PostgREST endpoints?

You can query Supabase data by sending HTTP requests to the /rest/v1 endpoints, applying filters and ordering to retrieve specific table rows directly from your project.

Can I manage Supabase auth users using a REST API?

Yes, you can list and manage auth users by authenticating with your project's service key, which grants the elevated privileges required for performing admin operations.

What's the best way to automate Supabase admin tasks like inserting and updating rows?

Automating Supabase admin tasks involves invoking REST calls to mutate data at /rest/v1 endpoints, enabling you to insert, update, and delete records to keep datasets in sync.

Do I need a service key to delete records in a Supabase database?

While standard API keys allow basic row mutations, a service key is specifically required for admin operations like listing and managing auth users within your Supabase project.

Does this approach work for both development and production Supabase environments?

Yes, querying and mutating data via PostgREST works across both development and production environments, provided you supply the proper API keys and REST endpoints.

What are the limitations of using PostgREST for Supabase database management?

PostgREST is limited to interacting with data via REST endpoints at /rest/v1, meaning complex SQL logic or database schema modifications must be handled through other database management tools.