supabase

What This Skill Does

The Supabase skill for OpenClaw acts as a powerful bridge between your AI agent and your backend infrastructure. It is specifically designed to provide deep observability into your project's user base and database health. By leveraging the Supabase Management API, this tool allows you to perform complex administrative queries, such as calculating user growth metrics, auditing recent signups, and verifying table accessibility—all without leaving the OpenClaw interface. It is an essential utility for developers who need to monitor user acquisition or debug database-related issues on the fly.

Installation

Installation is straightforward and can be handled via three distinct methods. For quick setup, use the interactive command python3 {baseDir}/scripts/supabase.py auth. For production or automated environments, you can manually create a configuration file at ~/.supabase_config.json or define your credentials as environment variables (SUPABASE_URL and SUPABASE_SERVICE_KEY). To ensure full functionality, it is mandatory to use the Legacy JWT service_role key found in your Supabase dashboard; keys starting with sb_secret_ lack the necessary permissions for user-level auditing.

Use Cases

This skill is ideal for product owners and technical leads who need immediate insights into application performance. Use it to generate daily user sign-up reports, verify that authentication services are active, or quickly identify the most recent users to troubleshoot onboarding friction. It eliminates the need to manually log in to the Supabase dashboard and navigate multiple tabs just to check simple statistics.

Example Prompts

1. "How many new users have signed up in the last 24 hours?"
2. "Show me the 5 most recent signups and their email addresses."
3. "List all the tables currently exposed via my project's REST API and check the status of my connection."

Tips & Limitations

Always prioritize security when handling your service_role key, as it provides full administrative access to your database. If you only need to query data tables and not list auth users, consider using a scoped API key to follow the principle of least privilege. Remember that this tool relies on the legacy JWT format for full visibility; if you find that user listing commands return errors, double-check that you have replaced your newer sb_secret key with the service_role JWT token.