Workflow Init
- 2.8k installs
- 2.3k repo stars
- Updated August 5, 2026
- vercel/workflow
workflow-init installs and configures Vercel Workflow SDK by fetching the framework-specific getting-started guide before workflow is in node_modules.
About
The workflow-init skill sets up the Vercel Workflow SDK before the workflow package is installed, fetching the official getting-started guide for the detected framework. It reads package.json and if workflow is already a dependency, redirects users to the /workflow skill that reads bundled node_modules docs. Framework auto-detection checks next, nuxt, sveltekit, astro, nestjs, nitro, express, fastify, hono, and vite in priority order, or asks the user when ambiguous. Each framework maps to a workflow-sdk.dev getting-started URL covering install, configuration, first workflow, route handler, and verification curl. Verification starts the dev server, triggers the example endpoint, confirms workflow logs, and optionally runs npx workflow web or inspect runs. If no framework exists, it asks whether the user wants a web app or API server and follows the chosen guide project creation section.
- Pre-install setup only; redirects to /workflow if workflow dep already exists.
- Auto-detects framework from package.json deps and config files.
- Fetches one workflow-sdk.dev getting-started guide per framework.
- Supports Next.js, Nuxt, SvelteKit, Astro, NestJS, Express, Hono, Fastify, Nitro, Vite.
- Verifies setup by curling example endpoint and checking workflow execution logs.
Workflow Init by the numbers
- 2,827 all-time installs (skills.sh)
- +107 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #63 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
workflow-init capabilities & compatibility
- Capabilities
- framework auto detection from package.json · per framework getting started guide fetching · pre install sanity check against existing workfl · dev server verification with example endpoint cu · handoff to /workflow for post install developmen
- Works with
- vercel
- Use cases
- ci cd · orchestration · api development
What workflow-init says it does
Each guide covers: install deps, configure framework, create first workflow, create route handler, run + verify.
npx skills add https://github.com/vercel/workflow --skill workflow-initAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.8k |
|---|---|
| repo stars | ★ 2.3k |
| Security audit | 2 / 3 scanners passed |
| Last updated | August 5, 2026 |
| Repository | vercel/workflow ↗ |
How do I set up Vercel Workflow SDK on Next.js or Express before the workflow package is installed?
Install and configure Vercel Workflow SDK for Next.js, Express, Hono, or other supported frameworks before workflow exists in node_modules.
Who is it for?
Projects adding durable workflows via Vercel Workflow SDK for supported JavaScript frameworks.
Skip if: Skip when workflow is already installed; use the /workflow skill for versioned node_modules docs instead.
When should I use this skill?
User asks to install workflow, set up durable workflows, init workflow sdk, or configure workflow for Next.js.
What you get
Installed workflow dependency, framework config, example workflow route, and verified dev server execution.
- Framework-specific Workflow SDK install instructions
- Pre-install sanity check result
By the numbers
- Skill version 1.3 authored by Vercel Inc.
- Supports 10 JavaScript frameworks including Next.js, Express, Hono, Fastify, NestJS, Nitro, Nuxt, Astro, SvelteKit, and
Files
workflow-init
Initial setup of Vercel Workflow SDK before workflow is installed. Fetch the official getting-started guide for the user's framework.
Decision Flow
0) Sanity check
Read package.json. If workflow is already a dependency, tell the user to use /workflow instead (it reads versioned docs from node_modules/workflow/docs/). Only continue if workflow is missing.
1) Determine the framework
Non-interactive: If the user named a framework in their prompt, use it directly.
Auto-detect: Inspect package.json deps and config files. Use the first match:
1. Next.js - next dep or next.config.* 2. Nuxt - nuxt dep or nuxt.config.* 3. SvelteKit - @sveltejs/kit dep or svelte.config.* 4. Astro - astro dep or astro.config.* 5. NestJS - @nestjs/core dep or nest-cli.json 6. Nitro - nitro dep or nitro.config.* 7. Express - express dep 8. Fastify - fastify dep 9. Hono - hono dep 10. Vite - vite dep (and not matched above)
If no match or multiple matches, ask the user to pick.
2) Fetch and follow the getting-started guide
Fetch exactly one of these URLs and follow the guide step-by-step:
| Framework | URL |
|---|---|
| Next.js | https://workflow-sdk.dev/docs/getting-started/next |
| Express | https://workflow-sdk.dev/docs/getting-started/express |
| Hono | https://workflow-sdk.dev/docs/getting-started/hono |
| Fastify | https://workflow-sdk.dev/docs/getting-started/fastify |
| NestJS | https://workflow-sdk.dev/docs/getting-started/nestjs |
| Nitro | https://workflow-sdk.dev/docs/getting-started/nitro |
| Nuxt | https://workflow-sdk.dev/docs/getting-started/nuxt |
| Astro | https://workflow-sdk.dev/docs/getting-started/astro |
| SvelteKit | https://workflow-sdk.dev/docs/getting-started/sveltekit |
| Vite | https://workflow-sdk.dev/docs/getting-started/vite |
Each guide covers: install deps, configure framework, create first workflow, create route handler, run + verify.
3) Verify setup
- Start the dev server per the guide.
- Trigger the example endpoint with the provided
curl. - Confirm logs show the workflow and steps executing.
- Optional:
npx workflow webornpx workflow inspect runs.
4) No framework yet?
If no framework exists, ask what the user wants:
- Web app: Next.js / Nuxt / SvelteKit / Astro
- API server: Express / Fastify / Hono
- Minimal server: Nitro or Vite
Then follow the "Create Your Project" section of the chosen guide.
Concept questions (pre-install)
If the user asks conceptual questions before installing, fetch:
- https://workflow-sdk.dev/docs/foundations/workflows-and-steps
- https://workflow-sdk.dev/cookbook
Handoff
When setup is complete, tell the user: Use `/workflow` for ongoing development - it reads the versioned docs bundled in node_modules/workflow/docs/.
Related skills
Azure DeploySafely execute production deployments of already-prepared applications to Microsoft Azure.485k1.3kAzure ValidateRun deep pre-deployment checks on Azure configuration, infrastructure definitions, RBAC roles, and managed identities before pushing to production.485k1.3k
Github Actions DocsGet precise, docs-grounded answers about GitHub Actions workflows, syntax, security, and migration instead of relying on stale knowledge.275k72
Setup Pre CommitAutomatically run Prettier, type checking, and tests on every commit via Husky and lint-staged.170k199k
Deploy To VercelSafely turn any local project into a live Vercel preview with one instruction.99.3k29.7kVercel Cli With TokensDeploy projects to Vercel from agents and scripts using token authentication instead of interactive browser login.74.6k29.7kHow it compares
Use workflow-init for first-time SDK bootstrap; switch to /workflow once the workflow package is already listed in package.json.
FAQ
What if workflow is already in package.json?
Stop and tell the user to use /workflow which reads versioned docs from node_modules/workflow/docs/.
How is the framework chosen?
Auto-detect from package.json and config files in priority order, or ask the user if ambiguous.
How is setup verified?
Start dev server, curl the example endpoint, and confirm workflow and step logs execute.
Is Workflow Init safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.