Skip to content

fcakyon/claude-codex-settings / plugins/supabase-skills/skills/supabase-cli

supabase-cli

Flagged

This skill should be used when user asks to "use supabase CLI", "supabase init", "supabase start", "run migrations", "deploy edge functions", "manage Supabase project", or works with the supabase command-line tool for local development and project management.

FileKindSize
SKILL.mdskill md6.3 KB
references/commands/functions.mdmarkdown543 B
references/commands/gen.mdmarkdown594 B
references/commands/init.mdmarkdown682 B
references/commands/link.mdmarkdown626 B
references/commands/login.mdmarkdown695 B
references/commands/network-bans.mdmarkdown230 B
references/commands/projects.mdmarkdown477 B
references/commands/pull.mdmarkdown7.0 KB
references/commands/secrets.mdmarkdown476 B
references/commands/start.mdmarkdown850 B
references/commands/status.mdmarkdown432 B
references/commands/stop.mdmarkdown475 B
references/commands/vanity-subdomains.mdmarkdown149 B
references/config/diff.mdmarkdown2.3 KB
references/config/pull.mdmarkdown8.0 KB
references/config/push.mdmarkdown1.5 KB
references/db/advisors.mdmarkdown174 B
references/db/diff.mdmarkdown2.8 KB
references/db/dump.mdmarkdown926 B
references/db/lint.mdmarkdown1.0 KB
references/db/pull.mdmarkdown5.4 KB
references/db/push.mdmarkdown843 B
references/db/query.mdmarkdown337 B
references/db/reset.mdmarkdown1.3 KB
references/db/schema-declarative-generate.mdmarkdown1.5 KB
references/db/schema-declarative-sync.mdmarkdown413 B
references/domains/activate.mdmarkdown523 B
references/examples.yamlconfig16.1 KB
references/functions/new.mdmarkdown510 B
references/functions/serve.mdmarkdown1.9 KB
references/inspect/db-bloat.mdmarkdown1.3 KB
references/inspect/db-blocking.mdmarkdown1.2 KB
references/inspect/db-cache-hit.mdmarkdown1.3 KB
references/inspect/db-calls.mdmarkdown1.3 KB
references/inspect/db-index-sizes.mdmarkdown660 B
references/inspect/db-index-usage.mdmarkdown968 B
references/inspect/db-locks.mdmarkdown1.1 KB
references/inspect/db-long-running-queries.mdmarkdown1.0 KB
references/inspect/db-outliers.mdmarkdown1.9 KB
references/inspect/db-replication-slots.mdmarkdown1.3 KB
references/inspect/db-role-connections.mdmarkdown1.6 KB
references/inspect/db-seq-scans.mdmarkdown720 B
references/inspect/db-table-index-sizes.mdmarkdown627 B
references/inspect/db-table-record-counts.mdmarkdown636 B
references/inspect/db-table-sizes.mdmarkdown756 B
references/inspect/db-total-index-size.mdmarkdown272 B
references/inspect/db-total-table-sizes.mdmarkdown608 B
references/inspect/db-traffic-profile.mdmarkdown1.8 KB
references/inspect/db-unused-indexes.mdmarkdown923 B
references/inspect/db-vacuum-stats.mdmarkdown2.4 KB
references/migration/list.mdmarkdown722 B
references/migration/new.mdmarkdown376 B
references/migration/repair.mdmarkdown2.6 KB
references/migration/squash.mdmarkdown892 B
references/overview.mdmarkdown5.4 KB
references/test/db.mdmarkdown440 B

references/examples.yaml

View on GitHub
supabase-init:
  - id: basic-usage
    name: Basic usage
    code: supabase init
    response: Finished supabase init.
  - id: from-workdir
    name: Initialize from an existing directory
    code: supabase init --workdir .
    response: Finished supabase init.
  - id: with-orioledb
    name: Initialize with OrioleDB
    code: supabase init --use-orioledb
    response: Finished supabase init.
supabase-login:
  - id: basic-usage
    name: Basic usage
    code: supabase login
    response: |
      You can generate an access token from https://supabase.com/dashboard/account/tokens
      Enter your access token: sbp_****************************************
      Finished supabase login.
supabase-link:
  - id: basic-usage
    name: Basic usage
    code: supabase link --project-ref ********************
    response: |
      Enter your database password (or leave blank to skip): ********
      Finished supabase link.
  - id: without-password
    name: Link without database password
    code: supabase link --project-ref ******************** <<< ""
    response: |
      Enter your database password (or leave blank to skip):
      Finished supabase link.
  - id: using-alternate-dns
    name: Link using DNS-over-HTTPS resolver
    code: supabase link --project-ref ******************** --dns-resolver https
    response: |
      Enter your database password (or leave blank to skip):
      Finished supabase link.
supabase-start:
  - id: basic-usage
    name: Basic usage
    code: supabase start
    response: |
      Creating custom roles supabase/roles.sql...
      Applying migration 20220810154536_employee.sql...
      Seeding data supabase/seed.sql...
      Started supabase local development setup.
  - id: without-studio
    name: Start containers without studio and imgproxy
    code: supabase start -x studio,imgproxy
    response: |
      Excluding container: supabase/studio:20221214-4eecc99
      Excluding container: darthsim/imgproxy:v3.8.0
      Started supabase local development setup.
  - id: ignore-health-check
    name: Ignore service health checks
    code: supabase start --ignore-health-check
    response: |
      service not healthy: [supabase_storage_cli]
      Started supabase local development setup.
supabase-stop:
  - id: basic-usage
    name: Basic usage
    code: supabase stop
    response: |
      Stopped supabase local development setup.
      Local data are backed up to docker volume.
  - id: clean-up
    name: Clean up local data after stopping
    code: supabase stop --no-backup
    response: |
      Stopped supabase local development setup.
supabase-status:
  - id: basic-usage
    name: Basic usage
    code: supabase status
    response: |2
      supabase local development setup is running.

               API URL: http://127.0.0.1:54321
           GraphQL URL: http://127.0.0.1:54321/graphql/v1
                DB URL: postgresql://postgres:postgres@127.0.0.1:54322/postgres
            Studio URL: http://127.0.0.1:54323
          Inbucket URL: http://127.0.0.1:54324
            JWT secret: super-secret-jwt-token-with-at-least-32-characters-long
              anon key: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6ImFub24iLCJleHAiOjE5ODM4MTI5OTZ9.CRXP1A7WOeoJeXxjNni43kdQwgnWNReilDMblYTn_I0
      service_role key: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6InNlcnZpY2Vfcm9sZSIsImV4cCI6MTk4MzgxMjk5Nn0.EGIM96RAZx35lJzdJsyH-qQwv8Hdp7fsn3W0YpN81IU
  - id: output-env
    name: Format status as environment variables
    code: supabase status -o env
    response: |
      ANON_KEY="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6ImFub24iLCJleHAiOjE5ODM4MTI5OTZ9.CRXP1A7WOeoJeXxjNni43kdQwgnWNReilDMblYTn_I0"
      API_URL="http://127.0.0.1:54321"
      DB_URL="postgresql://postgres:postgres@127.0.0.1:54322/postgres"
      GRAPHQL_URL="http://127.0.0.1:54321/graphql/v1"
      INBUCKET_URL="http://127.0.0.1:54324"
      JWT_SECRET="super-secret-jwt-token-with-at-least-32-characters-long"
      SERVICE_ROLE_KEY="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6InNlcnZpY2Vfcm9sZSIsImV4cCI6MTk4MzgxMjk5Nn0.EGIM96RAZx35lJzdJsyH-qQwv8Hdp7fsn3W0YpN81IU"
      STUDIO_URL="http://127.0.0.1:54323"
  - id: output-custom-name
    name: Customize the names of exported variables
    code: supabase status -o env --override-name auth.anon_key=SUPABASE_ANON_KEY --override-name auth.service_role_key=SUPABASE_SERVICE_KEY
    response: |
      Stopped services: [supabase_inbucket_cli supabase_rest_cli supabase_studio_cli]
      SUPABASE_ANON_KEY="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6ImFub24iLCJleHAiOjE5ODM4MTI5OTZ9.CRXP1A7WOeoJeXxjNni43kdQwgnWNReilDMblYTn_I0"
      DB_URL="postgresql://postgres:postgres@127.0.0.1:54322/postgres"
      GRAPHQL_URL="http://127.0.0.1:54321/graphql/v1"
      JWT_SECRET="super-secret-jwt-token-with-at-least-32-characters-long"
      SUPABASE_SERVICE_KEY="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6InNlcnZpY2Vfcm9sZSIsImV4cCI6MTk4MzgxMjk5Nn0.EGIM96RAZx35lJzdJsyH-qQwv8Hdp7fsn3W0YpN81IU"
supabase-migration-list:
  - id: basic-usage
    name: Basic usage
    code: supabase migration list
    response: |2
            LOCAL      │     REMOTE     │     TIME (UTC)
      ─────────────────┼────────────────┼──────────────────────
                       │ 20230103054303 │ 2023-01-03 05:43:03
                       │ 20230103093141 │ 2023-01-03 09:31:41
        20230222032233 │                │ 2023-02-22 03:22:33
  - id: with-db-url
    name: Connect to self-hosted database
    code: supabase migration list --db-url 'postgres://postgres[:percent_encoded_password]@127.0.0.1[:port]/postgres'
    response: |2
            LOCAL      │     REMOTE     │     TIME (UTC)
      ─────────────────┼────────────────┼──────────────────────
        20230103054303 │ 20230103054303 │ 2023-01-03 05:43:03
        20230103093141 │ 20230103093141 │ 2023-01-03 09:31:41
supabase-migration-new:
  - id: basic-usage
    name: Basic usage
    code: supabase migration new schema_test
    response: |
      Created new migration at supabase/migrations/20230306095710_schema_test.sql.
  - id: pipe-stdin
    name: With statements piped from stdin
    code: echo "create schema if not exists test;" | supabase migration new schema_test
    response: |
      Created new migration at supabase/migrations/20230306095710_schema_test.sql.
supabase-migration-repair:
  - id: basic-usage
    name: Mark a migration as reverted
    code: supabase migration repair 20230103054303 --status reverted
    response: |
      Repaired migration history: 20230103054303 => reverted
  - id: mark-applied
    name: Mark a migration as applied
    code: supabase migration repair 20230222032233 --status applied
    response: |
      Repaired migration history: 20230222032233 => applied
supabase-db-diff:
  - id: basic-usage
    name: Basic usage
    code: supabase db diff -f my_table
    response: |
      Connecting to local database...
      Creating shadow database...
      Applying migration 20230425064254_remote_commit.sql...
      Diffing schemas: auth,extensions,public,storage
      Finished supabase db diff on branch main.

      No schema changes found
  - id: linked-project
    name: Against linked project
    code: supabase db diff -f my_table --linked
    response: |
      Connecting to local database...
      Creating shadow database...
      Diffing schemas: auth,extensions,public,storage
      Finished supabase db diff on branch main.

      WARNING: The diff tool is not foolproof, so you may need to manually rearrange and modify the generated migration.
      Run supabase db reset to verify that the new migration does not generate errors.
  - id: specific-schema
    name: For a specific schema
    code: supabase db diff -f my_table --schema auth
    response: |
      Connecting to local database...
      Creating shadow database...
      Diffing schemas: auth
      Finished supabase db diff on branch main.

      No schema changes found
supabase-db-dump:
  - id: basic-usage
    name: Basic usage
    code: supabase db dump -f supabase/schema.sql
    response: |
      Dumping schemas from remote database...
      Dumped schema to supabase/schema.sql.
  - id: role-only
    name: Role only
    code: supabase db dump -f supabase/roles.sql --role-only
    response: |
      Dumping roles from remote database...
      Dumped schema to supabase/roles.sql.
  - id: data-only
    name: Data only
    code: supabase db dump -f supabase/seed.sql --data-only
    response: |
      Dumping data from remote database...
      Dumped schema to supabase/seed.sql.
supabase-db-lint:
  - id: basic-usage
    name: Basic usage
    code: supabase db lint
    response: |
      Linting schema: public

      No schema errors found
  - id: schema-warnings
    name: Warnings for a specific schema
    code: supabase db lint --level warning --schema storage
    response: |
      Linting schema: storage
      [
        {
          "function": "storage.search",
          "issues": [
            {
              "level": "warning",
              "message": "unused variable \"_bucketid\"",
              "sqlState": "00000"
            }
          ]
        }
      ]
supabase-db-pull:
  - id: basic-usage
    name: Basic usage
    code: supabase db pull
    response: |
      Connecting to remote database...
      Schema written to supabase/migrations/20240414044403_remote_schema.sql
      Update remote migration history table? [Y/n]
      Repaired migration history: [20240414044403] => applied
      Finished supabase db pull.
  - id: local-studio
    name: Local studio
    code: supabase db pull --local
    response: |
      Connecting to local database...
      Creating shadow database...
      Seeding globals from roles.sql...
      Applying migration 20240414044403_remote_schema.sql...
      Diffing schemas...
      No schema changes found
      The remote database is already in sync with your local migrations — nothing to pull.
  - id: custom-schemas
    name: Custom schemas
    code: supabase db pull --schema public,extensions
    response: |
      Connecting to remote database...
      Creating shadow database...
      Seeding globals from roles.sql...
      Applying migration 20240414044403_remote_schema.sql...
      Diffing schemas: public,extensions
      No schema changes found
      The remote database is already in sync with your local migrations — nothing to pull.
supabase-db-push:
  - id: basic-usage
    name: Basic usage
    code: supabase db push
    response: |
      Linked project is up to date.
  - id: self-hosted
    name: Self hosted
    code: supabase db push --db-url "postgres://user:pass@127.0.0.1:5432/postgres"
    response: |
      Pushing migration 20230410135622_create_employees_table.sql...
      Finished supabase db push.
  - id: dry-run
    name: Dry run
    code: supabase db push --dry-run
    response: |
      DRY RUN: migrations will *not* be pushed to the database.
      Would push migration 20230410135622_create_employees_table.sql...
      Would push migration 20230425064254_my_table.sql...
      Finished supabase db push.
supabase-db-reset:
  - id: basic-usage
    name: Basic usage
    code: supabase db reset
    response: |
      Resetting database...
      Initializing schema...
      Applying migration 20220810154537_create_employees_table.sql...
      Seeding data supabase/seed.sql...
      Finished supabase db reset on branch main.
supabase-db-schema-declarative-sync:
  - id: with-pg-delta
    name: Sync declarative schema with pg-delta
    code: |
      # After editing declarative schema files, generate a migration:
      supabase db schema declarative sync --experimental
    response: |
      Creating shadow database...
      Applying declarative schemas via pg-delta...
      Applied 239 statements in 1 round(s).
      Enter a name for this migration (press Enter to keep 'declarative_sync'): add_updated_at
      Created new migration at supabase/migrations/20260317194051_add_updated_at.sql
      Apply this migration to local database? [Y/n]
      Connecting to local database...
      Applying migration 20260317194051_add_updated_at.sql...
      Migration applied successfully.
  - id: generate-first
    name: Generate declarative schema from migrations
    code: |
      supabase db schema declarative sync --experimental
    response: |
      No declarative schema found. Generate a new one ? [Y/n]
      Reset local database to match migrations first? (local data will be lost) [y/N] y
      Resetting database...
      ...
      Declarative schema written to supabase/schemas
      Finished supabase db schema declarative generate.
supabase-test-db:
  - id: basic-usage
    name: Basic usage
    code: supabase test db
    response: |
      /tmp/supabase/tests/nested/order_test.pg .. ok
      /tmp/supabase/tests/pet_test.sql .......... ok
      All tests successful.
      Files=2, Tests=2,  6 wallclock secs ( 0.03 usr  0.01 sys +  0.05 cusr  0.02 csys =  0.11 CPU)
      Result: PASS
# TODO: use actual cli response for sso commands
supabase-sso-show:
  - id: basic-usage
    name: Show information
    code: |-
      supabase sso show 6df4d73f-bf21-405f-a084-b11adf19fea5 \
        --project-ref abcdefghijklmnopqrst
    response: |-
      Information about the identity provider in pretty output.
  - id: metadata-output
    name: Get raw SAML 2.0 Metadata XML
    code: |-
      supabase sso show 6df4d73f-bf21-405f-a084-b11adf19fea5 \
        --project-ref abcdefghijklmnopqrst \
        --metadata
    response: |-
      Raw SAML 2.0 XML assigned to this identity provider. This is the
      version used in the authentication project, and if using a SAML 2.0
      Metadata URL it may change depending on the caching information
      contained within the metadata.
supabase-sso-update:
  - id: basic-usage
    name: Replace domains
    code: |-
      supabase sso update 6df4d73f-bf21-405f-a084-b11adf19fea5 \
        --project-ref abcdefghijklmnopqrst \
        --domains new-company.com,new-company.net
    response: |-
      Information about the updated provider.
  - id: add-domains
    name: Add an additional domain
    code: |-
      supabase sso update 6df4d73f-bf21-405f-a084-b11adf19fea5 \
        --project-ref abcdefghijklmnopqrst \
        --add-domains company.net
    response: |-
      Information about the updated provider.
  - id: remove-domains
    name: Remove a domain
    code: |-
      supabase sso update 6df4d73f-bf21-405f-a084-b11adf19fea5 \
        --project-ref abcdefghijklmnopqrst \
        --remove-domains company.org
    response: |-
      Information about the updated provider.
supabase-sso-remove:
  - id: basic-usage
    name: Remove a provider
    code: |-
      supabase sso remove 6df4d73f-bf21-405f-a084-b11adf19fea5 \
        --project-ref abcdefghijklmnopqrst
    response: |-
      Information about the removed identity provider. It's a good idea to
      save this in case you need it later on.
supabase-sso-add:
  - id: basic-usage
    name: Add with Metadata URL
    code: |-
      supabase sso add \
        --project-ref abcdefgijklmnopqrst \
        --type saml \
        --metadata-url 'https://...' \
        --domains company.com
    response: |-
      Information about the added identity provider. You can use
      company.com as the domain name on the frontend side to initiate a SSO
      request to the identity provider.
  - id: with-xml
    name: Add with Metadata File
    code: |-
      supabase sso add \
        --project-ref abcdefgijklmnopqrst \
        --type saml \
        --metadata-file /path/to/metadata/file.xml \
        --domains company.com
    response: |-
      Information about the added identity provider. You can use
      company.com as the domain name on the frontend side to initiate a SSO
      request to the identity provider.
supabase-sso-info:
  - id: basic-usage
    name: Show project information
    code: supabase sso info --project-ref abcdefghijklmnopqrst
    response: Information about your project's SAML 2.0 configuration.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall