Agent skill · software engineering · jeremylongshore
notion-local-dev-loop
Create a repeatable local Notion development loop using fixtures, mocks, and an explicitly shared sandbox. Use when implementing or debugging without touching production content. Trigger with "develop Notion locally", "mock Notion API", or "set up Notion sandbox".
Why this skill is useful
Adds specific commands and configurations for setting up a Notion development environment that the AI wouldn't reliably generate on its own.
What it needs
Requires node, npm, pnpm 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 Isolated Local Development Loop Overview Create a repeatable local Notion development loop using fixtures, mocks, and an explicitly shared sandbox.. 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 Local tests should model the selected API version, pagination, errors, additive fields, data-source identities, and current write semantics. A sandbox smoke test complements but does not replace deterministic fixtures. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Use a dedicated sandbox connection and secret store reference. Never copy production tokens, page IDs, exports, or response bodies into fixtures. Instructions 1. Pin the SDK, selected API version, runtime, and fixture schema. 2. Create synthetic page, data-source, block, webhook, limit, and error fixtures with secret canaries. 3. Wrap the client behind an operation boundary that records status and request IDs without content. 4. Implement offline unit and contract tests before a live sandbox check. 5. Run one bounded read and, only when approved, one reversible sandbox write. 6. Reset fixtures, verify no production identifiers entered the workspace, and preserve test evidence. 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-local-dev-loop