Find Linear issues by text, assignee, or status, and read their details and comments. Prepare new issues, comments, and status changes for user approval, then return identifiers and links so results can be checked.
Search, read, create, and update the user's Linear issues, projects, and comments through per-user OAuth.
Review the instructions the agent will receive before you install.
Use this skill when the user asks about Linear issues, tickets, projects, cycles, or their team's work tracking — finding issues, checking status, filing a bug, leaving a comment, or updating an issue.
This is an OAuth connector. The resolved user's Linear token already lives on your computer as an environment variable (the way a logged-in CLI's cached credential would):
$VAULT_TOKEN_API_LINEAR_APP — for api.linear.appLinear's API is GraphQL at https://api.linear.app/graphql. Pass the token as a bearer
header (-H "Authorization: Bearer $VAULT_TOKEN_API_LINEAR_APP"). Do not ask the user for
a token, log it, or use another principal's credential.
If the variable is empty or the API returns 401/400 (authentication), tell the user they
need to connect Linear (Connectors page) and stop — don't guess at issue data.
Query issues by text, assignee, or state:
curl -sS -X POST 'https://api.linear.app/graphql' \
-H "Authorization: Bearer $VAULT_TOKEN_API_LINEAR_APP" \
-H 'content-type: application/json' \
--data '{"query":"{ issues(first: 20, filter: { title: { containsIgnoreCase: \"login\" } }) { nodes { identifier title state { name } assignee { name } url } } }"}'
Read one issue by id/identifier:
curl -sS -X POST 'https://api.linear.app/graphql' \
-H "Authorization: Bearer $VAULT_TOKEN_API_LINEAR_APP" \
-H 'content-type: application/json' \
--data '{"query":"{ issue(id: \"ENG-123\") { identifier title description state { name } assignee { name } url comments { nodes { body user { name } } } } }"}'
Keep issue identifiers and urls in your answer so claims can be traced.
To create or assign an issue you usually need a team id — list them once:
curl -sS -X POST 'https://api.linear.app/graphql' \
-H "Authorization: Bearer $VAULT_TOKEN_API_LINEAR_APP" \
-H 'content-type: application/json' \
--data '{"query":"{ teams(first: 100) { nodes { id key name } pageInfo { hasNextPage endCursor } } }"}'
Linear paginates every list: if pageInfo.hasNextPage is true, re-query with
after: "<endCursor>" — never conclude a team or issue doesn't exist from one page.
Creating an issue, commenting, or changing state is a write. Prepare the exact mutation, summarize what it will create/change (team, title, target issue), and ask for approval before running it.
After approval, create an issue:
curl -sS -X POST 'https://api.linear.app/graphql' \
-H "Authorization: Bearer $VAULT_TOKEN_API_LINEAR_APP" \
-H 'content-type: application/json' \
--data '{"query":"mutation($input: IssueCreateInput!) { issueCreate(input: $input) { success issue { identifier url } } }","variables":{"input":{"teamId":"TEAM_ID","title":"Login button misaligned on mobile","description":"Reported by a user; repro on iOS Safari."}}}'
Add a comment to an existing issue:
curl -sS -X POST 'https://api.linear.app/graphql' \
-H "Authorization: Bearer $VAULT_TOKEN_API_LINEAR_APP" \
-H 'content-type: application/json' \
--data '{"query":"mutation($input: CommentCreateInput!) { commentCreate(input: $input) { success comment { url } } }","variables":{"input":{"issueId":"ISSUE_UUID","body":"Fixed in the latest deploy."}}}'
Always report the resulting issue/comment identifier and url.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Help QM organization admins inspect settings, stored memory, conversations, files, and operational records across the organization. It also supports confirmed configuration changes and external user management, while keeping admin grant changes in the dashboard.
Carry out website tasks in a remote browser, including expense submissions, authorized orders, and retrieving data behind a login. Personal browser profiles preserve sign-ins, while users handle login and verification screens themselves.
Sign in to a cloud provider’s command-line tool using a verification URL and one-time code approved on the user’s device. Check installation and account identity, save the login, and run commands within that user’s permissions.
Help users discover and connect apps, then run available app tools through QM’s authenticated backend. It checks connection status, presents consent options, and keeps Composio project keys out of user-facing setup.
Connect supported work apps through browser consent without sharing passwords with the agent. The skill checks available connection methods, provides a single-use authorization link when appropriate, and guides personal Slack account linking.
Set up recurring agent work for issues, tickets, or small fixes. The skill tests one real item first, then defines a repeatable procedure, tracks work to prevent duplicates, and holds outputs for human review.