Agent skill · data analytics · jeremylongshore
notion-observability
Design content-safe metrics, logs, traces, alerts, and reconciliation signals for a Notion integration. Use when making operations diagnosable without leaking workspace data. Trigger with "instrument Notion integration", "monitor Notion sync", or "design Notion alerts".
Why this skill is useful
Adds domain-specific knowledge for monitoring Notion API calls with structured logging and metrics that the AI wouldn't reliably generate on its own.
What it needs
Requires @notionhq/client, notion-client, pino installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Notion Integration Observability Contract Overview Design content-safe metrics, logs, traces, alerts, and reconciliation signals for a Notion integration.. 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 Operational signals should distinguish operation class, status, structured code, request ID, latency, retry, queue age, cursor age, and reconciliation delta. Page IDs, titles, content, user data, tokens, and signed URLs are unsafe default labels. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Telemetry pipelines receive no bearer or verification tokens. Use tenant aliases and bounded fingerprints approved for the monitoring boundary. Instructions 1. Define service, freshness, correctness, and security objectives with owners. 2. Create a low-cardinality operation taxonomy covering reads, writes, webhooks, queues, files, and reconciliation. 3. Specify redaction before serialization and sampling after security events are preserved. 4. Correlate attempts with internal operation IDs and vendor request IDs without content. 5. Alert on sustained error class, Retry-After pressure, queue age, cursor staleness, and reconciliation drift. 6. Exercise dashboards and alerts with synthetic failures and document response 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-observability