supabase-cli_skill

This skill automates Supabase development workflows with CLI tooling for migrations, edge functions, secrets, and type generation, boosting safety and speed.
  • Python

9

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill georgekhananaev/claude-skills-vault --skill supabase-cli

  • SKILL.md6.9 KB

Overview

This skill automates Supabase development workflows from migrations and Edge Function deployment to secrets and type generation. It bundles safe, repeatable CLI scripts with environment validation and explicit safeguards for dangerous operations. Use it to reduce manual steps, enforce safety checks, and speed routine Supabase tasks in a senior full-stack workflow.

How this skill works

Scripts validate required environment variables and Supabase CLI access before performing operations. Tasks include scaffolding and applying migrations, generating TypeScript types from the schema, deploying Edge Functions, syncing and managing secrets, and executing SQL with risk classification and confirmation flags. Remote actions and destructive SQL require explicit --confirm to prevent accidental changes.

When to use it

  • When creating, testing, or applying database migrations locally or remotely
  • When scaffolding, serving, or deploying Supabase Edge Functions
  • When syncing local .env values to Supabase secrets or auditing remote secrets
  • When generating or updating TypeScript types from the database schema
  • When executing arbitrary SQL but you need automatic safety classification and confirmations
  • When checking schema drift or validating environment configuration before deploys

Best practices

  • Run environment validation (validate_env.py) before any operation to catch missing keys
  • Apply migrations locally and run drift checks before pushing to remote
  • Keep SUPABASE_ACCESS_TOKEN in a secure .env file (gitignored) or use supabase login for ephemeral sessions
  • Use --dry-run or --local flags to verify changes before remote apply
  • Require --confirm for remote destructive actions and review generated migration files before committing

Example use cases

  • Create a new migration, apply locally, run drift check, then push to remote with confirmation
  • Scaffold a new webhook Edge Function, serve locally for testing, then deploy via the deploy script
  • Sync APP_ prefixed environment variables from .env to Supabase secrets with a dry-run validation
  • Generate TypeScript types after a schema change to keep client code strongly typed
  • Run a one-off safe SQL query or classify and require confirmation for dangerous statements

FAQ

Generate a token at https://supabase.com/dashboard/account/tokens, then store it in .env.local, export it in your shell, or run supabase login to authenticate interactively.

What protection exists against accidental destructive SQL?

SQL is classified by risk; dangerous statements require an explicit --confirm flag and remote operations enforce confirmation for destructive actions.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational