Agent skill · software engineering · jeremylongshore
notion-ci-integration
Build CI checks for Notion integration contracts without exposing tokens or mutating production content. Use when gating SDK, schema, fixture, or migration changes. Trigger with "test Notion in CI", "gate Notion schema drift", or "add Notion contract checks".
Why this skill is useful
Adds executable scripts for integrating Notion API with CI/CD pipelines, enabling automated documentation and deploy tracking.
What it needs
Requires node, python3 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 Contract-Safe CI Integration Overview Build CI checks for Notion integration contracts without exposing tokens or mutating production content.. 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 CI should validate local contracts by default. Any live smoke test needs a dedicated non-production connection, explicitly shared fixture content, bounded reads, and a pinned tested API version. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Use short-lived CI secret delivery where supported and a least-privilege non-production token. Mask values and prevent fork jobs from receiving secrets. Instructions 1. Define offline unit, schema, pagination, error, webhook-signature, and migration fixtures. 2. Pin the SDK and tested API version in the dependency and contract matrix. 3. Separate secret-free pull-request jobs from trusted-branch live smoke tests. 4. Make the live lane read-only, fixture-scoped, time-bounded, and concurrency-limited. 5. Capture redacted status, error code, and request identifier without response content. 6. Gate promotion on exact fixtures, negative paths, rollback evidence, and named ownership. 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-ci-integration--ee60de