Agent skill · software engineering · jeremylongshore
notion-core-workflow-b
Create or update Notion pages and blocks with an idempotency key, semantic diff, and read-back verification. Use when an integration must write approved content. Trigger with "create Notion record", "update Notion page", or "append Notion blocks".
Why this skill is useful
Adds specific commands and patterns for managing Notion blocks and rich text that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. Requires notion account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Notion Idempotent Page Write Workflow Overview Create or update Notion pages and blocks with an idempotency key, semantic diff, and read-back verification.. This workflow produces an auditable decision or artifact before any live action. Prerequisites Current first-party Notion documentation and the selected integration's tested API-version contract. A named workspace owner, content or data owner, and operation owner. Synthetic or approved non-production fixtures with secrets and workspace content removed. Current Contract Page properties follow the parent data source schema; page body content is a block tree or enhanced markdown. Current placement and trash semantics depend on the pinned API contract. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Use only insert or update content capability required by the operation. Confirm parent access and keep lookup identities separate from write identities when risk warrants. Instructions 1. Resolve the exact parent, page, data source, and current revision. 2. Derive an idempotency key from the business object and operation version. 3. Render a semantic diff for properties, blocks, parent, and trash state. 4. Validate property types, relation targets, size limits, and block nesting offline. 5. Apply one approved mutation and persist the returned object ID before downstream work. 6. Read back the object, compare intended state, and retain compensation instructions. Tool Discipline Use Read, Glob, and Grep to inspect documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, workspace content, user data, file transfer, deployment, capability or sharing changes, writes, spend, or deletion. Approval Boundaries Require the content owner before insert, update, move, append, replacement, comment creation, or trash operations. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/notion-core-workflow-b