메뉴
Search, read, create, and update the user's Linear issues, projects, and comments through per-user OAuth.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/yc-software/qm --skill linear명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Read and act on the user's Gmail, Google Calendar, and Google Tasks through per-user OAuth.
Draft Gmail in the user's own voice from the voice profile built by email-voice-profile. Drafts only; the user reviews and sends.
Deploy the QM package from an organization-owned deployment repository to Fly.io or AWS, onboard an administrator, configure connectors, and optionally activate Slack.
| name | linear |
| description | Search, read, create, and update the user's Linear issues, projects, and comments through per-user OAuth. |
| requiredCapabilities | ["egress:api.linear.app"] |
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.