linear-projects-read
List and get Linear projects via CLI (read-only operations)
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Overview
CLI tools for reading Linear projects. Requires LINEAR_API_KEY set in <git-root>/.env or exported in the environment.
Prerequisites
- bun runtime installed
-
LINEAR_API_KEYset in<git-root>/.envor environment
Commands
List Projects
bun .opencode/skill/linear-projects-read/list-projects.js [options]
Options:
-
--status <status>- Filter by status (planned, started, paused, completed, canceled) -
--lead <name>- Filter by project lead name -
--limit <n>- Max results (default: 25) -
--json- Output as JSON
Examples:
bun .opencode/skill/linear-projects-read/list-projects.js --limit 10
bun .opencode/skill/linear-projects-read/list-projects.js --status started
bun .opencode/skill/linear-projects-read/list-projects.js --lead "James Madison" --json
Get Project
bun .opencode/skill/linear-projects-read/get-project.js <project-id-or-name> [options]
Arguments:
-
project-id-or-name- Project UUID or name (partial match supported)
Options:
-
--json- Output as JSON
Examples:
bun .opencode/skill/linear-projects-read/get-project.js "Mount Vernon"
bun .opencode/skill/linear-projects-read/get-project.js "Monticello" --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
--jsonoutput with tools likejq, the processed results are already visible to the user
Notes
- Project names support partial matching (case-insensitive)
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-28
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!