SkillBoss
Multi-AI gateway for building and deploying full-stack apps: websites, payments (Stripe), auth (Google OAuth), databases (D1/KV/R2), AI image/audio/video, email, and more.
How It Works
- Build / deploy request: Site · SaaS · API · login · payments · AI gen
- Init project + provision: Workers-React template · D1/KV/R2 auto-provisioned
- Add capabilities: Google OAuth · Stripe · AI image/audio/video · email
- Build the app: Wire features via api-hub.js across 50+ AI APIs
- Deploy to Cloudflare: wrangler deploy to the edge
- Live app: Hosted Workers app with full stack wired
Invocation Triggers
/skillbossbuild websitedeploy siteadd Stripeadd logingenerate imagetext to speechUse Cases
- Deploy a full-stack app to Cloudflare Workers with D1 database
- Add Stripe checkout or subscriptions to any project
- Generate images, audio, or video using 50+ AI models via one gateway
The Problem
Shipping a real app means assembling a dozen vendors — a host, a database, payments, auth, an image API, a TTS provider, an email sender — each with its own SDK, its own keys, its own quirks. You spend more time gluing services than building the thing. Every new capability is another integration and another set of credentials to manage. SkillBoss collapses that into one CLI over 50-plus APIs and the full Workers stack, so add-a-database and add-payments are one command each instead of an afternoon.
What It Does
- 1Init the project
deploy.js scaffolds a Cloudflare Workers app from a template — workers-react, a landing page, an API, or a webhook endpoint.
- 2Provision storage
Add a D1 SQL database, a KV store, or R2 object storage with a single add command. Bindings are auto-provisioned into the Workers config.
- 3Add auth and payments
add-auth wires Google OAuth or email OTP with session management. add-stripe sets up checkout, subscriptions, and webhooks. One command each.
- 4Call AI and utility services
api-hub.js routes to 50-plus APIs — image generation, text-to-speech and speech-to-text, video, email, web search, scraping, and document parsing — through one interface and one key.
- 5Deploy
wrangler deploy ships the app to Cloudflare's edge. Per-service secrets live in .env or wrangler.toml; only the services you actually use need keys.
What You Get / What It Doesn't Do
- A deployed Cloudflare Workers app on the edge
- Auto-provisioned D1, KV, or R2 storage with bindings wired
- Stripe checkout, subscriptions, and webhooks configured
- Google OAuth or email OTP auth with session management
- One CLI reaching image, audio, video, email, search, and scrape APIs
- Design your product or decide your architecture — you direct it
- Pay for the underlying services — you bring your own keys and billing
- Replace Stripe or Cloudflare dashboard work for live-mode compliance
- Manage secret rotation or production env hardening for you
Tips
Before you go pull a vendor SDK, check whether SkillBoss already routes to it. The win is one key and one interface instead of a new integration per capability.
Per-service secrets are needed only for the services you actually call. Do not populate the whole .env up front; add keys as you add capabilities.
add-d1, add-auth, and add-stripe write bindings into wrangler.toml. Verify those landed before wrangler deploy, not after the app 500s at the edge.
Get the Skill
Unlock the full SkillBoss SKILL.md — drop it into ~/.claude/skills/ and trigger it by name.
- A deployed Cloudflare Workers app on the edge
- Auto-provisioned D1, KV, or R2 storage with bindings wired
- Stripe checkout, subscriptions, and webhooks configured
- Google OAuth or email OTP auth with session management
29 more production skills ready to install.