Agent skill · data analytics · jeremylongshore
notion-data-handling
Define data classification, minimization, retention, and deletion controls for a Notion integration. Use when workspace content or user data crosses a system boundary. Trigger with "govern Notion data", "review Notion PII", or "design Notion retention".
Why this skill is useful
Provides specific implementations for PII detection and GDPR/CCPA compliance workflows that the AI wouldn't generate reliably 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 Data Handling and Privacy Control Overview Define data classification, minimization, retention, and deletion controls for a Notion integration.. 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 Notion page content, properties, comments, user objects, files, logs, and webhook metadata have different sensitivity and lifecycle characteristics. Connection capabilities and content sharing bound access but do not replace application governance. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Minimize content and user capabilities, separate tenants, and prohibit credentials or raw sensitive content in logs and fixtures. Instructions 1. Map collection, purpose, lawful basis, classification, owner, processor, destination, and retention for every field class. 2. Minimize requested capabilities, selected properties, page bodies, user fields, and webhook subscriptions. 3. Define encryption, tenant isolation, logging, backup, export, correction, deletion, and legal-hold behavior. 4. Represent Notion trash, application deletion, destination deletion, and retained audit evidence as separate states. 5. Exercise subject and owner workflows on synthetic records before production. 6. Record residual risk, exceptions, expiry dates, and review owners. 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-data-handling--9e5323