Agent skill · software engineering · jeremylongshore
notion-multi-env-setup
Define isolated development, staging, and production Notion connections, secrets, content roots, and promotion rules. Use when an integration spans multiple environments. Trigger with "separate Notion environments", "configure Notion staging", or "audit Notion env isolation".
Why this skill is useful
Provides specific commands and patterns for managing Notion integrations across multiple environments 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 Multi-Environment Isolation Overview Define isolated development, staging, and production Notion connections, secrets, content roots, and promotion rules.. 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 has no universal environment abstraction for integrations. Isolation comes from distinct connections or tokens, workspace/content boundaries, secrets, destinations, queues, webhooks, and application guards. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Provision unique secret references and fingerprints per environment. Never fall back from a missing non-production secret to production. Instructions 1. Inventory each environment's workspace, connection, owner, capabilities, shared roots, webhook, queue, and destination. 2. Define immutable environment identifiers and fail-closed startup assertions. 3. Separate secrets, object IDs, callback URLs, encryption keys, and telemetry labels. 4. Use synthetic fixtures outside production and prevent configuration fallbacks. 5. Promote code artifacts independently from credentials and content configuration. 6. Run cross-environment leak tests and record rotation, teardown, and break-glass 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. 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-multi-env-setup