Skip to content
Skills Library
Programming · Testing

notion-local-dev-loop

/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".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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".

Triggers from the description

develop Notion locallymock Notion APIset up Notion sandbox

Arguments

/notion-local-dev-loop <repository> <feature> <sandbox-workspace>
Original author description

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".

How it works

  1. Overview
  2. Prerequisites
  3. Current Contract
  4. Authentication
  5. Instructions
  6. Tool Discipline
  7. Approval Boundaries
  8. Error Handling
  9. Output
  10. Examples
Original SKILL.md headings · 68 lines, 440 words
SKILL.md preview
---
name: notion-local-dev-loop
description: >-
  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".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<repository> <feature> <sandbox-workspace>"
version: 1.41.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [saas, notion, development]
model: inherit
effort: high
compatibility: "Designed for Claude Code; live Notion actions require network access and explicit approval"
---
# 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.

## Approval Boundaries

Require the sandbox owner before any live call and explicit approval for writes, webhooks, file uploads, or destructive reset.

## Error Handling

- Do not record live responses as fixtures without classification and redaction.
- Do not make tests depend on search propagation timing.
- Fail if configuration points to a production connection or object.

## Output

Return the environment contract, fixture manifest, test commands, sandbox access map, live-check receipt, and cleanup status. Identify assumptions, owners, expirations, and evidence gaps explicitly.

## Examples

- Develop a data-source query entirely from synthetic multi-page fixtures.
- Exercise a page write in a sandbox and restore its original state.

## Validation

Exercise and record these paths with expected and observed results:

- production guard
- secret canary
- pagination
- unknown field
- retry
- sandbox cleanup

## Resources

- [Current first-party evidence map](references/official-docs.md) — recheck dated sources before relying on mutable behavior.
- Treat observed tenant behavior as environment-specific evidence, never a universal Notion guarantee.
Files in this package (2)
  • SKILL.md 4 KB
  • references/official-docs.md 2 KB

Versions

The database has no other skills named notion-local-dev-loop.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 4ca865d5ea8f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100onenote-local-dev-loop
    Create a repeatable local OneNote development loop using synthetic fixtures, mocks, and an explicitly approved delegated sandbox. Use when implementing or debugging without touching real notebooks. Trigger with "develop OneNote locally", "mock OneNote API", or "set up OneNote sandbox".
  • 100persona-local-dev-loop
    Run a deterministic local Persona sandbox loop with synthetic inquiries, raw webhook fixtures, and replay checks. Use when developing without production PII. Trigger with: "develop Persona locally", "test Persona webhook", "mock Persona flow".
  • 96notion
    Search, read, create and update pages and databases in your Notion workspace via the Notion API. Use when the user asks to find, read, or write Notion pages, notes, docs, or database rows.
  • 100notion-hub
    Read and write Notion data using Python + notion-client SDK. Authenticated via NOTION_API_KEY env var. Supports search, page CRUD (Markdown↔Blocks bidirectional conversion), database schema/query/create/add-row, block-level operations (append/update/delete), and comments.…
  • 100custom-blocks
    Create, modify, and troubleshoot custom blocks in Notion Workers. Use when the user wants to build interactive UI inside Notion connected to Notion data. Covers the author workflow from project setup to local preview and deployment.
  • 100notion
    Build integrations with the Notion API: databases and data sources, pages, blocks, search, and OAuth. Use when tasks involve reading or writing Notion workspace data, syncing external tools with a Notion database, building dashboards from Notion content, or automating page creation and updates.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.