Agent skill · software engineering · jeremylongshore
notion-prod-checklist
Decide whether a Notion integration is ready for production from evidence across access, contracts, correctness, safety, and operations. Use when reviewing a launch or material change. Trigger with "review Notion production readiness", "Notion go-live checklist", or "approve Notion launch".
Why this skill is useful
Adds a comprehensive executable checklist for deploying Notion integrations, including specific tests and validations not covered in public documentation.
What it needs
Requires node 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 Production Readiness Review Overview Decide whether a Notion integration is ready for production from evidence across access, contracts, correctness, safety, and operations.. 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 Readiness covers selected API and SDK contracts, connection model, access, schema and object identities, pagination, limits, retries, idempotency, webhooks, data governance, observability, reconciliation, and rollback. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Verify production secret provenance, workspace binding, minimum capabilities, shared roots, rotation, revocation, and break-glass custody. Instructions 1. Bind the review to an immutable artifact, configuration digest, owners, environments, and change window. 2. Walk access, data, version, schema, operation, limit, retry, webhook, and destructive-action controls. 3. Run offline tests and approved non-production happy, denied, failure, restart, and rollback paths. 4. Verify dashboards, alerts, incident ownership, support escalation, queue controls, and reconciliation. 5. List open risks with explicit acceptance authority and expiry. 6. Issue GO, CONDITIONAL GO, or NO-GO with evidence and post-launch observation gates. 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-prod-checklist