vanthienha199vanthienha199/openclaw-skills/deploy-kit/SKILL.md

deploy-kit

Skill1 starsChanged 8 months agoMITView on GitHub

Deploy projects to Vercel, Netlify, or Fly.io with one command. Auto-detects framework (Next.js, React, Python, Node.js, static HTML). Shows deploy URL when done. Supports rollback. Use when the user asks to deploy, ship, publish, or push to production. Triggers on: "deploy this", "ship it", "push to production", "deploy to vercel", "deploy to netlify", "deploy to fly", "go live".

Pipes a download into a shell
Installs packages

In this repository9 other files it gives its agents.
- figma-bridgeSkill
- job-hunterSkill
- meeting-notesSkill
- project-kickstartSkill
- slide-deckSkill
- smart-cost-trackerSkill
- social-posterSkill
- supabaseSkill
- translateSkill

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
When the user says "deploy" or "ship", detect what kind of project it is and deploy to the best platform.
line 27
Distinctive:
Check the project root for these files to determine the framework:
line 31
Distinctive:
Run the deploy command and show the output URL.
line 103
Distinctive:
Check the current deployment status:
line 118
Distinctive:
Always ask before deploying to production: "Deploy to production?
line 153
Distinctive:
If deploy fails, show the error and suggest a fix
line 155
Distinctive:
Never store or expose API tokens — use the CLI's built-in auth
line 156
Distinctive:
Default to preview/staging deploy, not production
line 157
Distinctive:
If no platform preference, recommend based on auto-detection table
line 158

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Deploy Kit

You deploy projects to Vercel, Netlify, or Fly.io. One command, auto-detection, done.

Core Behavior

When the user says "deploy" or "ship", detect what kind of project it is and deploy to the best platform. If the user specifies a platform, use that one.

Auto-Detection

Check the project root for these files to determine the framework:

File	Framework	Best Platform
`next.config.*`	Next.js	Vercel
`package.json` with `react-scripts`	Create React App	Vercel or Netlify
`index.html` (no package.json)	Static site	Netlify
`fly.toml`	Already configured for Fly.io	Fly.io
`Dockerfile`	Container	Fly.io
`requirements.txt` or `pyproject.toml`	Python	Fly.io
`Procfile`	Heroku-style	Fly.io
`astro.config.*`	Astro	Vercel or Netlify
`svelte.config.*`	SvelteKit	Vercel
`nuxt.config.*`	Nuxt	Vercel

Deploy Commands

Vercel

# Check if vercel CLI is installed
which vercel || npm install -g vercel

# Deploy (auto-detects framework)
vercel --yes

# Deploy to production
vercel --prod --yes

Netlify

# Check if netlify CLI is installed
which netlify || npm install -g netlify-cli

# Deploy preview
netlify deploy --dir=.

# Deploy to production
netlify deploy --prod --dir=.

# For static sites, detect the build output directory:
# Next.js: out/ or .next/
# React: build/
# Plain HTML: . (current directory)

Fly.io

# Check if fly CLI is installed
which fly || curl -L https://fly.io/install.sh | sh

# If no fly.toml, launch new app
fly launch --yes --no-deploy

# Deploy
fly deploy

Workflow

Step 1: Detect

Detected: Next.js project (found next.config.js)
Recommended platform: Vercel

Step 2: Check CLI

Vercel CLI: installed (v37.2.0)

Step 3: Deploy

Run the deploy command and show the output URL.

Step 4: Report

Deployed to Vercel
URL: https://my-project-abc123.vercel.app
Production: https://my-project.vercel.app
Time: 34s
Framework: Next.js
Region: iad1 (US East)

Other Commands

"Status" / "Is it live?"

Check the current deployment status:

vercel ls --limit 1
# or
netlify status
# or
fly status

"Rollback"

vercel rollback
# or
netlify rollback
# or
fly releases --image

"Logs"

vercel logs [url]
# or
netlify logs
# or
fly logs

"Add domain"

vercel domains add mydomain.com
# or
netlify domains:add mydomain.com

Rules

Always ask before deploying to production: "Deploy to production? (y/n)"
Show the URL immediately after deploy completes
If deploy fails, show the error and suggest a fix
Never store or expose API tokens — use the CLI's built-in auth
Default to preview/staging deploy, not production
If no platform preference, recommend based on auto-detection table

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free