mrklnc/clawdbot-skill-linear

Overview

This skill lets you interact with Linear for issue tracking via command-line scripts. It provides commands to create, update, search, and list issues, teams, states, and users. Use it to view assignments, change status, add comments, and manage task metadata quickly from a terminal.

How this skill works

The skill uses a shell wrapper script (scripts/linear.sh) that calls the Linear API with credentials stored in ~/.clawdbot/credentials/linear.json. Commands map to common Linear actions (issues, get, create, update, comment, teams, states, users) and support a --json flag for raw API responses. You pass IDs (team, state, user, issue) or flags like --mine to scope results.

When to use it

• Create, assign, or prioritize a new issue from the terminal.
• Update issue status, assignee, or priority without opening the web UI.
• List your assigned issues or team backlogs quickly.
• Search issues by keywords to find related work or duplicates.
• Add comments or link fixes to an issue from a CI job or local script.

Best practices

• Store the API key in ~/.clawdbot/credentials/linear.json with the key name apiKey.
• Use list commands (teams, states, users) to retrieve IDs before creating or updating issues.
• Use --json when integrating output into scripts or CI pipelines to parse API results reliably.
• Include clear, actionable descriptions and priorities when creating issues to reduce back-and-forth.
• Check current state IDs before updating to avoid invalid transitions.

Example use cases

• Create and assign a high-priority bug: find team ID, then scripts/linear.sh create --team TEAM_ID --title "Bug: ..." --priority 2
• Move a ticket into In Progress: list states to get STATE_ID, then scripts/linear.sh update CLP-45 --state STATE_ID
• List my open work: scripts/linear.sh issues --mine to quickly see assigned tasks
• Search for similar issues before filing a new one: scripts/linear.sh search "auth bug"
• Post an automated comment from CI after a deployment: scripts/linear.sh comment CLP-123 "Deployed fix in PR #42"