← Back to Skills Marketplace
Next-Supabase-Vercel Bundle
by
Bastian Berrios Alarcon
· GitHub ↗
· v1.0.0
654
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install next-supabase-vercel-bundle
Description
ORQUESTADOR REAL para el ciclo completo de desarrollo Full-Stack. Conecta a Supabase, genera migrations SQL ejecutables, y guía paso a paso. Integración con...
Usage Guidance
This skill appears to do what it claims (scaffold Next.js projects, generate migrations, and drive Vercel deployments), but review before use: 1) Verify source/origin — package.json points to a GitHub repo but the skill listing has no homepage; prefer installing from a known repo. 2) Inspect the generated .env.local and never put SUPABASE service-role keys where they will be exposed to the client (NEXT_PUBLIC_ prefix). 3) Expect the CLI to run npx/create-next-app, npm install, git init, and vercel link/deploy — run it in a disposable project or VM if you’re cautious. 4) Note the minor docs/code mismatch on which Supabase key is required (anon vs service key) — ensure you provide the correct key for the intended operation. 5) Check what you paste into the Vercel link prompts and review pasted environment variables before pushing them to any dashboard. If you want higher assurance, locate and review the upstream repo (studiohakke) and run the CLI in an isolated environment first.
Capability Analysis
Type: OpenClaw Skill
Name: next-supabase-vercel-bundle
Version: 1.0.0
The skill bundle is a legitimate development orchestrator for Next.js, Supabase, and Vercel. It automates project setup, generates boilerplate code and SQL migration files, and guides the user through manual configuration steps in Supabase and Vercel dashboards. All `execSync` calls in `src/commands/*.js` are for standard development tools (`npx`, `npm`, `vercel`) and use `stdio: 'inherit'` for transparency. Crucially, despite a potentially misleading statement in `SKILL.md` about 'automatic migration execution', the `src/commands/db.js` and `src/commands/storage.js` files explicitly instruct the user to run SQL migrations and configure RLS policies manually in the Supabase dashboard. There is no evidence of data exfiltration, malicious execution, persistence mechanisms, or prompt injection attempts against the AI agent. The handling of `SUPABASE_SERVICE_KEY` is confined to generated server-side client code, which is appropriate for its intended use.
Capability Assessment
Purpose & Capability
Name/description (Next + Supabase + Vercel orchestration) aligns with the included CLI commands and code. Required binaries (node, npm, npx, vercel) are reasonable. Minor inconsistency: SKILL.md sometimes mentions SUPABASE_SERVICE_KEY as required for db:setup, while the db setup implementation actually looks for NEXT_PUBLIC_SUPABASE_ANON_KEY; init writes both placeholders. This looks like sloppy docs rather than misdirection.
Instruction Scope
Runtime instructions and code operate on project files (create Next app, write .env.local, create pages, produce SQL migrations), run local commands (npx create-next-app, npm install, npm run build/dev), test Supabase via @supabase/supabase-js, and call/vercel via CLI. All of this is within the expected scope. Note: db:setup and other commands read .env.local from the project directory (which may contain sensitive keys) and the deploy flow runs vercel link/deploy, which interacts with your Vercel account.
Install Mechanism
No install spec provided (instruction-only skill plus code files). The CLI itself does not auto-download remote archives from untrusted URLs; it uses standard npx/npm operations when creating projects and installing dependencies. This is the expected, lower-risk pattern for a scaffolding CLI.
Credentials
The skill declares no required environment variables, yet the code reads and writes .env.local and expects NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY (and optionally SUPABASE_SERVICE_KEY for server operations). Requesting Supabase keys is proportional to the purpose, but: (1) the SKILL.md / sample outputs and code show inconsistent variable names, and (2) the repository/template creates a .env.local containing a placeholder SUPABASE_SERVICE_KEY (a sensitive service-role key) — users must not expose service role keys to client-side NEXT_PUBLIC variables or commit them to VCS.
Persistence & Privilege
The skill does not request persistent or global privileges. always is false and it does not attempt to modify other skills or system-wide agent settings. It runs commands only when invoked by user (or agent invocation, which is standard).
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install next-supabase-vercel-bundle - After installation, invoke the skill by name or use
/next-supabase-vercel-bundle - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release - Complete automation for Next.js + Supabase + Vercel development cycle
Metadata
Frequently Asked Questions
What is Next-Supabase-Vercel Bundle?
ORQUESTADOR REAL para el ciclo completo de desarrollo Full-Stack. Conecta a Supabase, genera migrations SQL ejecutables, y guía paso a paso. Integración con... It is an AI Agent Skill for Claude Code / OpenClaw, with 654 downloads so far.
How do I install Next-Supabase-Vercel Bundle?
Run "/install next-supabase-vercel-bundle" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Next-Supabase-Vercel Bundle free?
Yes, Next-Supabase-Vercel Bundle is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Next-Supabase-Vercel Bundle support?
Next-Supabase-Vercel Bundle is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Next-Supabase-Vercel Bundle?
It is built and maintained by Bastian Berrios Alarcon (@studio-hakke); the current version is v1.0.0.
More Skills