search-linear-issues

Solid

Use this skill whenever the user wants to search, list, or filter Linear issues — by state, assignee, label, or free text — even if they say 'find', 'show me', 'what's open', 'list my issues', or similar phrasing rather than 'search Linear'. Composes a Linear IssueFilter from structured flags, executes a cursor-paginated search scoped to the configured team, and renders a summary table of the results. Prefer this skill over raw GraphQL whenever the user's intent maps to a structured flag.

AI & Automation 34 stars 1 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
51
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Search Linear Issues !`accelerator config context --skill search-linear-issues --fail-safe` > **Configuration**: Set `work.integration: linear` in `.accelerator/config.md`. > The team is fixed at `/init-linear` time (single-team scoping) — there is no > per-search `--team` flag. See the > [`### work` section of `configure/SKILL.md`](../../config/configure/SKILL.md#work) > for 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 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. ## Step 2: Run the search Run the search subcommand, passing the flags through verbatim: ``` accelerator linear search [flags] ``` Run the bare launcher **directly** as an executable; never prefix it with `bash`/`sh`/`env` and never pipe its output (a wrapper prefix or a pipe escapes the skill's `allowed-tools` permission and forces an unnecessary prompt). The subcommand echoes the composed `IssueFilter` to stderr (`INFO:`) for auditability and emits a...

Details

Author
atomicinnovation
Repository
atomicinnovation/accelerator
Created
6 months ago
Last Updated
yesterday
Language
Rust
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

show-linear-issue

Use this skill when the user asks about a specific Linear issue by identifier (e.g. BLA-123, ENG-456) — for viewing the description, state, assignee, or comments. Trigger when the user says 'look up', 'check on', 'tell me about', 'what's on', or 'what is the status of' an identifier, or asks any direct question about an issue they reference. Do NOT trigger when an identifier appears incidentally inside other prose (commit messages, code review comments, release notes), where the user is talking about the issue rather than asking to fetch it.

34 Updated yesterday
atomicinnovation
Data & Documents Solid

search-jira-issues

Use this skill whenever the user wants to search, list, or filter Jira tickets — by assignee, status, label, project, type, component, reporter, parent, or free text — even if they say 'find', 'show me', 'what's open', 'list my tickets', or similar phrasing rather than 'search Jira'. Composes safe JQL from structured flags, executes a paginated search against a Jira Cloud tenant, and renders a summary table of the results. Supports --render-adf to convert ADF descriptions to Markdown inline. Prefer this skill over raw JQL whenever the user's intent maps to a structured flag.

34 Updated yesterday
atomicinnovation
Code & Development Solid

update-linear-issue

Use this skill only when the user explicitly invokes /update-linear-issue to change fields on an existing Linear issue (title, description, state, assignee, priority). This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. It shows a payload preview, requires explicit confirmation, then applies the update.

34 Updated yesterday
atomicinnovation