Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/notion-content-management

@820dfc8
Run it yourself

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

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/notion-content-management

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈73 tokens for metadata: the name and description. ≈808 when used: this file. ≈551 more on demand in 1 file.

Description uses 3.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈294 characters, or 3.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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 — recheck dated sources before relying on mutable behavior.
  • Treat observed tenant behavior as environment-specific evidence, never a universal Notion guarantee.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides comprehensive documentation and code examples for managing Notion content through official SDKs. It is assigned a low-risk verdict due to the inherent indirect prompt injection attack surface that exists when an agent processes user-provided data into Notion pages.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month
What it can do
Reads files Edits files
Modelinherit
argument-hint
<content-scope> <change-intent> <environment>
version
1.41.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "notion",
  "content"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; live Notion actions require network access and explicit approval

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/notion-content-management