Supabase Ops

Manages Supabase migrations, types generation, RLS policies, and edge functions

This skill appears to do what it says (manage Supabase migrations and edge functions) but ask yourself the following before installing or giving it credentials: - Do NOT provide your SUPABASE_SERVICE_ROLE_KEY to any automated skill unless you trust it and you understand the consequences. That key bypasses RLS and can read/modify all data. - Prefer running the skill with only development-scoped credentials or on a throwaway environment first. For production, require manual approval and review the 'planning' output before letting the skill run any `db push` with a production DB URL. - Verify the source repository and owner (claw.json references a GitHub URL but the published metadata's 'Homepage' is missing). Inspect the upstream code and commit history yourself if possible. - Be aware the skill will modify your repository (create migration files, regenerate types, run git commit). Ensure you have backups or CI checks and review commits before pushing. - The package metadata is inconsistent (registry metadata shows no required env vars while the included files require them). Treat that as a sign to be cautious and ask the publisher for clarification. If you decide to proceed: provide least-privilege credentials, run the skill in a dev branch or staging project, require dry-runs and explicit confirmations for production, and review all generated migrations and commits before applying them to production.

Type: OpenClaw Skill Name: supabase-ops Version: 0.1.2 The supabase-ops skill is a legitimate tool for managing Supabase infrastructure, including migrations, RLS policies, and edge functions. It includes a robust 'Planning Protocol' and safety rules designed to prevent accidental data loss, and its use of sensitive environment variables (e.g., SUPABASE_SERVICE_ROLE_KEY) is strictly aligned with its stated purpose of database administration via the standard Supabase CLI (SKILL.md, claw.json).