awfixers-stuff/workflow-init
skills/workflow-init/SKILL.md
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.
development
Updated Apr 27, 2026
$ install --global
skillsauthnpx skillsauth add awfixers-stuff/opencode-config workflow-initInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 2:47 AM57.0s1 file scanned
SKILL.md
- 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.
- author:
- Vercel Inc.
- version:
- 1.1
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:
- Next.js -
nextdep ornext.config.* - Nuxt -
nuxtdep ornuxt.config.* - SvelteKit -
@sveltejs/kitdep orsvelte.config.* - Astro -
astrodep orastro.config.* - NestJS -
@nestjs/coredep ornest-cli.json - Nitro -
nitrodep ornitro.config.* - Express -
expressdep - Fastify -
fastifydep - Hono -
honodep - Vite -
vitedep (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://useworkflow.dev/docs/getting-started/next | | Express | https://useworkflow.dev/docs/getting-started/express | | Hono | https://useworkflow.dev/docs/getting-started/hono | | Fastify | https://useworkflow.dev/docs/getting-started/fastify | | NestJS | https://useworkflow.dev/docs/getting-started/nestjs | | Nitro | https://useworkflow.dev/docs/getting-started/nitro | | Nuxt | https://useworkflow.dev/docs/getting-started/nuxt | | Astro | https://useworkflow.dev/docs/getting-started/astro | | SvelteKit | https://useworkflow.dev/docs/getting-started/sveltekit | | Vite | https://useworkflow.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://useworkflow.dev/docs/foundations/workflows-and-steps
- https://useworkflow.dev/docs/foundations/common-patterns
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
awfixers-stuff/zmx
development
VerifiedTrustedCommunity
Use when starting dev servers, watchers, tilt, or any process expected to outlive the conversation. Provides zmx session management patterns for long-lived processes.
SKILL.mdUpdated Apr 27, 2026
awfixers-stuff/zig-testing
development
VerifiedTrustedCommunity
Zig testing skill for writing and running tests. Use when using zig build test, writing comptime tests, using test filters, working with test allocators to detect leaks, or using Zig's built-in fuzz testing (0.14+). Activates on queries about Zig tests, zig test, zig build test, comptime testing, test allocators, Zig fuzz testing, or detecting memory leaks in Zig tests.
SKILL.mdUpdated Apr 27, 2026
awfixers-stuff/zig-debugging
development
VerifiedTrustedCommunity
Zig debugging skill. Use when debugging Zig programs with GDB or LLDB, interpreting Zig runtime panics, using std.debug.print for tracing, configuring debug builds, or debugging Zig programs in VS Code. Activates on queries about debugging Zig, Zig panics, zig gdb, zig lldb, std.debug.print, Zig stack traces, or Zig error return traces.
SKILL.mdUpdated Apr 27, 2026
awfixers-stuff/zig-cross
tools
VerifiedTrustedCommunity
Zig cross-compilation skill. Use when cross-compiling Zig programs to different targets, using Zig's built-in cross-compilation for embedded, WASM, Windows, ARM, or using zig cc to cross-compile C code without a system cross-toolchain. Activates on queries about Zig cross-compilation, zig target triples, zig cc cross-compile, Zig embedded targets, or Zig WASM.
SKILL.mdUpdated Apr 27, 2026