Linear
PassAudited by ClawScan on May 7, 2026.
Overview
This is a coherent Linear integration, but it needs a Maton API key/OAuth connection and can read or change Linear workspace data, so users should approve write actions carefully.
Before installing, make sure you trust Maton with your Linear OAuth connection and workspace data. Use the intended Linear connection ID when multiple accounts exist, and require explicit confirmation before any action that creates, updates, or deletes Linear data.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If approved incorrectly, the agent could create, update, or delete Linear records such as issues, projects, labels, or comments.
The skill gives the agent write-capable Linear API workflows, including GraphQL operations. This is purpose-aligned and includes an approval instruction, but users should notice that mistakes could affect workspace data.
Access the Linear API with managed OAuth authentication. Query and manage issues, projects, teams, cycles, labels, and comments using GraphQL. ... All write operations require explicit user approval.
Confirm the exact Linear workspace, resource, and intended change before approving any create, update, or delete operation.
The skill can act through the connected Linear account within the permissions granted to the OAuth connection.
The integration relies on a Maton API key and a Linear OAuth token. That is expected for the stated Linear integration, but it grants account-level delegated authority.
Requires network access and valid Maton API key. ... Maton proxies requests to `api.linear.app` and automatically injects your OAuth token.
Connect only the intended Linear account, use the least-privileged OAuth connection available, and revoke the connection when it is no longer needed.
Linear issue, project, team, and user data may be transmitted through Maton while using the skill.
Linear requests and responses are routed through Maton's gateway before reaching Linear. This is disclosed and purpose-aligned, but it means Linear data passes through an additional service boundary.
https://api.maton.ai/linear/graphql ... Maton proxies requests to `api.linear.app` and automatically injects your OAuth token.
Use this only if you trust Maton to handle your Linear data and OAuth connection appropriately.
Installing the optional CLI adds external software to the local environment that was not reviewed in the provided skill artifacts.
The documentation suggests installing an external CLI globally. This appears purpose-aligned, but the CLI package itself is outside the provided artifact set.
npm install -g @maton-ai/cli ... brew install maton-ai/cli/maton
Install the Maton CLI only from the official source you trust, and verify the package before using it with your API key.