Stats
Actions
Tags
From accelerator
Searches Linear issues by state, assignee, label, or free text with pagination and renders a summary table. Useful for finding and listing issues in the configured team.
How this skill is triggered — by the user, by Claude, or both
Slash command
/accelerator:search-linear-issues [--state NAME] [--assignee NAME] [--label NAME] [--text STR] [--limit 1..250] [--quiet][--state NAME] [--assignee NAME] [--label NAME] [--text STR] [--limit 1..250] [--quiet]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
!`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh`
!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh
!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-context.sh search-linear-issues
Configuration: Set
work.integration: linearin.accelerator/config.md. The team is fixed at/init-lineartime (single-team scoping) — there is no per-search--teamflag. See the### worksection ofconfigure/SKILL.mdfor the full reference.
Search the configured Linear team using structured flags that compose into a
Linear IssueFilter. Work through the steps below in order.
Read the argument string and note each flag:
--state NAME — WorkflowState name. Resolved (case-insensitively) to its
team-scoped UUID via the cached catalogue; an unknown state is an error.--assignee NAME — assignee display name.--label NAME — label name.--text STR — free-text match on the issue title.--limit N — page size (1..250, default 50). Pagination follows every page
regardless; --limit only sets the per-request page size.Run the search flow, passing the flags through verbatim:
${CLAUDE_PLUGIN_ROOT}/skills/integrations/linear/scripts/linear-search-flow.sh [flags]
Run the bare path directly as an executable; never prefix it with
bash/sh/env (a wrapper prefix escapes the skill's allowed-tools
permission and forces an unnecessary prompt).
The flow echoes the composed IssueFilter to stderr (INFO:) for auditability
and emits a single merged JSON result with all pages under .data.issues.nodes.
If .data.issues.truncated is true, more pages remained than were fetched —
say so.
Render a Markdown table with one row per issue:
| Identifier | Title | State | Assignee |
|---|
Read each row from .data.issues.nodes[]: .identifier, .title,
.state.name, .assignee.name (show — for an unassigned issue). Report the
total count and note if the result was truncated.
!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-instructions.sh search-linear-issues
npx claudepluginhub atomicinnovation/accelerator --plugin acceleratorSearch Linear issues by text in title/description or filters like team:KEY, status:NAME, priority:LEVEL, assignee:me, label:NAME. Displays top 20 results in a table.
Manages Linear.app issues via Linearis CLI with JSON output: create, read, update, search issues; list teams/projects/cycles/labels/users; add comments.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.