---
name: notion-content-management
description: >-
  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".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<content-scope> <change-intent> <environment>"
version: 1.41.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [ saas, notion, content ]
model: inherit
effort: high
compatibility: "Designed for Claude Code; live Notion actions require network access and explicit approval"
title: notion-content-management
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/notion-content-management
last_updated: 2026-10-23T06:01:00.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/notion-content-management/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/notion-content-management`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/notion-content-management`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/notion-content-management) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/notion-content-management`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/notion-content-management --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/notion-content-management --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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.

## Approval Boundaries

Require content-owner approval for every write; require separate approval for replacement, move, trash, file upload, broad descendant access, or public sharing.

## Error Handling

- Never replace an entire page when a bounded block or property update is sufficient.
- Do not reuse expiring download URLs as durable file identifiers.
- Stop on concurrent edits or an unexpected parent.

## Output

Return the content manifest, semantic diff, approvals, applied IDs, read-back evidence, conflicts, and rollback package. Identify assumptions, owners, expirations, and evidence gaps explicitly.

## Examples

- Append an approved section at the end of a page and verify its blocks.
- Trash a duplicate only after preserving its parent and restoration evidence.

## Validation

Exercise and record these paths with expected and observed results:

- preview exactness
- unsupported blocks
- position semantics
- file completion
- concurrent edit
- restore path

## Resources

- [Current first-party evidence map](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/notion-content-management/references/official-docs.md) — recheck dated sources before relying on mutable behavior.
- Treat observed tenant behavior as environment-specific evidence, never a universal Notion guarantee.
