linear

Translate human commands into Linear GraphQL API calls for issue management.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/regain-inc/popper --skill linear-regain-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear
Source: https://github.com/regain-inc/popper/tree/main/.claude/skills/linear
Command: npx skills add https://github.com/regain-inc/popper --skill linear-regain-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, jq, curl, and includes scripts (resource) components.

What problem does it solve?

Lightweight Linear integration via API scripts that replaces large MCP plugin and saves tokens, enabling fast, scriptable ticket operations.

Core Features & Use Cases

  • Lightweight Linear integration via API scripts for querying, creating, updating issues, and managing projects and cycles.
  • Repo-aware defaults: when running inside the popper repo, queries default to the "Popper" project unless explicitly asked for all projects.
  • Rich command surface: member, workload, status, project-issues, project-member, search, get, create, update, comment, and more, with explicit overrides to target specific projects or teams.

Quick Start

Run the Linear skill commands to fetch and manipulate tickets using .claude/skills/linear/scripts/linear.sh after setting LINEAR_API_KEY.

Frequently Asked Questions about linear

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Linear tickets automatically from the command line?

Linear ticket management is automated by translating human commands into GraphQL API calls using shell scripts. You can query, create, update, and comment on issues directly from the CLI without leaving your environment.

What is the best way to script Linear issue searches and updates?

Scripting Linear issue searches and updates is handled via the linear.sh shell script, which interacts with the Linear GraphQL API. It supports resolving specific IDs, filtering by projects or cycles, and mutating issues based on human commands.

Do I need an API key to automate Linear issue management via CLI?

Yes, a valid LINEAR_API_KEY environment variable is required to authenticate and automate Linear issue management. The script uses this key to authorize GraphQL API calls for fetching and mutating tickets.

Can I use this Linear integration to default queries to a specific project?

Yes, the integration supports repo-aware defaults, automatically querying the "Popper" project when running inside the popper repository. You can also apply explicit overrides to target different projects or teams.

Why use shell scripts instead of a large MCP plugin for Linear API operations?

Using shell scripts for Linear API operations saves tokens and provides a lightweight integration alternative to large MCP plugins. This approach enables fast, scriptable ticket operations with minimal overhead using curl and jq.

What are the limitations of using shell scripts for Linear GraphQL automation?

Limitations include dependency on external CLI tools like jq, curl, and pyyaml, meaning the environment must support shell execution. Complex asynchronous workflows or real-time streaming may exceed the capabilities of script-based API interactions.