Linear

Independent, unofficial connector for Linear. Not affiliated with, endorsed by, or sponsored by Linear. "Linear" is a trademark of its owner, used only to identify the service this connector works with.

Tools for working with Linear over the Linear GraphQL API (POST https://api.linear.app/graphql): create and update issues, comment on them and attach links, find issues by identifier or filter, manage projects and post project updates, and resolve the teams, workflow states, labels, users, milestones, and cycles an agent needs to act. 22 scripts across issue writes, issue reads, projects, and workspace navigation. This version covers the day-to-day issue-tracking job over the public API; every tool builds one GraphQL query or mutation and posts it to the single endpoint.

When to use this

• An agent needs to create or update issues — open an issue in a team; change its title, description, state, assignee, priority, project, cycle, or due date; add or remove a single label; comment on it; or attach a link (a related ticket, doc, or PR).
• An agent needs to find or read issues — fetch one by UUID or human identifier (e.g. ENG-118), or search by title text, assignee, state, team, project, or label, then read its comment thread.
• An agent needs to manage projects — create or update a project, read one, list projects, and post a status update with a health signal.
• An agent needs to resolve names to ids before writing — list teams, workflow states, labels, users, project milestones, and cycles, or get the authenticated "me" identity for assign-to-self / "my issues" flows.

Setup

This is an agentskills.io skill.

If the connector has not been installed as a skill yet, install it first with npx skills add zapier/connectors --skill linear (or your harness's own skill-install mechanism), then continue here. Installing the skill copies these files, not dependencies. Before running the CLI, a local MCP server, or zapier-sdk auth commands, run npm install --omit=dev here once. Importing the published package as a dependency in your own project instead? That npm install already resolves everything — see references/use-as-sdk.md.