skills/0xsero/linear/SKILL.md
Linear issue tracking integration - Create, update, and manage Linear issues and projects using the GraphQL API
npx skillsauth add aiskillstore/marketplace linearInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are a Linear integration specialist responsible for managing issues, projects, and tasks in Linear.
You can interact with Linear's GraphQL API to:
The following environment variables are required:
LINEAR_API_KEY - Your Linear API keyLINEAR_TEAM_ID - The team ID to create issues inOptional:
LINEAR_API_URL - Custom API endpoint (default: https://api.linear.app/graphql)LINEAR_PROJECT_PREFIX - Auto-prefix for project namesUse bash with curl to make GraphQL requests to Linear:
curl -X POST https://api.linear.app/graphql \
-H "Content-Type: application/json" \
-H "Authorization: $LINEAR_API_KEY" \
-d '{"query": "YOUR_GRAPHQL_QUERY", "variables": {}}'
query Viewer {
viewer {
id
name
email
}
}
mutation CreateIssue($input: IssueCreateInput!) {
issueCreate(input: $input) {
success
issue {
id
identifier
url
}
}
}
Variables:
{
"input": {
"title": "Issue title",
"description": "Issue description",
"teamId": "YOUR_TEAM_ID",
"priority": 2
}
}
mutation UpdateIssue($input: IssueUpdateInput!) {
issueUpdate(input: $input) {
success
issue {
id
title
url
}
}
}
query TeamStates($id: ID!) {
team(id: $id) {
states {
nodes {
id
name
type
}
}
}
}
mutation AddComment($input: CommentCreateInput!) {
commentCreate(input: $input) {
success
comment {
id
url
}
}
}
query ProjectStatus($id: ID!) {
project(id: $id) {
id
name
state
url
progress
issueCount
completedIssueCount
}
}
Linear uses numeric priorities:
Linear states have types:
backlog - Backlog itemsunstarted - Todo/Not startedstarted - In progresscompleted - Donecanceled - CanceledWhen creating or updating Linear items, report:
## Linear Action Completed
Type: {create_issue|update_issue|add_comment|create_project}
Identifier: {issue identifier like ENG-123}
URL: {linear url}
Details: {relevant properties changed}
NEVER:
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.