linear-observability — Claude Code skill: what it does, how to install
linear-observability collects metrics and alerts around a Linear integration: API calls, webhooks, queue, reconciliation. Tokens and issue text stay out of telemetry.
MIT 1 installs ★ 2,935 updated 2026-10-29
npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-observability -a claude-codeWhat linear-observability does
The skill lays out observability for a Linear integration: API success, GraphQL errors, webhook acknowledgement, queue lag, reconciliation freshness. It walks through six steps, from service objectives to the fields you emit, then alerts and dashboard tests with synthetic failures. File access goes through Read, Glob, Grep, Write and Edit; WebFetch is limited to Linear's own docs and package metadata.
Signals stay narrow: operation name, status, normalised error code, latency, retry count, remaining rate and complexity budget. Webhook telemetry covers hashed delivery IDs, event type, signature check result, ack latency and dedupe outcome. Tokens, GraphQL variables, issue text and user identities never reach the pipeline. When a rate-limit header is missing, the metric is marked unknown instead of guessed.
Live verification needs network access plus an approved Linear workspace credential, so without one the skill stays on reading code. A personal key goes in Authorization: <API_KEY> for owner-run scripts; user-delegated apps use OAuth with PKCE and Authorization: Bearer <ACCESS_TOKEN>. Creating, rotating or revoking keys, changing scopes and re-enabling webhooks all wait for the accountable owner's approval. Enterprise audit logs keep 90 days of data and stay owner-only, and the skill tells you not to route around that with scraped UI exports.
What it helps with
- add API metrics without leaking tokens into telemetry
- alert on webhook acknowledgement and queue lag
- check reconciliation freshness between Linear and your service
- write service objectives and tie them to runbooks
- produce audit evidence with sensitive fields scrubbed
Example prompts for the agent
- Instrument the Linear API calls in
services/syncwith operation name, status, error code and latency. - Add alerts for webhook signature failures and queue age.
- Audit which fields reach telemetry and strip GraphQL variables.
How to install linear-observability
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-observability -a claude-code2Manually: put the files in place
~/.claude/skills/linear-observability/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/linear-observability/
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-observability -a codex2Manually: put the files in place
.agents/skills/linear-observability/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-observability -a cursor2Manually: put the files in place
.cursor/skills/linear-observability/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jeremylongshore/tons-of-skills-marketplace skills/.curated/linear-observability2Manually: put the files in place
.github/skills/linear-observability/SKILL.md1Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-observability -a gemini-cli2Platform CLI
gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace --path skills/.curated/linear-observabilityManually: put the files in place
.devin/skills/linear-observability/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-observability -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about linear-observability
How do I install linear-observability in Claude Code?
Run npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-observability -a claude-code. The skill file lands at ~/.claude/skills/linear-observability/SKILL.md.
What does linear-observability do?
It turns Linear integration observability into six steps: service objectives, emitted fields, webhook signals, alerts, audit-log handling and dashboard tests with synthetic failures.
What do I need before a live check?
Network access and an approved Linear workspace credential. Without the credential the skill works from the repository code and configuration only.
Source text
SKILL.md · MIT
--- name: linear-observability description: >- 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". argument-hint: "[repository-path] [metrics|logs|traces|alerts]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.13.0 author: Jeremy Longshore <[email protected]> license: MIT tags: - saas - linear - observability model: inherit effort: high compatibility: Designed for Claude Code; live verification requires network access and an approved Linear workspace credential --- # 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: <API_KEY>`; OAuth tokens use `Authorization: Bearer <ACCESS_TOKEN>`. 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. Track webhook delivery ID hashes, event type, verification result, acknowledgement latency, dedupe outcome, and processing lag. 4. Alert on sustained budget exhaustion, auth failures, signature failures, queue age, and reconciliation divergence. 5. Keep audit-log ingestion separate, least-privileged, redacted, and aligned with the organization's retention policy. 6. Test dashboards and alerts with synthetic failures and record owner, runbook, and quieting rules. ## Approval Boundaries Do not create, reveal, rotate, or revoke credentials; authorize an OAuth app; change scopes or team access; create, mutate, archive, or delete workspace data; configure or re-enable webhooks; import or export data; change roles, SCIM, or audit streaming; transmit diagnostics; change paid entitlements; or perform another production mutation without explicit approval from the accountable owner. Keep diagnosis read-only unless implementation was requested. ## Output Return the workspace and team scope, auth mode without credential value, files and contracts inspected, exact operation names, evidence collected, validation result, sensitive fields redacted, remaining risk, accountable owner, approval state, and rollback or next action. ## Error Handling | Condition | Response | |---|---| | Sensitive telemetry | Drop and scrub the field before expanding observability. | | Header absent | Mark the metric unknown; do not fabricate a full budget. | | Alert storm | Aggregate by workspace/operation and preserve the first actionable evidence. | | Audit access denied | Confirm Enterprise owner authority; do not work around it with scraped UI data. | ## Examples Use a compact handoff that makes scope, mutation authority, and verification evidence reviewable. Input: ```text slo=webhook-ack<5s; dimensions=workspace-hash,operation; payload-logging=false ``` Expected handoff: ```text metrics=bounded; alerts=runbook-linked; content=excluded ``` ## Resources - [Skill-specific official documentation](references/official-docs.md) - [Linear developer documentation index](https://linear.app/llms.txt) - [Linear GraphQL API](https://linear.app/developers/graphql.md)
© Jeremy Longshore · MIT · jeremylongshore/tons-of-skills-marketplace