linear-issues-read
List and get Linear issues via CLI (read-only operations)
Best use case
linear-issues-read is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
List and get Linear issues via CLI (read-only operations)
Teams using linear-issues-read should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/linear-issues-read/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How linear-issues-read Compares
| Feature / Agent | linear-issues-read | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
List and get Linear issues via CLI (read-only operations)
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## Overview CLI tools for reading Linear issues. Requires `LINEAR_API_KEY` set in `<git-root>/.env` or exported in the environment. ## Prerequisites - [bun](https://bun.sh) runtime installed - `LINEAR_API_KEY` set in `<git-root>/.env` or environment ## Commands ### List Issues ```bash bun .opencode/skill/linear-issues-read/list-issues.js [options] ``` **Options:** - `--team <name>` - Filter by team (e.g., Engineering, Infrastructure, Product) - `--project <name>` - Filter by project name - `--assignee <name>` - Filter by assignee name - `--status <status>` - Filter by status (e.g., "In Progress", "Todo", "Done") - `--limit <n>` - Max results (default: 25) - `--json` - Output as JSON **Examples:** ```bash bun .opencode/skill/linear-issues-read/list-issues.js --team Engineering --limit 10 bun .opencode/skill/linear-issues-read/list-issues.js --assignee "George Washington" --status "In Progress" bun .opencode/skill/linear-issues-read/list-issues.js --project "Mount Vernon" --json ``` --- ### Get Issue ```bash bun .opencode/skill/linear-issues-read/get-issue.js <issue-id> [options] ``` **Arguments:** - `issue-id` - Issue identifier (e.g., ENG-123) or UUID **Options:** - `--json` - Output as JSON **Examples:** ```bash bun .opencode/skill/linear-issues-read/get-issue.js ENG-123 bun .opencode/skill/linear-issues-read/get-issue.js ENG-123 --json ``` --- ## Output Behavior - Command output is displayed directly to the user in the terminal - **Do not re-summarize or reformat table output** - the user can already see it - Only provide additional commentary if the user explicitly requests analysis, filtering, or summarization - When using `--json` output with tools like `jq`, the processed results are already visible to the user ## Notes - Team, user, and label names are resolved automatically (case-insensitive)
Related Skills
scanning-for-accessibility-issues
This skill enables Claude to perform comprehensive accessibility audits. It uses the accessibility-test-scanner plugin to identify WCAG 2.1/2.2 compliance issues, validate ARIA attributes, check keyboard navigation, and assess screen reader compatibility. Use this skill when the user requests an accessibility scan, audit, or compliance check, or when terms like "WCAG", "ARIA", "screen reader", "accessibility testing", or "a11y" are mentioned. It provides actionable insights for improving web application accessibility.
gws-gmail-read
Gmail: Read a message and extract its body or headers.
readme-blueprint-generator
Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans .github/copilot directory files and copilot-instructions.md to extract project information, technology stack, architecture, development workflow, coding standards, and testing approaches while generating well-structured markdown documentation with proper formatting, cross-references, and developer-focused content.
my-issues
List my issues in the current repository
gen-specs-as-issues
This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.
create-readme
Create a README.md file for the project
create-github-issues-for-unmet-specification-requirements
Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.
create-github-issues-feature-from-implementation-plan
Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.
twitter-reader
Fetch Twitter/X post content by URL using jina.ai API to bypass JavaScript restrictions. Use when Claude needs to retrieve tweet content including author, timestamp, post text, images, and thread replies. Supports individual posts or batch fetching from x.com or twitter.com URLs.
safe-file-reader
Read files from documents directory safely
deep-reading-analyst
Comprehensive framework for deep analysis of articles, papers, and long-form content using 10+ thinking models (SCQA, 5W2H, critical thinking, inversion, mental models, first principles, systems thinking, six thinking hats). Use when users want to: (1) deeply understand complex articles/content, (2) analyze arguments and identify logical flaws, (3) extract actionable insights from reading materials, (4) create study notes or learning summaries, (5) compare multiple sources, (6) transform knowledge into practical applications, or (7) apply specific thinking frameworks. Triggered by phrases like 'analyze this article,' 'help me understand,' 'deep dive into,' 'extract insights from,' 'use [framework name],' or when users provide URLs/long-form content for analysis.
readme-i18n
Use when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized README variants in a GitHub-style repository.