Skip to main content
skill Claude Code CX Codex Cursor GitHub Copilot

workflow-init — Claude Code skill: what it does, how to install

Sets up Vercel Workflow SDK in a project where workflow is not installed yet: picks the framework from package.json and walks the official guide up to a working first run.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add vercel/workflow --skill workflow-init -a claude-code
Open on GitHub

What workflow-init does

This skill covers the moment before workflow exists in node_modules. It reads package.json plus config files and matches them against a fixed order — next, nuxt, @sveltejs/kit, astro, @nestjs/core, nitro, express, fastify, hono, vite — then pulls exactly one getting-started guide and follows it: dependencies, framework config, a first workflow, a route handler, a run.

Several matches or none at all means it asks instead of guessing. In an empty directory you pick between a web app, an API server and a minimal server, and the skill starts from the project-creation section of that guide. Concept questions before installing get answered too, from the workflows-and-steps and cookbook material.

Verification is part of the flow: start the dev server, hit the example endpoint with curl, read the logs to see steps executing. Optional extras are npx workflow web and npx workflow inspect runs. Once workflow is already a dependency, skip this skill — it hands off to /workflow, which reads versioned docs from node_modules/workflow/docs/. Run it before the package lands, not after.

What it helps with

  • get a durable workflow running in a fresh Next.js app
  • settle which framework you are on when package.json matches several
  • confirm the workflow steps actually execute instead of failing quietly
  • wire a first route handler into a Hono or Fastify server
  • grasp what a workflow and a step are before adding the dependency

Example prompts for the agent

  • Install workflow in my Next.js project and show me how to run the first workflow
  • Set up the workflow sdk in this Express app, it's empty right now
  • Add durable workflows to my SvelteKit project, the framework is already there

How to install workflow-init

1Skills CLI (Vercel)

npx skills add vercel/workflow --skill workflow-init -a claude-code

2Manually: put the files in place

~/.claude/skills/workflow-init/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/workflow-init/

From the same set2

The whole set →

Similar

nitro Anthony Fu A skill with Nitro v3 references: file-based routing, route rules, caching, storage and deployment presets. Use it when the agent edits nitro.config or writes H3 handlers. Claude Code CX Codex Cursor +1 2,600installs dart-build-cli-app dart-lang Skill for building command-line applications in Dart. Provides architectural patterns, entrypoint structure, exit codes, stream routing, and subprocess spawning. Claude Code CX Codex Cursor +1 18,000installs api-docs ruvnet Skill that turns TypeScript and JavaScript source into documentation: it finds public exports, reads existing JSDoc, writes the missing comments and emits OpenAPI 3.0 for HTTP endpoints. Claude Code CX Codex Cursor +1 891installs python-pypi-package-builder official github This skill guides Python package creation, testing, versioning, and PyPI publishing. Use it for libraries, SDKs, CLI tools, and framework plugins. GitHub Copilot 943installs pi-agent K-Dense-AI Helps you install and configure Pi, then build extensions, integrations, and terminal UI components around it. Claude Code CX Codex Cursor +1 1,200installs wordpress-penetration-testing zebbern This skill audits WordPress installations for common vulnerabilities and REST API permission issues in plugins. Designed for authorized security assessments. Claude Code CX Codex Cursor +1 1,100installs mcp-builder official anthropics This skill walks through building an MCP server in TypeScript or Python, from reading the protocol spec to writing tests and evaluation questions. Claude Code Claude.ai 130,949installs google-agents-cli-adk-code official Google A reference skill for building ADK agents with tools, callbacks, state, and workflows. Use it when an agent project needs concrete API patterns or code examples. Claude Code CX Codex Cursor +1 511,400installs

Questions about workflow-init

How do I install workflow-init in Claude Code?

Run npx skills add vercel/workflow --skill workflow-init -a claude-code. The skill lands at ~/.claude/skills/workflow-init/SKILL.md.

What does workflow-init do?

It runs the first-time setup of Vercel Workflow SDK: detects the framework, fetches that framework's getting-started guide and follows it through to a verified run.

How is it different from `/workflow`?

/workflow is for ongoing work after installation and reads the versioned docs in node_modules/workflow/docs/. If workflow is already a dependency, workflow-init points you there.

Source text

SKILL.md · Apache-2.0
---
name: workflow-init
description: Install and configure Vercel Workflow SDK before it exists in node_modules. Use when the user asks to "install workflow", "set up workflow", "add durable workflows", "configure workflow sdk", or "init workflow" for Next.js, Express, Hono, Fastify, NestJS, Nitro, Nuxt, Astro, SvelteKit, or Vite.
metadata:
  author: Vercel Inc.
  version: '1.4'
---

# 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/`.

© Vercel Inc. · Apache-2.0 · vercel/workflow

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor