Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Manage Linear projects, issues, and tasks via the bundled Node CLI and the official Linear API. Use when you need to read, create, update, or organize Linear...
Manage Linear projects, issues, and tasks via the bundled Node CLI and the official Linear API. Use when you need to read, create, update, or organize Linear...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Manage Linear issues and projects through the bundled CLI at {baseDir}/scripts/linear-cli.js.
This skill runs node {baseDir}/scripts/linear-cli.js .... The CLI uses the official @linear/sdk. Authentication is LINEAR_API_KEY from the local environment. Expected API destination is Linear GraphQL (https://api.linear.app/graphql) through the official SDK.
Node.js and npm are installed. Install script dependencies once: cd {baseDir}/scripts && npm install Set your API key: export LINEAR_API_KEY="lin_api_..." If dependencies or LINEAR_API_KEY are missing, stop and complete setup before issue/project operations.
Required credential: LINEAR_API_KEY. Get it from https://linear.app/settings/api. Use least-privilege access and a dedicated token for automation.
Clarify intent and scope: Team/project, labels, cycle, assignee, due date, priority. Read current state first: List/get issues, projects, statuses, labels, users, cycles. Apply mutations second: Create/update issues, comments, projects, milestones, labels. Summarize exactly what changed: Mention IDs, states, assignees, blockers, and follow-up actions.
Teams and projects: teams, projects, createProject Issues: issues, issue, createIssue, updateIssue Comments: createComment States and labels: states, labels User: user
node {baseDir}/scripts/linear-cli.js teams node {baseDir}/scripts/linear-cli.js projects node {baseDir}/scripts/linear-cli.js issues node {baseDir}/scripts/linear-cli.js issue ENG-123 node {baseDir}/scripts/linear-cli.js createIssue "Title" "Description" "team-id" '{"priority":2}' node {baseDir}/scripts/linear-cli.js updateIssue "issue-id" '{"stateId":"state-id"}'
Triage urgent bugs: list high-priority open issues, assign owners, move state to In Progress, add triage comments. Sprint planning: review cycle scope, create missing issues, set priorities and estimates, align assignees. Release prep: verify blockers, update project status, create milestone tasks, add rollout comments. Documentation cleanup: find stale docs/issues, open follow-up tasks, link related records.
Never invent IDs; fetch and confirm before updates. Prefer narrow updates over broad bulk edits. For bulk edits, explain grouping logic before applying changes. Do not include secrets in issue comments or descriptions. Do not send data to endpoints outside Linear API scope for this skill.
references/API.md for priority values and workflow patterns.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.