Agent skill · data analytics · jeremylongshore
linear-observability
Instrument Linear API, SDK, webhook, queue, and reconciliation behavior with useful redacted signals. Use when defining service objectives, dashboards, alerts, or audit evidence. Trigger with "monitor Linear integration", "add Linear API metrics", or "observe Linear webhooks".
Why this skill is useful
Provides specific metrics collection and logging patterns for Linear API integrations that the AI wouldn't reliably generate on its own.
What it needs
Requires pino, prom-client installed locally. Requires linear account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Linear Integration Observability Overview Measure contract health and business freshness without placing tokens, GraphQL variables, issue content, or user identities in telemetry. Prerequisites The target repository, Linear workspace, environment, and accountable owner Current security, privacy, compliance, capacity, and change-control requirements An approved Linear credential only when a bounded live verification is necessary Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Linear documentation and package metadata. Use Write or Edit only for requested implementation with known target files. Never write credentials, customer content, unrestricted environment output, or unredacted GraphQL variables. Current Contract Linear returns request-limit, endpoint-limit, complexity, remaining-budget, and reset headers that can drive safe capacity telemetry. Webhook delivery headers include unique delivery ID, event type, signature, and timestamp; never log the signature as reusable evidence. Enterprise audit logs retain 90 days and can be queried or streamed, but are owner-only and contain sensitive actor/IP metadata. Authentication Use a personal API key only for owner-controlled scripts, OAuth with PKCE for user-delegated applications, or an enabled client-credentials grant for approved automation. Personal keys use Authorization: <APIKEY>; OAuth tokens use Authorization: Bearer <ACCESSTOKEN>. Store credentials server-side in an approved secret manager. Treat app approval, team access, scope changes, credential creation, rotation, revocation, and production access as owner-approved actions. Instructions 1. Define service objectives for API success, GraphQL application errors, webhook acknowledgement, queue lag, and reconciliation freshness. 2. Emit operation names, status, normalized error code, latency, retry count, and rate/complexity budget—not raw queries or variables. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-observability