deploy
- Repo stars 330
- License MIT
- Author updated Live
- Author repo claude-skill-registry
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @majiayu000 · MIT
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Env read
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: deploy
description: Deploy workflow for Vercel and Supabase Edge Functions npx vercel --yes npx vercel --prod --yes…
category: data
runtime: no special runtime
---
# deploy output preview
## PART A: Task fit
- Use case: Deploy workflow for Vercel and Supabase Edge Functions npx vercel --yes npx vercel --prod --yes supabase functions deploy [name] --project-ref [ref] supabase functions deploy --project-ref [ref] runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Pre-deploy Checklist / Vercel / Supabase Edge Functions” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Deploy workflow for Vercel and Supabase Edge Functions npx vercel --yes npx vercel --prod --yes supabase functions deploy [name] --project-ref [ref] supabase functions deploy --project-ref [ref] runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Pre-deploy Checklist / Vercel / Supabase Edge Functions” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, read environment variables, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, read environment variables, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, read environment variables, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Pre-deploy Checklist / Vercel / Supabase Edge Functions”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: deploy
description: Deploy workflow for Vercel and Supabase Edge Functions npx vercel --yes npx vercel --prod --yes…
category: data
source: majiayu000/claude-skill-registry
---
# deploy
## When to use
- Deploy workflow for Vercel and Supabase Edge Functions npx vercel --yes npx vercel --prod --yes supabase functions dep…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Pre-deploy Checklist / Vercel / Supabase Edge Functions” and keep inference separate from source facts.
- read files, read environment variables, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "deploy" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Pre-deploy Checklist / Vercel / Supabase Edge Functions
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, read environment variables, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Deploy Workflow
Pre-deploy Checklist
npm run typecheck- passesnpm run build- passesnpm run test- passes (if available)- No
console.login production code - Environment variables set in hosting platform
Vercel
Preview:
npx vercel --yesProduction:
npx vercel --prod --yesSupabase Edge Functions
Single function:
supabase functions deploy [name] --project-ref [ref]All functions:
supabase functions deploy --project-ref [ref]Post-deploy
- Verify production URL loads
- Test critical user flows
- Monitor error logs for 5 minutes
Decide Fit First
Design Intent
How To Use It
Boundaries And Review