agentsclimarketplace
Sign in

Linear issues write

Skill bg-szy/TOP-SKILLS/skills/marketplace/linear-issues-write

Create and update Linear issues via CLI (write operations)From its SKILL.md

Install
npx -y skills add bg-szy/TOP-SKILLS --skill linear-issues-write

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.6 KB, 715 tokens by cl100k_base, as published. Nobody here has run it

Overview

CLI tools for creating and updating Linear issues. Requires LINEAR_API_KEY set in <git-root>/.env or exported in the environment.

Prerequisites

  • bun runtime installed
  • LINEAR_API_KEY set in <git-root>/.env or environment

Commands

Create Issue

bun .opencode/skill/linear-issues-write/create-issue.js --title "..." --team <team> [options]

Required:

  • --title <title> - Issue title
  • --team <name> - Team name (e.g., Engineering)

Options:

  • --description <text> - Issue description
  • --assignee <name> - Assignee name
  • --priority <0-4> - Priority: 0=none, 1=urgent, 2=high, 3=medium, 4=low
  • --labels <labels> - Comma-separated labels (e.g., "Bug,SOC2")
  • --project <name> - Project name
  • --json - Output as JSON

Examples:

bun .opencode/skill/linear-issues-write/create-issue.js --title "Fix login bug" --team Engineering --priority 2
bun .opencode/skill/linear-issues-write/create-issue.js --title "New feature" --team Engineering --labels "Feature" --assignee "John Adams"
bun .opencode/skill/linear-issues-write/create-issue.js --title "Security fix" --team Engineering --project "Monticello" --priority 1

Update Issue

bun .opencode/skill/linear-issues-write/update-issue.js <issue-id> [options]

Arguments:

  • issue-id - Issue identifier (e.g., ENG-123) or UUID

Options:

  • --title <title> - New title
  • --description <text> - New description
  • --status <status> - New status (e.g., "In Progress", "Done")
  • --assignee <name> - New assignee (use "none" to unassign)
  • --priority <0-4> - New priority
  • --labels <labels> - Replace all labels
  • --add-labels <labels> - Add labels without removing existing
  • --project <name> - Set project (use "none" to remove)
  • --json - Output as JSON

Examples:

bun .opencode/skill/linear-issues-write/update-issue.js ENG-123 --status "In Progress"
bun .opencode/skill/linear-issues-write/update-issue.js ENG-123 --assignee "Thomas Jefferson" --priority 2
bun .opencode/skill/linear-issues-write/update-issue.js ENG-123 --add-labels "Bug,Urgent"
bun .opencode/skill/linear-issues-write/update-issue.js ENG-123 --assignee none

Notes

  • Team, user, and label names are resolved automatically (case-insensitive)
  • Use --json flag for machine-readable output suitable for scripting
  • All commands support --help for detailed usage information

What ships with it: 2 files

38.2 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,750. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.