Safe SQL Execution
supabase/supabase
A skill your agent uses whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix…
ORQUESTADOR REAL para el ciclo completo de desarrollo Full-Stack.
$ npx skills add LeoYeAI/openclaw-master-skills --skill next-supabase-vercel-bundle -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills next-supabase-vercel-bundle --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/next-supabase-vercel-bundle .claude/skills/next-supabase-vercel-bundle && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "next-supabase-vercel-bundle" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/next-supabase-vercel-bundle into .claude/skills/next-supabase-vercel-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-supabase-vercel-bundle", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/next-supabase-vercel-bundleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill next-supabase-vercel-bundle -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills next-supabase-vercel-bundle --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/next-supabase-vercel-bundle .agents/skills/next-supabase-vercel-bundle && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "next-supabase-vercel-bundle" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/next-supabase-vercel-bundle into .agents/skills/next-supabase-vercel-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-supabase-vercel-bundle", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill next-supabase-vercel-bundle -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills next-supabase-vercel-bundle --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/next-supabase-vercel-bundle .cursor/skills/next-supabase-vercel-bundle && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "next-supabase-vercel-bundle" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/next-supabase-vercel-bundle into .cursor/skills/next-supabase-vercel-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-supabase-vercel-bundle", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/next-supabase-vercel-bundle--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill next-supabase-vercel-bundle -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills next-supabase-vercel-bundle --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/next-supabase-vercel-bundle .gemini/skills/next-supabase-vercel-bundle && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "next-supabase-vercel-bundle" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/next-supabase-vercel-bundle into .gemini/skills/next-supabase-vercel-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-supabase-vercel-bundle", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills next-supabase-vercel-bundleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill next-supabase-vercel-bundle -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/next-supabase-vercel-bundle .github/skills/next-supabase-vercel-bundle && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "next-supabase-vercel-bundle" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/next-supabase-vercel-bundle into .github/skills/next-supabase-vercel-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-supabase-vercel-bundle", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill next-supabase-vercel-bundle -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills next-supabase-vercel-bundle --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/next-supabase-vercel-bundle .opencode/skills/next-supabase-vercel-bundle && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "next-supabase-vercel-bundle" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/next-supabase-vercel-bundle into .opencode/skills/next-supabase-vercel-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-supabase-vercel-bundle", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
next-supabase-vercel-bundleORQUESTADOR REAL para el ciclo completo de desarrollo Full-Stack.
Next Supabase Vercel Bundle is an agent skill from LeoYeAI/openclaw-master-skills. 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 Vercel para deployment automático.
Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 17 other files (for example `_meta.json`, `package.json` and `snv.js`).
It sits in Databases, covering SQL. It works with Supabase, Vercel, SQL and TypeScript. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
8 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships script files (JavaScript and TypeScript), which the agent can run.
Shell commands in SKILL.md call:
npmvercelnvmnodeFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
supabase.comxxx.supabase.covercel.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
SUPABASE_SERVICE_KEYNEXT_PUBLIC_SUPABASE_ANON_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Next Supabase Vercel Bundle loads about 4.3k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 940 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
3. Genera `.env.local` y `.env.example` con placeholders1. Editar .env.local con tus credenciales de Supabase1. **Verifica .env.local**: Requiere `NEXT_PUBLIC_SUPABASE_URL` y `SUPABASE_SERVICE_KEY`1. **Verifica .env.local**: Requiere credenciales1. **Verifica .env.local**: Requiere credenciales1. Verifica `.env.local` existe# .env.local- Lee credenciales de `.env.local`sudo ln -sf ~/.nvm/versions/node/v22.22.0/bin/node /usr/local/bin/node### Problema: ".env.local no encontrado"Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 940 words, ~4,294 tokens.
.claude/skills/next-supabase-vercel-bundle/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.ORQUESTADOR REAL para Next.js + Supabase + Vercel Development
Este skill no es solo scaffolding básico. Es un AUTOMATIZADOR COMPLETO del ciclo de desarrollo full-stack:
Value Prop: 3+ horas → 30 segundos
# Crear proyecto con auth + database (RECOMENDADO)
snv init my-app --template auth-db
# Configurar database (auto-conecta + genera migrations)
cd my-app
snv db:setup
# Configurar authentication (genera SQL + guía)
snv auth:setup
# Configurar storage (genera SQL + guía) - opcional
snv storage:setup --buckets avatars,documents
# Iniciar desarrollo local
snv dev
# Deployar automáticamente a Vercel
snv deploysnv init <project-name> - Crear y Configurar Proyectosnv init my-app
snv init my-app --template auth-dbQué hace:
.env.local y .env.example con placeholderssupabase/migrations/package.json con dependencias pre-configuradastsconfig.json para TypeScriptFlags:
--template <name>: Template a usarminimal - Básico (Next.js + Supabase client)auth-db - RECOMENDADO - Auth + Databaseauth - Con authenticationfull - Completo (Auth + DB + Storage)--no-typescript: Deshabilitar TypeScript--no-tailwind: Deshabilitar Tailwind CSS--no-eslint: Deshabilitar ESLintOutput:
✅ Proyecto my-app creado exitosamente!
Siguientes pasos:
1. Editar .env.local con tus credenciales de Supabase
2. Ejecutar: snv db:setup (configura DB + migrations)
3. (Opcional) Ejecutar: snv auth:setup (configura Auth)
4. (Opcional) Ejecutar: snv storage:setup (configura Storage)
5. Ejecutar: snv dev (iniciar desarrollo)
Para comenzar:
cd my-app
snv devsnv db:setup - Configurar Database (ORQUESTADOR)snv db:setupQué hace:
NEXT_PUBLIC_SUPABASE_URL y SUPABASE_SERVICE_KEYsupabase/migrations/ por archivos .sqlsupabase/migrations-summary.md con lista de migrationsMigrations SQL generadas: El skill crea migraciones con SQL real y ejecutable:
Migration de Auth:
-- Habilitar Authentication en Supabase
-- 1. Habilitar Email Auth
alter schema auth.users enable row level security;
-- 2. Crear tabla de usuarios (ejemplo)
create table if not exists public.users (
id uuid default gen_random_uuid() primary key,
email text unique not null,
created_at timestamp with time zone default timezone('utc', now()) not null,
updated_at timestamp with time zone default timezone('utc', now()) not null
);
-- 3. Configurar RLS para usuarios
alter table public.users enable row level security;
create policy "Usuarios pueden ver su propio perfil"
on public.users for select
using (auth.uid())
with check (auth.uid() = id);
grant select;Ejemplos de migrations:
Output:
🔌 Checking environment variables...
📝 Loading credentials...
🌐 Connecting to Supabase...
✅ Connection to Supabase successful!
📋 Checking for migrations...
📦 Found 2 migration(s):
1. 001_initial_schema.sql
2. 002_enable_auth.sql
⚠️ NOTE: Las migrations deben ejecutarse en Supabase Dashboard
ABRIR: https://supabase.com/dashboard/project/_/sql/new
✅ Database setup completado!
Estado de la base de datos:
URL: https://xxx.supabase.co
Service Key: eyJhbGcOiJIUz...
Archivo creado: supabase/migrations-summary.md
Usa este archivo como guía para ejecutar las migrations en el dashboard.snv auth:setup - Configurar Authentication (ORQUESTADOR)snv auth:setupQué hace:
002_enable_auth.sql con:userssrc/app/auth/login/page.tsxsrc/app/auth/signup/page.tsxsrc/lib/auth.ts con utilitiesEjemplo de migration SQL generado:
-- Habilitar Authentication en Supabase
-- 1. Habilitar Email Auth
alter schema auth.users enable row level security;
-- 2. Crear tabla de usuarios
create table if not exists public.users (
id uuid default gen_random_uuid() primary key,
email text unique not null,
created_at timestamp with time zone default timezone('utc', now()) not null,
updated_at timestamp with time zone default timezone('utc', now()) not null
);
-- 3. Configurar RLS para usuarios
alter table public.users enable row level security;
create policy "Usuarios pueden ver su propio perfil"
on public.users for select
using (auth.uid())
with check (auth.uid() = id);
grant select;Output:
🔐 Checking authentication setup...
✅ Authentication enabled in Supabase
📋 Creating auth migration...
✅ Migration creada: 002_enable_auth.sql
📄 Creating auth pages...
src/app/auth/login/page.tsx
src/app/auth/signup/page.tsx
src/lib/auth.ts
📋 Pasos para completar configuración:
ABRIR el Supabase Dashboard: https://supabase.com/dashboard/project/_/auth/providers
1. Habilita Email Auth (Authentication > Providers > Email)
2. (Opcional) Agrega Google OAuth (Authentication > Providers > Google)
Luego ejecuta la migration 002_enable_auth.sql en SQL Editor:
https://supabase.com/dashboard/project/_/sql/new
✅ Auth setup completado!
Notas importantes:
- Las páginas de login/signup ya existen en tu proyecto
- Revisa src/lib/supabase.ts para la configuración de Auth
- Los RLS policies (Row Level Security) se aplican automáticamentesnv storage:setup - Configurar Storage (ORQUESTADOR)snv storage:setup
snv storage:setup --buckets avatars,documentsQué hace:
003_enable_storage.sql con:Ejemplo de migration SQL generado:
-- Habilitar Storage en Supabase
-- 1. Crear buckets de ejemplo
insert into storage.buckets (id, name, public, file_size_limit, allowed_mime_types)
values
('avatars', 'avatars', true, 5242880, 'image/jpeg,image/png,image/gif'),
('documents', 'documents', true, 52428800, 'application/pdf,application/msword,text/plain')
on conflict (id) do nothing;
-- 2. Configurar políticas RLS
-- NOTA: Las políticas deben configurarse manualmente en el Dashboard
-- URL: https://supabase.com/dashboard/project/_/storage/policies
-- Ejemplo de política para acceso público a avatars
create policy "Acceso público a avatars"
on storage.objects for select
using (bucket_id)
with check (bucket_id in ('avatars'))
grant select;Output:
📦 Checking storage configuration...
✅ Storage enabled in Supabase
📋 Creating storage migration...
✅ Migration creada: 003_enable_storage.sql
📋 Pasos para completar configuración:
ABRIR el Supabase Dashboard: https://supabase.com/dashboard/project/_/storage/buckets
1. Ejecuta la migration 003_enable_storage.sql en SQL Editor
2. Configura las políticas RLS (Row Level Security) para cada bucket
3. Ajusta límites de tamaño de archivos según tus necesidades
✅ Storage setup completado!
Notas importantes:
- Los buckets se crean automáticamente
- Los RLS policies deben configurarse manualmente en el Dashboard
- Revisa los límites de file_size_limit en el Dashboardsnv dev - Iniciar Desarrollo Localsnv dev
snv dev --port 3000Qué hace:
.env.local existenpm run devhttp://localhost:3000Output:
🚀 Starting development server...
✅ Dev server iniciado en: http://localhost:3000
Presiona Ctrl+C para detenersnv deploy - Deploy a Vercel (ORQUESTADOR)snv deploy
snv deploy --prodQué hace:
vercel link --yesnpm run buildvercel deploy o vercel deploy --prodOutput:
🔍 Checking Vercel CLI...
✅ Vercel CLI listo
🔨 Building project...
✅ Build completado
🚀 Deploying to Vercel...
✅ Deploy completado!
🌐 Deployment URL:
https://my-app.vercel.app
📝 Environment variables en Vercel:
DEBES CONFIGURARLAS MANUALMENTE EN EL DASHBOARD DE VERCEL:
https://vercel.com/dashboard
Variables requeridas:
NEXT_PUBLIC_SUPABASE_URL
NEXT_PUBLIC_SUPABASE_ANON_KEY
SUPABASE_SERVICE_KEY
⚠️ NOTA: Asegúrate de configurar estas variables en Vercel para que funcione en producción| Template | Descripción | Features |
|---|---|---|
minimal | Básico | Next.js + Supabase client |
auth-db | RECOMENDADO | Auth + Database |
auth | Con Auth | Login/Signup páginas + utilities |
full | Completo | Auth + DB + Storage |
Para todos los proyectos:
# .env.local
NEXT_PUBLIC_SUPABASE_URL=https://yourproject.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=your_anon_key_here
# Service role key (requerido para snv db:setup)
SUPABASE_SERVICE_KEY=your_service_role_key_hereObtén tus credenciales en:
Fase de Inicialización (snv init)
Fase de Conexión (snv db:setup)
.env.localFase de Configuración (snv auth:setup, snv storage:setup)
Fase de Desarrollo (snv dev)
Fase de Deployment (snv deploy)
El skill genera migrations con SQL VALIDO y ejecutable:
Migration de Auth (002_enable_auth.sql):
-- Habilitar Authentication en Supabase
-- 1. Habilitar Email Auth
alter schema auth.users enable row level security;
-- 2. Crear tabla de usuarios
create table if not exists public.users (
id uuid default gen_random_uuid() primary key,
email text unique not null,
created_at timestamp with time zone default timezone('utc', now()) not null,
updated_at timestamp with time zone default timezone('utc', now()) not null
);
-- 3. Configurar RLS para usuarios
alter table public.users enable row level security;
create policy "Usuarios pueden ver su propio perfil"
on public.users for select
using (auth.uid())
with check (auth.uid() = id);
grant select;Migration de Storage (003_enable_storage.sql):
-- Habilitar Storage en Supabase
-- 1. Crear buckets de ejemplo
insert into storage.buckets (id, name, public, file_size_limit, allowed_mime_types)
values
('avatars', 'avatars', true, 5242880, 'image/jpeg,image/png,image/gif'),
('documents', 'documents', true, 52428800, 'application/pdf,application/msword,text/plain')
on conflict (id) do nothing;
-- 2. Nota: Las políticas RLS deben configurarse manualmente
-- En Dashboard: https://supabase.com/dashboard/project/_/storage/policiesSolución: Actualizar Node.js a v22.22.0+
# Verificar versión
node --version
# Actualizar NVM
nvm install 22.22.0
nvm alias default 22.22.0
# O actualizar symlink de sistema (Linux)
sudo ln -sf ~/.nvm/versions/node/v22.22.0/bin/node /usr/local/bin/node**Solución: Ejecutar snv init primero
Solución:
.env.localSolución:
npm install -g vercelSolución:
vercel link# 1. Crear proyecto
snv init my-app --template auth-db
# 2. Configurar credenciales
cd my-app
# Editar .env.local con:
# NEXT_PUBLIC_SUPABASE_URL=https://xxx.supabase.co
# NEXT_PUBLIC_SUPABASE_ANON_KEY=eyJ...
# SUPABASE_SERVICE_KEY=eyJ...
# 3. Configurar database (auto-conecta + migrations)
snv db:setup
# 4. Configurar authentication (genera SQL)
snv auth:setup
# 5. Ejecutar migrations en Supabase Dashboard
# ABRE: https://supabase.com/dashboard/project/_/sql/new
# Copia y ejecuta 002_enable_auth.sql
# 6. Iniciar desarrollo
snv dev# 1. En desarrollo
cd my-app
# 2. Build y deploy
snv deploy --prod
# 3. Configurar env vars en Vercel Dashboard
# ABRE: https://vercel.com/dashboard
# Agrega: NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_KEY# 1. En desarrollo
cd my-app
# 2. Configurar storage (genera SQL)
snv storage:setup --buckets avatars
# 3. Ejecutar migration en Supabase Dashboard
# ABRE: https://supabase.com/dashboard/project/_/sql/new
# Copia y ejecuta 003_enable_storage.sql
# 4. Configurar políticas RLS en Supabase Dashboard
# ABRE: https://supabase.com/dashboard/project/_/storage/policiesnpm i -g vercelSkills individuales:
Nuestra skill:
Antfarm:
Nuestra skill:
Este skill es open source. Para mejorar:
Mejoras bienvenidas en:
ORQUESTADOR REAL para Next.js + Supabase + Vercel - De la idea al deploy en 30 segundos. 🚀
© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 12 other files in skills/next-supabase-vercel-bundle of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Next Supabase Vercel Bundle next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Next Supabase Vercel Bundle this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.3k | Automated safety check: Notes | MIT | |
| Safe SQL Executionsupabase/supabase | 111k | — | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Replica ArchitectJakeschincariol/replica-skill | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Openagentskill RegistryLeon-Drq/openagentskill | 357 | — | ~437 | Automated safety check: Pass | MIT | |
| Find SkillsLeon-Drq/openagentskill | 357 | — | ~539 | Automated safety check: Pass | MIT | |
| Srtd CLIt1mmen/srtd | 105 | — | ~360 | Automated safety check: Pass | MIT |
supabase/supabase
A skill your agent uses whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix…
Jakeschincariol/replica-skill
Plans the stack, database schema and API for an app clone, from the recon map replica-recon wrote.
Leon-Drq/openagentskill
Discover, compare, audit, and safely install reusable AI Agent Skills with OpenAgentSkill.
Leon-Drq/openagentskill
Find, compare, audit, and safely install reusable AI agent skills from OpenAgentSkill.
t1mmen/srtd
This skill should be used when the user mentions "srtd", "sql templates", "migrations-templates", "live reload sql", "supabase functions", when working with files in supabase/migrations-templates/…
faasjs/faasjs
A skill your agent uses when working with @faasjs/pg or PostgreSQL in FaasJS: Tables declaration merging, QueryBuilder, select aliases, parameterized sql expressions, raw SQL, numeric/decimal/bigint…
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Works with
Categories
ORQUESTADOR REAL para el ciclo completo de desarrollo Full-Stack. Next Supabase Vercel Bundle is an agent skill from LeoYeAI/openclaw-master-skills. ORQUESTADOR REAL para el ciclo completo de desarrollo Full-Stack.
Next Supabase Vercel Bundle fits situations like: tasks that involve SQL.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill next-supabase-vercel-bundle -a claude-code`. Or copy the skill folder (skills/next-supabase-vercel-bundle in LeoYeAI/openclaw-master-skills) into .claude/skills/next-supabase-vercel-bundle in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill next-supabase-vercel-bundle -a codex`. Or copy the skill folder (skills/next-supabase-vercel-bundle in LeoYeAI/openclaw-master-skills) into .agents/skills/next-supabase-vercel-bundle in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill next-supabase-vercel-bundle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/next-supabase-vercel-bundle, .gemini/skills/next-supabase-vercel-bundle, .github/skills/next-supabase-vercel-bundle and .opencode/skills/next-supabase-vercel-bundle in your project.
Going by SKILL.md and its folder, Next Supabase Vercel Bundle needs JavaScript and TypeScript for the scripts in its folder, the command-line tools its instructions call (npm, vercel, nvm and node) and credentials named SUPABASE_SERVICE_KEY and NEXT_PUBLIC_SUPABASE_ANON_KEY. Our summary lists: Node.js; A credential in SUPABASE_SERVICE_KEY; A credential in NEXT_PUBLIC_SUPABASE_ANON_KEY.
SKILL.md names 3 domains. In commands or code: supabase.com, xxx.supabase.co and vercel.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file; runs commands with sudo), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Next Supabase Vercel Bundle is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Next Supabase Vercel Bundle: Safe SQL Execution (supabase/supabase, 111k stars), Replica Architect (Jakeschincariol/replica-skill, 1.2k stars), Openagentskill Registry (Leon-Drq/openagentskill, 357 stars) and Find Skills (Leon-Drq/openagentskill, 357 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,160 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.