workflow · makenotion, workers — Claude Code skill: what it does, how to install
Adds a Workflow to a Notion Worker template: picks the trigger, splits work into replay-safe steps and writes a file to src/workflows/. Handy when a new triggered scenario appears.
MIT ★ 232 updated 2026-10-25
npx skills add makenotion/notion-cookbook --skill workflow -a claude-codeWhat workflow does
The skill adds a Workflow to a Notion Worker template. It reads AGENTS.md plus whatever already sits in src/workflows/, inspects the declared triggers, then settles on the trigger, the outcome and where each step begins and ends. Output is a single camelCase file placed directly in src/workflows/.
Code goes through a default createWorkflow(...) export built from typed trigger creators. Anything non-deterministic belongs in an awaited context.step(...) call, which is what lets a run survive a replay. Steps carry a constant display name, and repeated steps take a stable composite key such as { key: ["process-page", page.id] }. Steps hand back JSON-safe values only, while the step id doubles as an idempotency key where the platform supports one.
Credentials stay out of the scaffold. When configuration is required, .env.example gets variable names and safe placeholders, nothing more. At the end the skill runs npm run check and npm run build.
What it helps with
- scaffold a Workflow inside a Notion Worker template
- split non-deterministic work into steps that survive a replay
- settle trigger, outcome and step boundaries before writing code
- keep repeated steps idempotent with a composite
key - fill
.env.examplewithout leaking credentials
Example prompts for the agent
- /workflow Add a workflow to this template: trigger on a new page, then a step that calls the API.
- Break the non-deterministic parts into awaited
context.step(...)calls with stable names. - Run
npm run checkon the workflow file you just created.
How to install workflow
1Skills CLI (Vercel)
npx skills add makenotion/notion-cookbook --skill workflow -a claude-code2Manually: put the files in place
~/.claude/skills/workflow/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/workflow/
1Skills CLI (Vercel)
npx skills add makenotion/notion-cookbook --skill workflow -a codex2Manually: put the files in place
.agents/skills/workflow/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add makenotion/notion-cookbook --skill workflow -a cursor2Manually: put the files in place
.cursor/skills/workflow/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install makenotion/notion-cookbook workers/agents/skills/workflow2Manually: put the files in place
.github/skills/workflow/SKILL.md1Skills CLI (Vercel)
npx skills add makenotion/notion-cookbook --skill workflow -a gemini-cli2Platform CLI
gemini skills install https://github.com/makenotion/notion-cookbook --path workers/agents/skills/workflowManually: put the files in place
.devin/skills/workflow/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add makenotion/notion-cookbook --skill workflow -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about workflow
How do I install the workflow skill in Claude Code?
Run npx skills add makenotion/notion-cookbook --skill workflow -a claude-code. The skill lands at ~/.claude/skills/workflow/SKILL.md.
What does the workflow skill do?
It scaffolds a Workflow inside a Notion Worker template: reads AGENTS.md, chooses the trigger and step boundaries, writes one camelCase file to src/workflows/ and checks the build.
Why do repeated steps need a shared key?
The display name stays constant across repeats, so a composite key such as { key: ["process-page", page.id] } keeps them apart. Where supported, the step id serves as the idempotency key.
Source text
SKILL.md · MIT
---
name: workflow
description: Scaffold a Notion Worker Workflow with typed triggers and replay-safe durable steps.
user-invocable: true
disable-model-invocation: true
---
# Workflow
Use this skill to add a Workflow to this template.
1. Read `AGENTS.md` and the existing files in `src/workflows/`.
2. Inspect the installed Workflow and trigger declarations.
3. Choose the trigger, outcome, step boundaries, and required configuration.
4. Create one camelCase file directly in `src/workflows/`.
5. Default-export `createWorkflow(...)` and use typed trigger creators.
6. Put all non-deterministic work in awaited `context.step(...)` calls.
7. Give each step a stable display name. For repeated steps, keep the name
constant and pass a stable, unique composite `key`, such as
`{ key: ["process-page", page.id] }`.
8. Return JSON-safe values needed by later steps.
9. Use the step `id` as an idempotency key when supported.
10. Run `npm run check` and `npm run build`.
Do not write credentials. Add only environment variable names and safe
placeholders to `.env.example` when configuration is required.
© makenotion · MIT · makenotion/notion-cookbook
Similar skills
All skills for Agent setup: memory, context, orchestration →workflow by other authors comes first.