Agent skill · software engineering · jeremylongshore
notion-content-management
Plan and verify safe Notion page, block, markdown, and file-content changes with previews and rollback evidence. Use when creating, updating, moving, or trashing workspace content. Trigger with "edit Notion content", "publish Notion page", or "manage Notion blocks".
Why this skill is useful
Provides specific commands and patterns for managing Notion pages and blocks that the AI wouldn't reliably generate on its own.
What it needs
Requires @notionhq/client 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 Content Change Control Overview Plan and verify safe Notion page, block, markdown, and file-content changes with previews and rollback evidence.. 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 Current content operations distinguish pages, blocks, databases, and data sources. Block placement uses the current position object; current REST trash state and enhanced-markdown behavior must come from the selected version contract. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Use a connection with only the content capabilities needed for the approved scope. Confirm the exact parent and content-sharing path before any mutation. Instructions 1. Resolve stable IDs and capture a pre-change snapshot, revision marker, and content owner. 2. Choose page properties, block operations, enhanced markdown, or file uploads based on the documented object contract. 3. Build a semantic preview showing creates, replacements, moves, and trash actions. 4. Validate payload size, nesting, unsupported blocks, file lifecycle, and version shape offline. 5. Apply the smallest approved change with idempotency and conflict detection. 6. Read back the changed scope and preserve rollback material until acceptance. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/notion-content-management