Supabase Agent Skills
supabase/agent-skillsSupabase's official skills: a general Supabase skill for Auth, RLS, CLI and MCP, and a Postgres best-practices skill with 34 rule files.
Four skills for building on the InsForge backend-as-a-service: SDK integration, CLI project management, debugging and auth-provider integrations.
Detailed vendor documentation for the agent, but it is only useful with an InsForge account and the CLI acts on a live cloud project.
These skills teach an agent to work with InsForge, a hosted backend-as-a-service. The insforge skill covers app code with @insforge/sdk: database CRUD and row-level security, auth and OAuth, storage uploads, serverless functions, realtime, email, OpenRouter-based AI calls and Stripe or Razorpay payments. The insforge-cli skill is the largest at about 41 KB and handles infrastructure through npx -y @insforge/cli: logging in, creating or linking projects, SQL and migrations, secrets, backups, deployments, schedules and logs. The insforge-debug skill gives a set of diagnostic primitives (logs, metrics, database health, advisor scans, policies) and symptom recipes, with an optional AI-assisted triage command. The insforge-integrations skill documents connecting external auth providers such as Auth0, Clerk, Kinde and WorkOS, plus an onchain payment guide. Across the four skills there are 44 reference files and no scripts. The instructions warn that InsForge API keys are full-access admin keys and should stay server-side. It only makes sense if you use, or are evaluating, InsForge.
Four skills averaging 21 KB with 44 reference files, but no scripts, tests or evals.
Counted from the repository file tree. How we score depth.
This skill asks for more access than most, or sends data to another service. That is usually a design choice rather than bad intent, but you should know before you install it.
insforge feedback reports to the InsForge team, including the failing command and verbatim error output (locally pattern-redacted by the CLI), whenever it judges a problem to be InsForge's fault, without asking each time.skills/insforge-cli/SKILL.md:332Markdown skills for building on the InsForge backend platform through the @insforge/cli package, covering SQL, auth, storage, functions, deployments, payments and diagnostics. The skills have the agent run the latest CLI with admin-level project keys, so approve destructive operations yourself; they also tell the agent to send InsForge feedback reports containing failing commands and errors. The CLI and the local-stack setup script it fetches were not available to review.
npx -y @insforge/cli <command> (latest version, no install prompt); other skills also run npx -y skills and npx -y @posthog/wizard@latest.skills/insforge-cli/SKILL.md:14curl -L https://fly.io/install.sh | sh; local start also fetches deploy/setup.sh from the InsForge repo and runs it (references/local.md).skills/insforge-cli/references/compute-deploy.md:32ai setup writes an OpenRouter key to a local server-side env file.skills/insforge-cli/SKILL.md:45local start pulls Docker images for a local Postgres/PostgREST/edge-functions stack; skills also install the @insforge/sdk package and run npx skills installs.skills/insforge-cli/references/local.md:4.env.local, and local start writes .insforge/checkout/.env with generated secrets.skills/insforge-cli/references/login.md:86The repository (83 files) on Oct 29, 2026. Not a full review: it relies on code outside the repository: npm package @insforge/cli (run through npx -y); deploy/setup.sh fetched from the InsForge repository by `local start`; flyctl installer from fly.io and @posthog/wizard.
NVIDIA SkillSpector static scan: 546 pattern hits (MCP Rug Pull 467, Privilege Escalation 29, Prompt Injection 12, Excessive Agency 10, Data Exfiltration 10, Memory Poisoning 8). Hits are overwhelmingly documentation: .env, access-token and credentials.json mentions are CLI auth and env-file instructions, DELETE lines are REST API docs, 'bypass policies' is an RLS note, and 'no disclaimers' is in an x402 payments recipe. The only code files are plugin manifests and a settings file that enables the skill-creator plugin for work inside this repo.
A review, not a certification. Skills change after we check them — read the files before installing.
Apache-2.0 — commercial use allowed.
Not really. These are reference skills for interactive backend work and need login and project setup first.
Supabase's official skills: a general Supabase skill for Auth, RLS, CLI and MCP, and a Postgres best-practices skill with 34 rule files.
Neon's official skills for Lakebase Postgres and its Auth, Functions, Object Storage, AI Gateway and Realtime services, with branch-first workflows and evals.
Google's 13 official Firebase skills: CLI and project setup, Auth, Firestore, Hosting, App Hosting, Data Connect, AI Logic and security rules.
Six official skills for the Better Auth TypeScript library: scaffolding auth, best practices, email and password, organizations, two-factor and security hardening.
InsForge is a backend-as-a-service with database, auth, storage, functions, realtime and hosting. This repo contains the agent skills for working with it.
Run npx -y skills add insforge/insforge-skills. In Claude Code you can use /install-skills insforge/insforge-skills, and Codex users can add the repo as a plugin marketplace.
The guidance is readable, but the CLI and SDK steps need an InsForge project, which the skill tells the agent to create or link before writing app code.
Both are vendor skill sets for a hosted backend. Pick the one that matches the platform you actually deploy to; supabase/agent-skills covers Supabase.