search-linear-issues
Invocation: User- and model-invocable
Argument hint: [--state NAME] [--assignee NAME] [--label NAME] [--text STR] [--limit 1..250] [--quiet]
Allowed tools: Bash(${CLAUDE_PLUGIN_ROOT}/skills/integrations/linear/scripts/*), Bash(${CLAUDE_PLUGIN_ROOT}/scripts/config-*), Bash(jq), Bash(curl)
Source: skills/integrations/linear/search-linear-issues/SKILL.md
Search Linear Issues
Section titled “Search Linear Issues”!${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.
Step 1: Parse the flag set
Section titled “Step 1: Parse the flag set”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;--limitonly sets the per-request page size.
Step 2: Run the search
Section titled “Step 2: Run the search”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.
Step 3: Render the results
Section titled “Step 3: Render the results”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

