Agent skill · software engineering · jeremylongshore
notion-deploy-integration
Prepare and verify a Notion integration deployment with environment isolation, secret provenance, staged rollout, and rollback. Use when promoting an integration runtime. Trigger with "deploy Notion integration", "promote Notion worker", or "review Notion release".
Why this skill is useful
Provides specific deployment patterns and environment variable management for Notion-integrated Node.js applications that the AI wouldn't reliably generate on its own.
What it needs
Requires fly, node, railway, vercel 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 Deployment Control Overview Prepare and verify a Notion integration deployment with environment isolation, secret provenance, staged rollout, and rollback.. 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 Deployment readiness depends on the tested SDK and API contract, connection configuration, shared fixture content, worker or queue topology, and rollback compatibility; a successful build is not a production acceptance test. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Bind each environment to distinct secret references and Notion connections. Never copy development tokens into production or expose secrets to preview builds. Instructions 1. Pin the artifact digest, dependency lock, selected API version, schema assumptions, and migration order. 2. Verify environment-specific connection, content access, webhook destination, queue, and observability bindings. 3. Run offline contract tests and a non-production read-only smoke test. 4. Produce a rollout plan with canary scope, concurrency, retry, write, and reconciliation guards. 5. Deploy only through the approved platform workflow and observe defined health signals. 6. Reconcile output and either promote or execute the tested rollback. 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-deploy-integration--14967b