[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FC0JD8WSSZ652CBHJRNY3P":3,"skill-same:01M6FC0JD8WSSZ652CBHJRNY3P":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":30,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6FC0JD8WSSZ652CBHJRNY3P","supabase",null,"Use when doing ANY task involving Supabase.","boisenoise\u002Fskills-collections","boisenoise","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F193180?v=4","01M6CDBDQK6BDN55ZMA6B6PKBM","01M6CDBDVSJ3JPTBYN26FZ7TZK",12,"MIT","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-supabase\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"github","official","license","https","use","agent-skills","task","main","wed","critical","tree","blob","when","2026","2026-11-10 10:12:30",false,"---\nname: supabase\ndescription: \"Use when doing ANY task involving Supabase.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fsupabase\u002Fagent-skills\u002Ftree\u002Fmain\u002Fskills\u002Fsupabase\nsource_repo: supabase\u002Fagent-skills\nsource_type: official\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fsupabase\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Supabase\n## When to Use\n\nUse when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase\u002Fssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, session handling and access policies.\n\n\n## Core Principles\n\n**1. Supabase changes frequently — verify against changelog and current docs before implementing.**\nDo not rely on training data for Supabase features. Function signatures, config.toml settings, and API conventions change between versions.\n\nFirst, fetch `https:\u002F\u002Fsupabase.com\u002Fchangelog.md` (a lightweight summary index — not a heavy pull), scan for `breaking-change` tags relevant to your task, and follow the linked page for any that apply. Then look up the relevant topic using the documentation access methods below.\n\n**2. Verify your work.**\nVerify with the smallest relevant check in an authorized local\u002Ftest environment; use role-specific positive and negative policy tests for access changes. A SQL query is not appropriate verification for every UI, auth or docs change. State any unavailable check rather than issuing production mutations for verification.\n\n**3. Recover from errors, don't loop.**\nIf an approach fails after 2-3 attempts, stop and reconsider. Try a different method, check documentation, inspect the error more carefully, and review relevant logs when available. Supabase issues are not always solved by retrying the same command, and the answer is not always in the logs, but logs are often worth checking before proceeding.\n\n**4. Exposing tables to the Data API:** Depending on the user's [Data API settings](https:\u002F\u002Fsupabase.com\u002Fdashboard\u002Fproject\u002F\u003Cref>\u002Fintegrations\u002Fdata_api\u002Fsettings), newly created tables may not be automatically exposed via the Data (REST) API. If this is the case, `anon` and `authenticated` roles will need to be explicitly granted access.\n\n> Note that this is separate from RLS, which controls which _rows_ are visible once a table is accessible, not whether the table is accessible at all.\n\nWhen a user reports a SQL-created table is unexpectedly inaccessible, check their Data API settings and whether the roles have been granted access via explicit `GRANT` SQL. When granting public (`anon`\u002F`authenticated`) access, always enable RLS too. See [Exposing a Table to the Data API](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fapi\u002Fsecuring-your-api.md) for the full setup workflow.\n\n**5. RLS in exposed schemas.**\nEnable RLS on every table in any exposed schema, which includes `public` by default. This is critical in Supabase because tables in exposed schemas can be reachable through the Data API when the `anon`\u002F`authenticated` roles have access (see [Exposing a Table to the Data API](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fapi\u002Fsecuring-your-api.md)). For private schemas, prefer RLS as defense in depth. After enabling RLS, create policies that match the actual access model rather than defaulting every table to the same `auth.uid()` pattern.\n\n**6. Security checklist.**\nWhen working on any Supabase task that touches auth, RLS, views, storage, or user data, run through this checklist. These are Supabase-specific security traps that silently create vulnerabilities:\n\n- **Auth and session security**\n  - **Never use `user_metadata` claims in JWT-based authorization decisions.** In Supabase, `raw_user_meta_data` is user-editable and can appear in `auth.jwt()`, so it is unsafe for RLS policies or any other authorization logic. Store authorization data in `raw_app_meta_data` \u002F `app_metadata` instead.\n  - **Deleting a user does not invalidate existing access tokens.** Sign out or revoke sessions first, keep JWT expiry short for sensitive apps, and for strict guarantees validate `session_id` against `auth.sessions` on sensitive operations.\n  - **If you use `app_metadata` or `auth.jwt()` for authorization, remember JWT claims are not always fresh until the user's token is refreshed.**\n\n- **API key and client exposure**\n  - **Never expose the `service_role` or secret key in public clients.** Prefer publishable keys for frontend code. Legacy `anon` keys are only for compatibility. In Next.js, any `NEXT_PUBLIC_` env var is sent to the browser.\n\n- **RLS, views, and privileged database code**\n  - **Views bypass RLS by default.** In Postgres 15 and above, use `CREATE VIEW ... WITH (security_invoker = true)`. In older versions of Postgres, protect your views by revoking access from the `anon` and `authenticated` roles, or by putting them in an unexposed schema.\n  - **UPDATE requires a SELECT policy.** In Postgres RLS, an UPDATE needs to first SELECT the row. Without a SELECT policy, updates silently return 0 rows — no error, just no change.\n  - **`auth.role()` is deprecated — use the `TO` clause instead.** Supabase has deprecated `auth.role()` in favour of specifying the target role directly on the policy with `TO authenticated` or `TO anon`. Beyond deprecation, `auth.role() = 'authenticated'` breaks silently when anonymous sign-ins are enabled, because anonymous sign-in users carry the `authenticated` Postgres role, including with `TO authenticated`. If guest accounts must be excluded, check the verified `is_anonymous` claim too; role targeting alone does not distinguish guest from permanent users.\n    ```sql\n    -- Deprecated (do not use)\n    create policy \"example\" on table_name for select\n    using ( auth.role() = 'authenticated' );\n    ```\n  - **`TO authenticated` alone is authentication without authorization (BOLA \u002F IDOR).** Using `TO authenticated` only checks the role — it does not restrict which rows a user can access. The correct pattern combines `TO authenticated` with an ownership predicate in `USING`:\n    ```sql\n    create policy \"example\" on table_name for select\n    to authenticated\n    using ( (select auth.uid()) = user_id );\n    ```\n  - **Write explicit `USING` and `WITH CHECK` predicates for clarity.** PostgreSQL reuses `USING` as `WITH CHECK` when the latter is omitted for UPDATE\u002FALL; omission alone does not allow ownership reassignment. Review all applicable permissive policies and column privileges, not just this example:\n    ```sql\n    create policy \"example\" on table_name for update\n    to authenticated\n    using ( (select auth.uid()) = user_id )\n    with check ( (select auth.uid()) = user_id );\n    ```\n  - **`SECURITY DEFINER` functions can bypass RLS depending on their owner’s privileges.** They run as the function owner; table owners and BYPASSRLS roles have different behavior from an ordinary owner role, and FORCE ROW LEVEL SECURITY changes table-owner treatment. Never add `SECURITY DEFINER` to resolve a permission error; it silently removes access control without fixing the underlying cause. Prefer `SECURITY INVOKER`.\n  - **Review function EXECUTE grants and exposed schemas.** Postgres grants `EXECUTE` to `PUBLIC` by default for every new function, so new functions can be executable by all roles unless privileges are revoked or default privileges changed. API exposure additionally depends on schema exposure and schema USAGE. When `SECURITY DEFINER` is genuinely needed (e.g., bypassing RLS on an internal lookup table), keep the function in a non-exposed schema, use a least-privileged owner, fixed safe search_path and explicit caller\u002Foperation authorization as appropriate, revoke EXECUTE from PUBLIC\u002Fanon\u002Fauthenticated and grant only intended callers, and run `supabase db advisors` after making changes.\n\n- **Storage access control**\n  - **Storage upsert requires INSERT + SELECT + UPDATE.** Granting only INSERT allows new uploads but file replacement (upsert) silently fails. You need all three.\n\n- **Dependency and supply-chain security**\n  - **Always pin package versions and commit lockfiles** when installing Supabase packages (`supabase-js`, `@supabase\u002Fssr`, `supabase-py`, etc.). See the [npm security guide](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fsecurity\u002Fnpm-security.md) for the full checklist.\n\nFor any security concern not covered above, fetch the Supabase product security index: `https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fsecurity\u002Fproduct-security.md`\n\n## Supabase CLI\n\nAlways discover commands via `--help` — never guess. The CLI structure changes between versions.\n\n```bash\nsupabase --help                    # All top-level commands\nsupabase \u003Cgroup> --help            # Subcommands (e.g., supabase db --help)\nsupabase \u003Cgroup> \u003Ccommand> --help  # Flags for a specific command\n```\n\n**Supabase CLI Known gotchas:**\n\n- `supabase db query` requires **CLI v2.79.0+** → use MCP `execute_sql` or `psql` as fallback\n- `supabase db advisors` requires **CLI v2.81.3+** → use MCP `get_advisors` as fallback\n- When you need a new migration SQL file, **always** create it with `supabase migration new \u003Cname>` first. Never invent a migration filename or rely on memory for the expected format.\n\n**Version check and upgrade:** Run `supabase --version` to check. For CLI changelogs and version-specific features, consult the [CLI documentation](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freference\u002Fcli\u002Fintroduction) or [GitHub releases](https:\u002F\u002Fgithub.com\u002Fsupabase\u002Fcli\u002Freleases).\n\n## Supabase MCP Server\n\nFor setup instructions, server URL, and configuration, see the [MCP setup guide](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fgetting-started\u002Fmcp).\n\n**Troubleshooting connection issues** — follow these steps in order:\n\n1. **Check if the server is reachable:**\n   `curl -so \u002Fdev\u002Fnull -w \"%{http_code}\" https:\u002F\u002Fmcp.supabase.com\u002Fmcp`\n   A `401` can show the endpoint is reachable; it does not establish client authentication or tool readiness. Timeout or \"connection refused\" means it may be down.\n\n2. **Check `.mcp.json` configuration:**\n   Verify the project root has a valid `.mcp.json` with the correct server URL. If missing, prepare the configuration for the user’s actual client and authorized project scope; do not automatically add a connector or expose every project. Prefer read-only, project-scoped access where sufficient.\n\n3. **Authenticate the MCP server:**\n   If the server is reachable and `.mcp.json` is correct but tools aren't visible, the user needs to authenticate. The Supabase MCP server uses OAuth 2.1 — tell the user to trigger the auth flow in their agent, complete it in the browser, and reload the session.\n\n## Supabase Documentation\n\nBefore implementing any Supabase feature, find the relevant documentation. Use these methods in priority order:\n\n1. **MCP `search_docs` tool** (preferred — returns relevant snippets directly)\n2. **Fetch docs pages as markdown** — any docs page can be fetched by appending `.md` to the URL path.\n3. **Web search** for Supabase-specific topics when you don't know which page to look at.\n\n## Making and Committing Schema Changes\n\nWork in an explicitly identified disposable local\u002Ftest database. Prefer `supabase migration new \u003Cname>`, edit its SQL, then apply and test through the project’s migration workflow. Inspect installed command help; never infer a remote target from a fallback tool. Ad hoc SQL can be useful for local exploration, but direct remote DDL creates drift and does not become safe merely because it omits migration history.\n\nTo finalize:\n\n1. Inspect the current schema and migration history; choose the repository’s migration-first or documented local-diff workflow.\n2. For local exploration, generate a diff using the installed CLI’s documented local-target options and review every statement; do not blindly pull from a linked remote or accept `--yes` prompts.\n3. Recreate an authorized disposable local database from migration history, seed synthetic fixtures and run intended\u002Fdenied access cases. Reset destroys data: verify the local target before use.\n4. Run available advisors and relevant tests; record remaining findings. Review SQL and rollback\u002Fforward-fix plans before any separately authorized remote deployment.\n\nA concrete RLS check uses two synthetic users: user A can read\u002Fupdate A’s row, user B cannot read or update it, and neither can change its owner to another user. Also test anonymous\u002Fguest behavior required by the application. Do not use service-role bypass credentials as proof that client RLS works.\n\n## Reference Guides\n\n- **Skill Feedback** → [references\u002Fskill-feedback.md](references\u002Fskill-feedback.md)\n  **MUST read when** the user reports that this skill gave incorrect guidance or is missing information.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream product or API scope.\n- Verify commands, API behavior, pricing, quotas, credentials, and deployment effects against current official documentation before making changes.\n- Do not treat generated examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Supabase\n## When to Use\n\nUse when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase\u002Fssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, session handling and access policies.\n\n\n## Core Principles\n\n**1. Supabase changes frequently — verify against changelog and current docs before implementing.**\nDo not rely on training data for Supabase features. Function signatures, config.toml settings, and API conventions change between versions.\n\nFirst, fetch `https:\u002F\u002Fsupabase.com\u002Fchangelog.md` (a lightweight summary index — not a heavy pull), scan for `breaking-change` tags relevant to your task, and follow the linked page for any that apply. Then look up the relevant topic using the documentation access methods below.\n\n**2. Verify your work.**\nVerify with the smallest relevant check in an authorized local\u002Ftest environment; use role-specific positive and negative policy tests for access changes. A SQL query is not appropriate verification for every UI, auth or docs change. State any unavailable check rather than issuing production mutations for verification.\n\n**3. Recover from errors, don't loop.**\nIf an approach fails after 2-3 attempts, stop and reconsider. Try a different method, check documentation, inspect the error more carefully, and review relevant logs when available. Supabase issues are not always solved by retrying the same command, and the answer is not always in the logs, but logs are often worth checking before proceeding.\n\n**4. Exposing tables to the Data API:** Depending on the user's [Data API settings](https:\u002F\u002Fsupabase.com\u002Fdashboard\u002Fproject\u002F\u003Cref>\u002Fintegrations\u002Fdata_api\u002Fsettings), newly created tables may not be automatically exposed via the Data (REST) API. If this is the case, `anon` and `authenticated` roles will need to be explicitly granted access.\n\n> Note that this is separate from RLS, which controls which _rows_ are visible once a table is accessible, not whether the table is accessible at all.\n\nWhen a user reports a SQL-created table is unexpectedly inaccessible, check their Data API settings and whether the roles have been granted access via explicit `GRANT` SQL. When granting public (`anon`\u002F`authenticated`) access, always enable RLS too. See [Exposing a Table to the Data API](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fapi\u002Fsecuring-your-api.md) for the full setup workflow.\n\n**5. RLS in exposed schemas.**\nEnable RLS on every table in any exposed schema, which includes `public` by default. This is critical in Supabase because tables in exposed schemas can be reachable through the Data API when the `anon`\u002F`authenticated` roles have access (see [Exposing a Table to the Data API](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fapi\u002Fsecuring-your-api.md)). For private schemas, prefer RLS as defense in depth. After enabling RLS, create policies that match the actual access model rather than defaulting every table to the same `auth.uid()` pattern.\n\n**6. Security checklist.**\nWhen working on any Supabase task that touches auth, RLS, views, storage, or user data, run through this checklist. These are Supabase-specific security traps that silently create vulnerabilities:\n\n- **Auth and session security**\n  - **Never use `user_metadata` claims in JWT-based authorization decisions.** In Supabase, `raw_user_meta_data` is user-editable and can appear in `auth.jwt()`, so it is unsafe for RLS policies or any other authorization logic. Store authorization data in `raw_app_meta_data` \u002F `app_metadata` instead.\n  - **Deleting a user does not invalidate existing access tokens.** Sign out or revoke sessions first, keep JWT expiry short for sensitive apps, and for strict guarantees validate `session_id` against `auth.sessions` on sensitive operations.\n  - **If you use `app_metadata` or `auth.jwt()` for authorization, remember JWT claims are not always fresh until the user's token is refreshed.**\n\n- **API key and client exposure**\n  - **Never expose the `service_role` or secret key in public clients.** Prefer publishable keys for frontend code. Legacy `anon` keys are only for compatibility. In Next.js, any `NEXT_PUBLIC_` env var is sent to the browser.\n\n- **RLS, views, and privileged database code**\n  - **Views bypass RLS by default.** In Postgres 15 and above, use `CREATE VIEW ... WITH (security_invoker = true)`. In older versions of Postgres, protect your views by revoking access from the `anon` and `authenticated` roles, or by putting them in an unexposed schema.\n  - **UPDATE requires a SELECT policy.** In Postgres RLS, an UPDATE needs to first SELECT the row. Without a SELECT policy, updates silently return 0 rows — no error, just no change.\n  - **`auth.role()` is deprecated — use the `TO` clause instead.** Supabase has deprecated `auth.role()` in favour of specifying the target role directly on the policy with `TO authenticated` or `TO anon`. Beyond deprecation, `auth.role() = 'authenticated'` breaks silently when anonymous sign-ins are enabled, because anonymous sign-in users carry the `authenticated` Postgres role, including with `TO authenticated`. If guest accounts must be excluded, check the verified `is_anonymous` claim too; role targeting alone does not distinguish guest from permanent users.\n    ```sql\n    -- Deprecated (do not use)\n    create policy \"example\" on table_name for select\n    using ( auth.role() = 'authenticated' );\n    ```\n  - **`TO authenticated` alone is authentication without authorization (BOLA \u002F IDOR).** Using `TO authenticated` only checks the role — it does not restrict which rows a user can access. The correct pattern combines `TO authenticated` with an ownership predicate in `USING`:\n    ```sql\n    create policy \"example\" on table_name for select\n    to authenticated\n    using ( (select auth.uid()) = user_id );\n    ```\n  - **Write explicit `USING` and `WITH CHECK` predicates for clarity.** PostgreSQL reuses `USING` as `WITH CHECK` when the latter is omitted for UPDATE\u002FALL; omission alone does not allow ownership reassignment. Review all applicable permissive policies and column privileges, not just this example:\n    ```sql\n    create policy \"example\" on table_name for update\n    to authenticated\n    using ( (select auth.uid()) = user_id )\n    with check ( (select auth.uid()) = user_id );\n    ```\n  - **`SECURITY DEFINER` functions can bypass RLS depending on their owner’s privileges.** They run as the function owner; table owners and BYPASSRLS roles have different behavior from an ordinary owner role, and FORCE ROW LEVEL SECURITY changes table-owner treatment. Never add `SECURITY DEFINER` to resolve a permission error; it silently removes access control without fixing the underlying cause. Prefer `SECURITY INVOKER`.\n  - **Review function EXECUTE grants and exposed schemas.** Postgres grants `EXECUTE` to `PUBLIC` by default for every new function, so new functions can be executable by all roles unless privileges are revoked or default privileges changed. API exposure additionally depends on schema exposure and schema USAGE. When `SECURITY DEFINER` is genuinely needed (e.g., bypassing RLS on an internal lookup table), keep the function in a non-exposed schema, use a least-privileged owner, fixed safe search_path and explicit caller\u002Foperation authorization as appropriate, revoke EXECUTE from PUBLIC\u002Fanon\u002Fauthenticated and grant only intended callers, and run `supabase db advisors` after making changes.\n\n- **Storage access control**\n  - **Storage upsert requires INSERT + SELECT + UPDATE.** Granting only INSERT allows new uploads but file replacement (upsert) silently fails. You need all three.\n\n- **Dependency and supply-chain security**\n  - **Always pin package versions and commit lockfiles** when installing Supabase packages (`supabase-js`, `@supabase\u002Fssr`, `supabase-py`, etc.). See the [npm security guide](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fsecurity\u002Fnpm-security.md) for the full checklist.\n\nFor any security concern not covered above, fetch the Supabase product security index: `https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fsecurity\u002Fproduct-security.md`\n\n## Supabase CLI\n\nAlways discover commands via `--help` — never guess. The CLI structure changes between versions.\n\n```bash\nsupabase --help                    # All top-level commands\nsupabase \u003Cgroup> --help            # Subcommands (e.g., supabase db --help)\nsupabase \u003Cgroup> \u003Ccommand> --help  # Flags for a specific command\n```\n\n**Supabase CLI Known gotchas:**\n\n- `supabase db query` requires **CLI v2.79.0+** → use MCP `execute_sql` or `psql` as fallback\n- `supabase db advisors` requires **CLI v2.81.3+** → use MCP `get_advisors` as fallback\n- When you need a new migration SQL file, **always** create it with `supabase migration new \u003Cname>` first. Never invent a migration filename or rely on memory for the expected format.\n\n**Version check and upgrade:** Run `supabase --version` to check. For CLI changelogs and version-specific features, consult the [CLI documentation](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freference\u002Fcli\u002Fintroduction) or [GitHub releases](https:\u002F\u002Fgithub.com\u002Fsupabase\u002Fcli\u002Freleases).\n\n## Supabase MCP Server\n\nFor setup instructions, server URL, and configuration, see the [MCP setup guide](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fgetting-started\u002Fmcp).\n\n**Troubleshooting connection issues** — follow these steps in order:\n\n1. **Check if the server is reachable:**\n   `curl -so \u002Fdev\u002Fnull -w \"%{http_code}\" https:\u002F\u002Fmcp.supabase.com\u002Fmcp`\n   A `401` can show the endpoint is reachable; it does not establish client authentication or tool readiness. Timeout or \"connection refused\" means it may be down.\n\n2. **Check `.mcp.json` configuration:**\n   Verify the project root has a valid `.mcp.json` with the correct server URL. If missing, prepare the configuration for the user’s actual client and authorized project scope; do not automatically add a connector or expose every project. Prefer read-only, project-scoped access where sufficient.\n\n3. **Authenticate the MCP server:**\n   If the server is reachable and `.mcp.json` is correct but tools aren't visible, the user needs to authenticate. The Supabase MCP server uses OAuth 2.1 — tell the user to trigger the auth flow in their agent, complete it in the browser, and reload the session.\n\n## Supabase Documentation\n\nBefore implementing any Supabase feature, find the relevant documentation. Use these methods in priority order:\n\n1. **MCP `search_docs` tool** (preferred — returns relevant snippets directly)\n2. **Fetch docs pages as markdown** — any docs page can be fetched by appending `.md` to the URL path.\n3. **Web search** for Supabase-specific topics when you don't know which page to look at.\n\n## Making and Committing Schema Changes\n\nWork in an explicitly identified disposable local\u002Ftest database. Prefer `supabase migration new \u003Cname>`, edit its SQL, then apply and test through the project’s migration workflow. Inspect installed command help; never infer a remote target from a fallback tool. Ad hoc SQL can be useful for local exploration, but direct remote DDL creates drift and does not become safe merely because it omits migration history.\n\nTo finalize:\n\n1. Inspect the current schema and migration history; choose the repository’s migration-first or documented local-diff workflow.\n2. For local exploration, generate a diff using the installed CLI’s documented local-target options and review every statement; do not blindly pull from a linked remote or accept `--yes` prompts.\n3. Recreate an authorized disposable local database from migration history, seed synthetic fixtures and run intended\u002Fdenied access cases. Reset destroys data: verify the local target before use.\n4. Run available advisors and relevant tests; record remaining findings. Review SQL and rollback\u002Fforward-fix plans before any separately authorized remote deployment.\n\nA concrete RLS check uses two synthetic users: user A can read\u002Fupdate A’s row, user B cannot read or update it, and neither can change its owner to another user. Also test anonymous\u002Fguest behavior required by the application. Do not use service-role bypass credentials as proof that client RLS works.\n\n## Reference Guides\n\n- **Skill Feedback** → [references\u002Fskill-feedback.md](references\u002Fskill-feedback.md)\n  **MUST read when** the user reports that this skill gave incorrect guidance or is missing information.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream product or API scope.\n- Verify commands, API behavior, pricing, quotas, credentials, and deployment effects against current official documentation before making changes.\n- Do not treat generated examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":32,"source":42,"license":14,"date_added":43,"description":7,"source_repo":44,"source_type":24,"license_source":45},"https:\u002F\u002Fgithub.com\u002Fsupabase\u002Fagent-skills\u002Ftree\u002Fmain\u002Fskills\u002Fsupabase",1782864000000,"supabase\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fsupabase\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE","7bf2279c8a65758319526a721d5c4b75683aec9c","skills\u002Fantigravity-supabase",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-13 14:20:47",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add boisenoise\u002Fskills-collections --skill supabase",{"tool":58,"command":59},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill supabase",{"tool":61,"command":62},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill supabase","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-supabase\u002FSKILL.md",true,[66,72,78],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"assets\u002Ffeedback-issue-template.md","ASSET","资产文件",459,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-supabase\u002Fassets\u002Ffeedback-issue-template.md",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"CHANGELOG.md","REFERENCE","参考文档",3290,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-supabase\u002FCHANGELOG.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fskill-feedback.md",1250,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-supabase\u002Freferences\u002Fskill-feedback.md",[83,109,129,154,173,196],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":37},"01M6WNH92BHVFXHGPDZCPJ0AG0","web-access","Use Treg for public web or platform data only when existing search, browser and connected tools cannot cover the task, with explicit cost and data boundaries.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FSKILL.md",[],[92,93,94,24,95,96,97,98,99,100,101,102,103,104,105,32,106,107,108,35,36],"web","access","web access","development","browser","search","data","Tools","read","fetch","only","youtube","free tools","platform","free","cover","normal",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":117,"publishedAt":37},"01M6WNF9XAYAB2CZDDJBAKNM93","treg","Use the Treg CLI or MCP catalog to discover, price and call authorized external tools with team-scoped credentials and a user-approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FSKILL.md",[116],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[111,118,119,23,24,95,25,99,120,121,122,123,27,124,125,32,126,127,128,34,36],"MCP","cli","Budget","credentials","team","catalog","call","discover","external tools","with","scoped",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":141,"publishedAt":37},"01M6WN93MEAZ4E41DYAHJRPHQT","recruit","Turn a job description into an evidence-linked candidate shortlist through Treg, with job-related ranking and optional authorized business contact enrichment.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FSKILL.md",[136],{"categoryNo":137,"categoryName":138,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[131,23,24,25,26,142,143,144,145,146,32,147,148,149,127,150,151,152,153,34,111,36],"email","enrichment","business","evidence","phone","ranking","post","job description","for","person","candidate","reason",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":158,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":37},"01M6WN8R5RXSMHM9B4D9FAFX42","rea-growth","Analyze a company’s public growth and content through Treg, distinguish observations from hypotheses, and produce an evidence-linked playbook within an approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FSKILL.md",[],[162,163,164,23,24,25,165,166,26,167,120,168,169,170,145,32,171,172,34,111,36],"growth","rea","rea growth","produce","content","playbook","marketing","analyze","public","observations","company",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":177,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":37},"01M6WN2EVE3RQRGWAKBT4S7YT2","make-ugc","Create original AI UGC-style product videos through Treg: research hooks, approve a licensed presenter and voice, generate clips, add captions and report costs.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FSKILL.md",[],[181,182,23,183,24,184,25,185,186,187,188,189,32,190,191,192,193,194,195,34],"make","make ugc","research","create","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":200,"sourceHtmlUrl":201,"categories":202,"keywords":203,"publishedAt":37},"01M6WN10ARAA63Y8K1YNGXJ2RM","lead-signals","Find and qualify public buying signals through Treg, rank fitting business accounts and optionally enrich authorized business contact information.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FSKILL.md",[],[204,205,206,23,24,25,207,208,144,209,210,32,211,212,213,214,215,216,217,34],"signals","lead","lead signals","how","find","ready","as","how to","qualify","people","information","enrich","changes","funding"]