JPeetz/agent-skills / skills/business-strategy/linear-project-management
linear-project-management
VerifiedUse this skill when driving Linear projects and issues from an agent.
| File | Kind | Size |
|---|---|---|
| CHANGELOG.md | markdown | 530 B |
| LICENSE | other | 1.1 KB |
| SKILL.md | skill md | 5.6 KB |
| evals/evals.json | config | 2.6 KB |
| references/linear-graphql.md | markdown | 1.8 KB |
| references/sources.md | markdown | 380 B |
references/linear-graphql.md
View on GitHub# Linear GraphQL Reference
Endpoint: `https://api.linear.app/graphql`
Auth header: `Authorization: {LINEAR_ACCESS_TOKEN}`
Always query your workspace for status IDs first — they are not global constants.
## Statuses (fetch first)
```graphql
query { projectStatuses { nodes { id name } } }
```
Common names: `Backlog`, `Planned`, `In Progress`, `Completed`, `Canceled`.
## Discovery before create
```graphql
query FindIssue($title: String!) {
issues(filter: { title: { contains: $title } }, first: 5) { nodes { id title } }
}
```
## Create issue
```graphql
mutation CreateIssue($title: String!, $teamId: String!, $description: String!) {
issueCreate(input: { title: $title, teamId: $teamId, description: $description }) {
success issue { id identifier }
}
}
```
## Create project (set BOTH description and content)
```graphql
mutation CreateProject($name: String!, $description: String!, $content: String!) {
projectCreate(input: { name: $name, description: $description, content: $content }) {
success project { id }
}
}
```
## Milestone / resource link
```graphql
mutation Milestone($projectId: String!, $name: String!, $description: String!) {
projectMilestoneCreate(input: { projectId: $projectId, name: $name, description: $description }) {
success milestone { id }
}
}
mutation Resource($url: String!, $label: String!, $projectId: String!) {
entityExternalLinkCreate(input: { url: $url, label: $label, projectId: $projectId }) {
success { entity { id } }
}
}
```
## Bulk state change (loop in the SDK, or N issueUpdate calls)
```graphql
mutation UpdateState($issueId: String!, $stateId: String!) {
issueUpdate(id: $issueId, input: { stateId: $stateId }) { success }
}
```
Source of the API patterns (MIT): wrsmith108/linear-claude-skill —
https://github.com/wrsmith108/linear-claude-skill
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |