Skip to content
Skills Library
Programming · Analysis

linear-common-errors

/linear-common-errors

Diagnose Linear GraphQL and SDK failures from transport, response, and request evidence. Use when an integration returns partial data, authentication failures, rate limits, invalid input, or missing resources. Trigger with "debug Linear GraphQL", "Linear API error", or "why did Linear SDK fail".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Diagnose Linear GraphQL and SDK failures from transport, response, and request evidence. Use when an integration returns partial data, authentication failures, rate limits, invalid input, or missing resources. Trigger with "debug Linear GraphQL", "Linear API error", or "why did Linear SDK fail".

Triggers from the description

debug Linear GraphQLLinear API errorwhy did Linear SDK fail

Arguments

/linear-common-errors [repository-path] [redacted-error-or-request-id]
Original author description

Diagnose Linear GraphQL and SDK failures from transport, response, and request evidence. Use when an integration returns partial data, authentication failures, rate limits, invalid input, or missing resources. Trigger with "debug Linear GraphQL", "Linear API error", or "why did Linear SDK fail".

How it works

  1. Overview
  2. Prerequisites
  3. Tool Discipline
  4. Current Contract
  5. Authentication
  6. Instructions
  7. Approval Boundaries
  8. Output
  9. Error Handling
  10. Examples
Original SKILL.md headings · 76 lines, 552 words
SKILL.md preview
---
name: linear-common-errors
description: >-
  Diagnose Linear GraphQL and SDK failures from transport, response, and request evidence. Use when an integration returns partial data, authentication failures, rate limits, invalid input, or missing resources. Trigger with "debug Linear GraphQL", "Linear API error", or "why did Linear SDK fail".
argument-hint: "[repository-path] [redacted-error-or-request-id]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.13.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
- saas
- linear
- error-triage
model: inherit
effort: high
compatibility: Designed for Claude Code; live verification requires network access and an approved Linear workspace credential
---
# Linear Error Triage

## Overview

Classify a failure before changing code or credentials, because Linear can return GraphQL errors with HTTP 200 and throttling errors with HTTP 400.

## 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

- Always inspect the GraphQL `errors` array; a response can include partial `data` and errors together.
- Rate limiting is identified by `extensions.code: RATELIMITED` in an HTTP 400 GraphQL response, not by assuming HTTP 429.
- The SDK exposes parsed `LinearError` details including query, variables, status, data, raw error, and per-error path/type when available.

## 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. Capture the operation name, HTTP status, GraphQL error code/path, SDK version, and redacted rate headers.
2. Separate authentication, authorization, input, not-found, complexity, endpoint-budget, and service-health failures.
3. Reproduce with the smallest read-only query using the same auth mode; do not paste tokens or full customer variables.
4. For partial data, decide whether the caller must reject the whole response or can use explicitly safe fields.
5. For throttling, follow reset metadata, shrink requested fields/pages, and coordinate all workers sharing the user or app budget.
6. Return the root-cause evidence, bounded remediation, and a regression assertion.

## 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 |
|---|---|
| HTTP 200 plus `errors` | Treat it as an application failure unless partial-data handling is explicitly designed. |
| HTTP 400 plus `RATELIMITED` | Honor reset data and reduce request or complexity pressure. |
| Forbidden | Verify team visibility and exact OAuth scope; do not broaden access by default. |
| Unknown schema field | Check introspection, SDK version, and deprecation notices before renaming code. |

## Examples

Use a compact handoff that makes scope, mutation authority, and verification evidence reviewable.

Input:

```text
status=200; errors[0].path=issueCreate; sdk=95.0.0; variables=redacted
```

Expected handoff:

```text
class=graphql-application-error; retry=no; regression=payload-error-check
```

## 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)
Files in this package (2)
  • SKILL.md 5 KB
  • references/official-docs.md 3 KB

Versions

RepositoryScoreLicence
This page · jeremylongshore/tons-of-skills-marketplace100MIT
HelixDevelopment/agent100MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version ccae3d3dfdc7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100linear-sdk-patterns
    Implement current Linear TypeScript SDK query, mutation, pagination, raw GraphQL, and error-handling patterns. Use when building or refactoring a typed Linear adapter. Trigger with "use Linear SDK", "refactor Linear client", or "write typed Linear GraphQL".
  • 100fireflies-common-errors
    Diagnose Fireflies transport, GraphQL, permission, plan, processing, and operation-limit failures without unsafe retries or data probing. Use when an integration fails or returns partial data. Trigger with "Fireflies error", "too_many_requests", or "object_not_found Fireflies".
  • 100linear-install-auth
    Install and configure Linear SDK/CLI authentication. Use when setting up a new Linear integration, configuring API keys, or initializing Linear in your project. Trigger with phrases like "install linear", "setup linear", "linear auth", "configure linear API key", "linear SDK setup".
  • 100linear-rate-limits
    Handle Linear API rate limiting and quotas effectively. Use when dealing with rate limit errors, implementing throttling, or optimizing API usage patterns. Trigger with phrases like "linear rate limit", "linear throttling", "linear API quota", "linear 429 error", "linear request limits".
  • 90Linear GraphQL Patterns
    This skill should be used when writing or reviewing GraphQL queries against the Linear API — selecting fragments, navigating connection types, batching, and avoiding deprecated fields. Activates on "linear graphql", "linear query", "linear api", "linear schema".
  • 90Linear SDK Usage
    This skill should be used when implementing Linear integrations using the official @linear/sdk — creating issues programmatically, advanced fetch/modify patterns, error handling, and type safety. Activates on "linear sdk", "@linear/sdk", "linear client", "linear typescript".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.