← Back to Skills Marketplace

Linear

Name: Linear
Author: byungkyu

by byungkyu · GitHub ↗ · v1.2.9 · MIT-0

cross-platform ✓ Security Clean

14569

Downloads

Stars

Active Installs

Versions

Install in OpenClaw

/install linear-api

Description

Linear API integration with managed OAuth. Query and manage issues, projects, teams, cycles, and labels using GraphQL. Use this skill when users name Linear explicitly or ask about their Linear issues, cycles, projects, or teams — for example "create a Linear issue for this bug", "what is in my current cycle", "move ENG-412 to done". Not for GitHub issues, Jira, or generic task lists, and not for planning work that is not tracked in Linear. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Linear connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Linear action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Linear examples; they add no Linear capability - Linear is itself an event source, so its own events are in `references/linear/triggers.md`, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

Usage Guidance

Before installing, expect this skill to connect through Maton and Linear OAuth and to access business issue data. Approve only the account and scopes needed, confirm every mutation or automation before it runs, avoid unscoped triggers or third-party destinations unless you explicitly want ongoing forwarding, and prefer OAuth over long-lived API keys.

Capability Assessment

ℹ Credentials

Requested Bash/Read/Grep/Glob and network access are proportionate for a CLI-backed API skill. The raw HTTP fallback requires a Maton API key, but the artifact explicitly limits that path to cases where the CLI cannot be installed and gives handling rules to avoid leaking or persisting the key.

ℹ Install Mechanism

Installation uses a pinned Maton CLI via npm or Homebrew and optional pinned SDK packages; there are no executable files shipped in the skill artifact. Global package installation and OAuth setup are expected for this integration and disclosed.

ℹ Instruction Scope

The main skill gives clear activation criteria, excludes GitHub/Jira/generic task lists, defaults to read/list calls, and requires confirmation for writes, new connections, hosted functions, triggers, and destinations. The Linear trigger reference could give more example trigger phrases, but its text still limits use to connected sources and named event requests.

ℹ Persistence & Privilege

The skill uses persistent OAuth credentials in the OS credential store and can create server-side functions, triggers, and destinations, including automatic event forwarding. These are high-impact capabilities, but the artifact repeatedly discloses them, requires explicit user approval, recommends narrow scoping and DENY_ALL network policy, and provides deletion/revocation guidance.

✓ Purpose & Capability

The skill purpose is Linear API access through Maton OAuth, and the documented capabilities match that purpose: reading and managing Linear issues, teams, projects, cycles, labels, comments, and related Linear-triggered automation.

How to Use

Make sure OpenClaw is installed (local or Docker)
Run the install command in chat: /install linear-api
After installation, invoke the skill by name or use /linear-api
Provide required inputs per the skill's parameter spec and get structured output

Version History

v1.2.9

Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.

v1.2.8

Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.

v1.2.7

Align the appendix caution text with the example, which extracts a single field rather than printing the whole response

v1.2.6

Extract only the needed field in the raw HTTP fallback example instead of printing the whole response body

v1.2.5

Fix the raw HTTP fallback example: restore the gateway base URL in the GATEWAY constant (and the fastmail streaming call), which a previous edit had replaced with a placeholder

v1.2.4

Make the GraphQL request model consistent throughout (every Linear call is a POST; classify reads and writes by query vs mutation) and describe Drive's file-level scope precisely

v1.2.3

Resolve remaining audit findings: correct the delete-task example object type, align appendix request guidance with GraphQL-only POST, list workspace members and the full Klaviyo surface in the declared scope, and narrow activation wording with explicit exclusions

v1.2.2

Resolve remaining audit findings: state one consistent endpoint policy instead of conflicting scope claims, qualify the local-execution and high-impact wording, note that locale examples are illustrative, and correct app-specific auth, method and upload-path documentation

v1.2.1

Address security-audit findings: disclose the api passthrough in the access-scope and description text, warn on irreversible connection deletion, add response data-minimization guidance, and correct app-specific auth and request-body notes

v1.2.0

CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings

v1.1.0

CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment

v1.0.6

- Removed the sample file `skill-card.md`. - No other user-facing changes or new features.

v1.0.5

- Added Maton CLI commands throughout documentation for improved usability and quick start. - Expanded setup instructions to include Homebrew and NPM installation options. - Provided CLI equivalents for all connection management and core API tasks alongside existing Python examples. - Updated example queries and CLI usage for more practical, real-world tasks (issue listing, team view, etc.). - Clarified connection specification steps for users with multiple Linear accounts.

v1.0.4

- Updated API and connection management endpoints from `gateway.maton.ai`/`ctrl.maton.ai` to `api.maton.ai` - Added new section outlining security & permissions, highlighting the need for explicit user approval for write operations - Improved instructions for specifying which Linear connection to use when working with multiple accounts - Clarified proxying and authentication flow for Maton API integrations - Removed the file `LICENSE.txt`

v1.0.3

- Added `clawdbot` metadata section with required environment variable `MATON_API_KEY`. - No changes to API, documentation, or functionality.

v1.0.2

- Documentation update only: SKILL.md file has been modified. - No functional changes to the skill; endpoints and usage remain the same.

v1.0.1

- No code or documentation changes detected in this version. - Version number incremented to 1.0.1.

v1.0.0

Initial release of the Linear API integration skill. - Provides access to the Linear API with managed OAuth authentication via the Maton platform. - Allows querying and managing issues, projects, teams, cycles, labels, and comments using GraphQL. - Includes connection management endpoints (list, create, get, delete) for Linear OAuth connections. - Offers detailed usage examples for key workflows (issue search, create/update issues, team/project querying). - Requires a Maton API key and network access for all operations.

Metadata

Slug linear-api

Version 1.2.9

License MIT-0

All-time Installs 0

Active Installs 0

Total Versions 18

Frequently Asked Questions

What is Linear?

How do I install Linear?

Run "/install linear-api" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Linear free?

Yes, Linear is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Linear support?

Linear is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Linear?

It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.9.

More Skills