Skip to main content
skill CX Codex

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

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

What 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.example without 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 check on the workflow file you just created.

How to install workflow

1Skills CLI (Vercel)

npx skills add makenotion/notion-cookbook --skill workflow -a claude-code

2Manually: put the files in place

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

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

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.

workflow Vercel Inc. Builds durable, resumable tasks with the Vercel Workflow SDK when operations must survive server restarts or pause for external events. CX Codex +1 5,500installs workflow makenotion Build or review Notion App workflows with typed triggers, replay-safe steps, and idempotent effects. The skill requires reading the SDK guide before workflow code changes. CX Codex +1 ★ 232repo stars notion-automation claude-office-skills notion-automation automates Notion databases and page templates with cross-platform triggers. Useful for handling leads, task digests, and calendar events. CX Codex +1 5,000installs notion-api intellectronica A skill for interacting with the Notion API through REST requests. Gives agents full access to pages, databases, blocks, and comments — read, create, update, and delete content. CX Codex +1 106,200installs notion acedatacloud This skill connects Claude Code to Notion’s REST API for workspace search, page editing, database queries, and new page creation. CX Codex +1 215installs connect-apps Composio connect-apps — a plugin for Claude Code that connects to 500+ services: Gmail, Slack, GitHub, Notion, and more. Perform actions directly from code — send emails, create tasks, post messages. ★ 2,003repo stars notion-sdk terrylica notion-sdk — a skill for managing Notion via the official Python SDK. Creates pages and databases, queries information, adds content blocks — all programmatically. CX Codex +1 133installs notion-webhooks hookdeck notion-webhooks generates Notion webhook handlers, verifies HMAC-SHA256 signatures, and handles the initial handshake token. CX Codex +1 121installs

From the same set17

The whole set →
workflow-validate workflow-validate walks through src/workflows/ and flags trigger typing mistakes and retry hazards. Useful before a workflow ships. CX Codex +1 ★ 232repo stars workflow-guide workflow-guide is a Claude Code skill that guides agents writing durable Notion workflows with isolated steps, idempotency, and replay-safe data. CX Codex +1 ★ 232repo stars sync This skill guides the design of a new Notion Worker sync and writes the implementation. Use it when an API needs a clear mode, schema, and pagination state. CX Codex +1 ★ 232repo stars sync-validate sync-validate is a Claude Code skill that reviews sync code for cursor, pagination, state, and deletion bugs. Run it to inspect a sync capability. CX Codex +1 ★ 232repo stars sync-guide sync-guide instructs coding assistants on building Notion Workers syncs, including replace mode, backfill-delta architectures, pagination, and cursor buffers. CX Codex +1 ★ 232repo stars sync-debug sync-debug — a skill for Claude Code and other AI agents that walks through a failing or misbehaving Notion sync: pulls run logs, finds the error, and checks it against the code. CX Codex +1 ★ 232repo stars custom-blocks custom-blocks walks you through building an interactive UI inside Notion that reads and writes workspace data. CX Codex +1 ★ 232repo stars auth-guide auth-guide configures third-party authentication for Notion Workers using brokered credentials, OAuth, or environment secrets. Needed when connecting a worker to APIs like GitHub or Stripe. CX Codex +1 ★ 232repo stars

Project sponsors

Companies that keep this analytics open