Web Deploy

Build, preview, and deploy websites, web apps, and APIs using Vercel, Railway, GitHub Pages, or local Canvas environments.

Security Scan

Instruction-only deploy guide that contains typical commands for Vercel, Railway, GitHub Pages and a local Canvas path; the steps and requested actions are consistent with a deployment helper and nothing in the skill asks for unrelated credentials or system access.

Purpose & Capability

The SKILL.md provides a coherent set of deployment and local-preview commands for static sites, Next.js, Vite, FastAPI and deployment targets (Vercel, Railway, GitHub Pages, and a local 'clawd/canvas' folder). There are no unrelated requirements (no unexpected env vars, binaries, or config paths).

Instruction Scope

Instructions stay within the scope of building, previewing, and deploying web apps. They instruct using standard CLIs (vercel, railway, gh-pages) and local copy commands. The doc does not instruct reading unrelated files, exfiltrating data, or calling unexpected external endpoints.

Install Mechanism

No install spec or bundled code — this is instruction-only. Nothing will be written automatically to disk by the skill itself.

Credentials

The skill declares no required environment variables or credentials, which is reasonable for an instruction-only guide. However the commands it recommends (e.g., `railway login`, `npx vercel`, `npx vercel env add`) will prompt you to authenticate to third-party services and/or create environment variables on those platforms at runtime; the guide does not attempt to collect those secrets itself.

Persistence & Privilege

always is false and there are no instructions to modify other skills or global agent settings. The recommended CLIs may store authentication tokens locally when you run them, but the skill itself does not request persistent privileges.

Assessment

This skill is an instruction-only deployment guide and appears coherent with its purpose. Before using it, keep these points in mind: - The file only suggests commands — it does not itself install anything or request credentials. You will need to run CLI tools (vercel, railway, gh-pages, npx, etc.) and those tools will require you to authenticate; that authentication is handled by those CLIs and may store tokens locally. - npx runs packages from the npm registry if a local binary isn't present. Verify command names (e.g., `vercel`, `http-server`, `serve`) are correct and from official packages to avoid typosquatting risks. - Do not commit secrets to git or include .env contents in your build artifacts; the guide already warns about this. - The guide includes copying files to ~/clawd/canvas — ensure you understand and trust that local path and its purpose before copying site files there. - If you want stronger assurance, install the official CLIs from vendor documentation (rather than running one-off npx invocations), and verify the source of any package before executing it.

Build and deploy websites, web apps, and APIs to production.

Local Preview Workflow

# Static site
npx http-server ./dist -p 8080 -c-1

# Next.js
npm run dev          # Development (hot reload)
npm run build && npm run start  # Production preview

# FastAPI
uvicorn app.main:app --reload --port 8000

# Vite-based
npm run dev          # Dev server
npm run build && npx serve dist  # Production preview

Deployment Targets

Vercel (Frontend / Next.js / Static)

# First time setup
npx vercel link

# Preview deployment
npx vercel

# Production deployment
npx vercel --prod

# Environment variables
npx vercel env add SECRET_KEY

Best for: Next.js apps, React SPAs, static sites, serverless functions.

Config: vercel.json (usually not needed for Next.js)

{
  "buildCommand": "npm run build",
  "outputDirectory": "dist",
  "framework": "nextjs"
}

Railway (Backend / APIs / Databases)

# First time setup
railway login
railway init

# Deploy
railway up

# Add database
railway add --plugin postgresql

# Environment variables
railway variables set SECRET_KEY=value

# View logs
railway logs

Best for: Backend APIs, databases, long-running processes, Docker containers.

GitHub Pages (Static Sites)

# Using gh-pages package
npm install -D gh-pages
# Add to package.json scripts: "deploy": "gh-pages -d dist"
npm run build && npm run deploy

Best for: Documentation, simple static sites, project pages.

Canvas (Clawdbot Workspace)

Deploy to ~/clawd/canvas/ for local serving through the clawdbot gateway.

cp -r ./dist/* ~/clawd/canvas/my-project/

Pre-Deploy Checklist

• Build succeeds locally (npm run build / python -m build)
• No TypeScript/lint errors
• Tests pass
• Environment variables set on target platform
• .env / secrets NOT in git
• robots.txt and sitemap.xml if public site
• Favicon and meta tags set
• HTTPS configured (automatic on Vercel/Railway)
• Error pages (404, 500) configured
• Performance: images optimized, code split, no huge bundles

Rollback

# Vercel — redeploy previous
npx vercel rollback

# Railway — redeploy previous
railway rollback

# Git-based — revert and push
git revert HEAD && git push

Domain Setup

# Vercel
npx vercel domains add mydomain.com

# DNS: Point CNAME to cname.vercel-dns.com
# Or A record to 76.76.21.21