Workflow Init
Bootstrap the Vercel Workflow SDK in a greenfield or not-yet-installed repo with the right framework-specific getting-started steps.
Overview
workflow-init is an agent skill for the Build phase that installs and configures the Vercel Workflow SDK before the workflow package exists in node_modules.
Install
npx skills add https://github.com/vercel/workflow --skill workflow-initWhat is this skill?
- Runs only when workflow is absent from package.json—otherwise redirects to /workflow versioned docs
- Auto-detects framework from deps and config across 10 stacks (Next.js through Vite)
- Fetches the official getting-started guide for the detected framework
- Supports explicit framework choice when the user names it in the prompt
- Decision flow starts with package.json sanity check before any install
- Auto-detect priority list covers 10 framework signals (Next.js through Vite)
- Skill metadata version 1.3
Adoption & trust: 1.8k installs on skills.sh; 2.1k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want durable Vercel workflows in your app but package.json still has no workflow dependency and you are unsure which framework guide to follow.
Who is it for?
Indie full-stack devs starting Workflow SDK integration on Next.js, Express, Hono, NestJS, or other supported frameworks.
Skip if: Repos that already list workflow as a dependency—use the /workflow skill for in-tree versioned documentation instead.
When should I use this skill?
Install and configure Vercel Workflow SDK before it exists in node_modules when the user asks to install workflow, set up workflow, add durable workflows, configure workflow sdk, or init workflow for supported frameworks
What do I get? / Deliverables
You get framework-matched official setup steps applied and workflow added/configured—or a clear handoff to /workflow if it was already installed.
- Installed workflow dependency
- Framework-aligned configuration per official getting-started guide
Recommended Skills
Journey fit
How it compares
First-install bootstrap skill—not the ongoing workflow authoring reference that ships inside node_modules.
Common Questions / FAQ
Who is workflow-init for?
Solo builders and small teams on supported JS frameworks who are adding Vercel Workflow for the first time and need an agent-led install path.
When should I use workflow-init?
During Build when the user asks to install workflow, set up the SDK, init durable workflows, or configure Workflow for their stack before dependencies exist.
Is workflow-init safe to install?
Check this page’s Security Audits panel; installing packages and fetching remote docs affects your repo and network—review changes before merging.
SKILL.md
READMESKILL.md - Workflow Init
# 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 web` or `npx 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/`.