Agent skill · data analytics · jeremylongshore
notion-advanced-troubleshooting
Diagnose difficult Notion integration failures from redacted evidence without trial-and-error writes. Use when ordinary error handling has not isolated the fault. Trigger with "trace Notion failure", "analyze Notion request ID", or "debug Notion permissions".
Why this skill is useful
Provides specific debugging techniques and scripts for handling Notion API issues that the AI wouldn't reliably generate on its own.
What it needs
Requires @notionhq/client, curl, 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 Evidence-First Advanced Troubleshooting Overview Diagnose difficult Notion integration failures from redacted evidence without trial-and-error writes.. 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 Treat the HTTP status, Notion error code, request identifier, selected API version, object type, and connection access graph as separate evidence. A page, database, and data source ID are not interchangeable. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Use a redacted credential fingerprint only. Confirm connection type, token owner, capabilities, shared content, and environment; never copy a bearer token into a bundle. Instructions 1. Freeze retries and preserve one representative response with its request identifier. 2. Reconstruct the request method, object type, selected version, payload shape, and target environment. 3. Trace effective access from token owner through capabilities and explicitly shared content. 4. Classify the fault as transport, authentication, authorization, object identity, version shape, limit, conflict, or service failure. 5. Reproduce with a read-only metadata request or fixture before proposing any write. 6. Return the smallest corrective change, rollback, and escalation 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-advanced-troubleshooting