Agent skill · software engineering · jeremylongshore
notion-reliability-patterns
Analyze and apply retry, idempotency, checkpoint, circuit, dead-letter, and reconciliation patterns to a specific Notion operation. Use when hardening failure recovery. Trigger with "harden Notion reliability", "make Notion writes idempotent", or "design Notion recovery".
Why this skill is useful
Adds executable patterns for fault-tolerant Notion integrations, including retry logic, circuit breakers, and caching mechanisms.
What it needs
Requires @notionhq/client, lru-cache, 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 Reliability Pattern Selection Overview Analyze and apply retry, idempotency, checkpoint, circuit, dead-letter, and reconciliation patterns to a specific Notion operation.. 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 Reliability behavior depends on whether an operation is a read, create, update, webhook signal, paginated extraction, file lifecycle, or downstream side effect. Retry safety cannot be inferred from HTTP method alone. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Recovery stores and dead letters must protect workspace content and tenant identifiers to the same standard as the primary system. Instructions 1. Define success, acknowledgement, idempotency identity, checkpoint, timeout ambiguity, and compensation for the operation. 2. Classify permanent, transient, rate, conflict, access, and unknown failures. 3. Select bounded retry, idempotency record, lease, circuit, dead letter, or reconciliation only where its invariant is explicit. 4. Persist response identity before acknowledging creates and destination state before advancing read checkpoints. 5. Exercise duplicate, reorder, timeout, crash, poison item, and partial downstream failure. 6. Document operator recovery, replay authorization, observability, and 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/notion-reliability-patterns--5a39b4