nexus-deployments
Provides standard deployment and infrastructure management procedures for web apps and browser extensions.
Install
mkdir -p .claude/skills/nexus-deployments && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14180" && unzip -o skill.zip -d .claude/skills/nexus-deployments && rm skill.zipInstalls to .claude/skills/nexus-deployments
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Deployment protocols for Vercel (Next.js Web App), Chrome Web Store packaging (Plasmo Extension), and Supabase production migrations. Use this when setting up CI/CD, preparing a release, or configuring deployment environment variables.Key capabilities
- →Configure Vercel deployments for Next.js monorepos
- →Manage environment variables for Vercel deployments
- →Set maxDuration for Next.js Edge Functions
- →Build Plasmo extensions for production
- →Package Plasmo extensions for Chrome Web Store submission
- →Generate Supabase database migrations
How it works
The skill provides protocols and commands for deploying Next.js web apps to Vercel, packaging Plasmo extensions, and managing Supabase production migrations.
Inputs & outputs
When to use nexus-deployments
- →Deploy Next.js to Vercel
- →Package a Chrome extension
- →Generate database migrations
About this skill
Project Nexus: Deployment & DevOps Protocol
1. Vercel Deployment (Next.js Web App)
- Monorepo Handling: If the project is structured as a monorepo (e.g., Turborepo or npm workspaces), ensure the Vercel Root Directory is set to
apps/web(or the folder containing the Next.js app). - Build Command: The build command must strictly be
npm run build(orpnpm build). - Environment Variables: Never commit
.envfiles. When setting up deployments, explicitly list the required Vercel environment variables (e.g.,NEXT_PUBLIC_SUPABASE_URL,NEXT_PUBLIC_SUPABASE_ANON_KEY). - Edge Functions: For long-running AI summarization tasks, ensure the Next.js API routes specify
export const maxDuration = 60;to prevent Vercel's default 10-second timeout on the hobby tier.
2. Plasmo Extension Deployment
- Production Build: To build the extension for production, run
plasmo build --target=chrome-mv3. - Zip Packaging: For Chrome Web Store submission, use
plasmo package. This generates the.zipfile. - Manifest Validation: Before building, ensure the
package.jsoncontains the correct version number, description, and permissions (e.g.,storage,activeTab,scripting) required by the Chrome Web Store.
3. Supabase Production Migrations
- Database Changes: Never make database schema changes directly in the Supabase production dashboard.
- Migration Generation: Always use the Supabase CLI:
supabase db diff -f feature_nameto generate a migration file. - Type Generation: After a database change, run
supabase gen types typescript --local > types/supabase.tsto keep the frontend types perfectly synced with the backend schema.
When not to use it
- →When deploying applications not using Vercel, Plasmo, or Supabase
- →When managing infrastructure outside of these specific platforms
Limitations
- →The skill is specific to Vercel (Next.js), Plasmo (Chrome Web Store), and Supabase.
- →The skill does not cover deployment for other cloud providers or application types.
How it compares
This skill centralizes and standardizes deployment procedures for specific platforms, offering explicit instructions and best practices, unlike a manual process that might involve disparate documentation and potential inconsistencies.
Compared to similar skills
nexus-deployments side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| nexus-deployments (this skill) | 0 | 5mo | Review | Intermediate |
| vercel-deployment | 3 | 6mo | No flags | Intermediate |
| vercel-deploy | 4 | 5mo | Review | Beginner |
| vercel-multi-env-setup | 1 | 29d | Caution | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
vercel-deployment
davila7
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.
vercel-deploy
openai
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
vercel-multi-env-setup
jeremylongshore
Configure Vercel across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Vercel configurations. Trigger with phrases like "vercel environments", "vercel staging", "vercel dev prod", "vercel environment setup", "vercel config by env".
vercel-deploy-preview
jeremylongshore
Execute Vercel primary workflow: Deploy Preview. Use when Deploying a preview for a pull request, Testing changes before production, or Sharing preview URLs with stakeholders. Trigger with phrases like "vercel deploy preview", "create preview deployment with vercel".
vercel-cli-management
CaptainCrouton89
Deploy, manage environment variables, view logs, and configure cron jobs with Vercel CLI. Use when deploying to Vercel, managing env vars (add/update/remove), viewing runtime/build logs, or configuring scheduled tasks in vercel.json.
onboarding
ColeMurray
Deploy your own Open-Inspect instance. Use when the user wants to set up, deploy, or onboard to Open-Inspect. Guides through repository setup, credential collection, Terraform deployment, and verification with user handoffs.