Skip to content
Skills Library
Programming · Planning

linear-reference-architecture

/linear-reference-architecture

Design a Linear integration with separated auth, GraphQL, webhook, queue, policy, and reconciliation boundaries. Use when reviewing or creating a durable service architecture. Trigger with "design Linear integration", "architect Linear webhook service", or "review Linear system design".

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

Design a Linear integration with separated auth, GraphQL, webhook, queue, policy, and reconciliation boundaries. Use when reviewing or creating a durable service architecture. Trigger with "design Linear integration", "architect Linear webhook service", or "review Linear system design".

Triggers from the description

design Linear integrationarchitect Linear webhook servicereview Linear system design

Arguments

/linear-reference-architecture [repository-path] [read-only|bidirectional|event-driven]
Original author description

Design a Linear integration with separated auth, GraphQL, webhook, queue, policy, and reconciliation boundaries. Use when reviewing or creating a durable service architecture. Trigger with "design Linear integration", "architect Linear webhook service", or "review Linear system design".

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, 539 words
SKILL.md preview
---
name: linear-reference-architecture
description: >-
  Design a Linear integration with separated auth, GraphQL, webhook, queue, policy, and reconciliation boundaries. Use when reviewing or creating a durable service architecture. Trigger with "design Linear integration", "architect Linear webhook service", or "review Linear system design".
argument-hint: "[repository-path] [read-only|bidirectional|event-driven]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.13.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
- saas
- linear
- architecture
model: inherit
effort: high
compatibility: Designed for Claude Code; live verification requires network access and an approved Linear workspace credential
---
# Linear Integration Reference Architecture

## Overview

Create a repo-grounded architecture that makes authority, data flow, failure containment, and reconciliation explicit. Preserve the host application's boundaries instead of forcing a generic service topology.

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

- Use the official SDK for broad typed access and purpose-built GraphQL queries for narrow high-volume projections.
- Webhook ingress must verify the raw-body HMAC, acknowledge within five seconds, deduplicate by delivery ID, and move durable work to a queue.
- A reconciliation reader is still required because webhooks and downstream consumers can fail or be disabled.

## 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. Map callers, workspaces, teams, auth actors, data classes, latency targets, writes, and compliance boundaries from the repository.
2. Separate credential acquisition, Linear adapter, policy/authorization, webhook ingress, durable queue, worker, and reconciliation components.
3. Define stable identifiers, idempotency, pagination checkpoints, partial-error handling, and rate-budget ownership.
4. Keep mutation commands behind policy and approval checks; keep reads and reconciliation independently operable.
5. Design observability around operation metadata and delivery IDs with strict content redaction.
6. Review outage, backlog, schema change, credential rotation, replay, rollback, and tenant-isolation scenarios.

## 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 |
|---|---|
| Shared mutable client crosses tenants | Split credential and cache scope by workspace/actor. |
| Webhook does business work inline | Queue after verification and acknowledge quickly. |
| No reconciliation path | Add a cursor-based reader before declaring event-driven completeness. |
| Mutation policy embedded in transport | Separate business authorization from GraphQL mechanics. |

## Examples

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

Input:

```text
mode=bidirectional; tenants=multi-workspace; freshness=5m; writes=approval-gated
```

Expected handoff:

```text
boundaries=defined; ingress=queued; reconciliation=cursor-based; rollback=owned
```

## 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 10c3a1b0c2c6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

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

Similar skills

  • 100bamboohr-reference-architecture
    Design a multi-tenant BambooHR connector with explicit auth, ingestion, webhook, queue, storage, destination, reconciliation, and audit boundaries. Use when creating or reviewing production HR integration architecture. Trigger with "BambooHR architecture", "BambooHR system…
  • 100webflow-reference-architecture
    Design a Webflow integration architecture with explicit Data API, Content Delivery, webhook, identity, queue, and publication boundaries. Use when starting a service or untangling a coupled integration. Trigger with "Webflow architecture", "design Webflow integration", or "Webflow service layout".
  • 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".
  • 100linear
    Emulated Linear GraphQL API for local development and testing. Use when the user needs to test Linear integrations locally, emulate Linear issues, comments, teams, workflow states, OAuth apps, webhooks, agent sessions, or work with the Linear API without hitting the real Linear…
  • 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-hello-world
    Create your first Linear issue and query using the GraphQL API. Use when making initial API calls, testing Linear connection, or learning basic Linear operations. Trigger with phrases like "linear hello world", "first linear issue", "create linear issue", "linear API example",…

Feedback and reports

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