Agent skill · marketing growth · jeremylongshore
notion-policy-guardrails
Turn Notion security, privacy, access, version, and mutation rules into enforceable repository and runtime gates. Use when defining policy-as-code for integrations. Trigger with "add Notion guardrails", "enforce Notion policy", or "review Notion controls".
Why this skill is useful
Adds specific governance scripts and naming conventions for Notion integrations that the AI wouldn't reliably generate on its own.
What it needs
Requires @notionhq/client, notion-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 Integration Policy Guardrails Overview Turn Notion security, privacy, access, version, and mutation rules into enforceable repository and runtime gates.. 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 Useful guardrails cover secret handling, tested versions, object-type correctness, pagination, retries, capabilities, content sharing, tenant binding, webhook verification, destructive actions, and evidence retention. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Policy checks may inspect secret names and fingerprints but never values. Runtime checks must bind a credential to its expected workspace and environment. Instructions 1. Translate each policy statement into owner, scope, machine check, human gate, evidence, and exception expiry. 2. Add static checks for credentials, legacy object operations, unsafe logging, unbounded retries, and missing approvals. 3. Add tests for page/data-source identity, pagination, webhook signatures, idempotency, and tenant isolation. 4. Add runtime guards for environment, write scope, concurrency, payload size, and destructive operations. 5. Define signed, time-bounded exceptions with compensating controls. 6. Exercise allow, deny, bypass-expired, and rollback paths before enforcing the gate. Tool Discipline Use Read, Glob, and Grep to inspect documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/notion-policy-guardrails