Skip to content
TrustedSkillsbeta
Back to all skills

Supabase Environments

Checked
mildtomato·vlatest·database

Manage Supabase environments (dev, staging, prod) – switch connections, deploy migrations, and monitor status directly within your workflow.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add mildtomato/agent-skills --skill supabase-environments -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

mildtomato

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned mildtomato/agent-skills at 00b38ad749.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
00b38ad749
Manifest
supabase-environments/SKILL.md
Scanned
25 files, 3,826 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows AI agents to interact with Supabase environments. It enables managing environment variables, switching between environments (dev, staging, production), and potentially executing database migrations specific to each environment. This simplifies deployment workflows and ensures consistent configurations across different stages of development.

When to use it

  • Deploying a new feature: Switch the agent's context to the 'staging' environment to test changes before pushing them live.
  • Troubleshooting production issues: Quickly access and inspect environment variables in the 'production' environment for debugging purposes.
  • Running database migrations: Execute specific migration scripts tailored to a particular Supabase environment (e.g., dev, staging).
  • Managing API keys: Retrieve or update API keys associated with different environments.

Key capabilities

  • Environment variable management
  • Environment switching (dev, staging, production)
  • Database migration execution (potentially)
  • API key access/modification (potentially)

Example prompts

  • "Switch the environment to staging."
  • "What is the value of the DATABASE_URL environment variable in the production environment?"
  • “Run the latest database migrations on the development environment.”

Tips & gotchas

The agent needs appropriate Supabase API keys or access tokens configured for authentication. Specific actions (like running migrations) may require additional permissions within your Supabase project.