linear-api Skill
Read and manage Linear issues, projects, cycles, teams, comments, and labels. Use this whenever the user wants to list their issues, search issues, create or update an issue, move an issue between states, add a comment, check a project or cycle, look up a team, or ask "what's on my plate in Linear" — even if they don't Published by anthropics in claude-tag-plugins.
What is linear-api Skill?
Read and manage Linear issues, projects, cycles, teams, comments, and labels. Use this whenever the user wants to list their issues, search issues, create or update an issue, move an issue between states, add a comment, check a project or cycle, look up a team, or ask "what's on my plate in Linear" — even if they don't Published by anthropics in claude-tag-plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Design and media
- Writing
- Research
- Design and media use cases
- Writing use cases
Technical details
- Install or run with Copy skill directory
When to use linear-api Skill
- Use it for design and media.
- Use it for writing.
- Use it for research.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/claude-tag-plugins
- Skill file: linear/skills/linear-api/SKILL.md
What it does
Read and manage Linear issues, projects, cycles, teams, comments, and labels. Use this whenever the user wants to list their issues, search issues, create or update an issue, move an issue between states, add a comment, check a project or cycle, look up a team, or ask "what's on my plate in Linear" — even if they don't
Skill instructions
Linear has a single GraphQL endpoint — there is no REST API. Every read is a query, every write is a mutation, and everything goes to one URL. Don't look for /api/v1/issues-style paths; they don't exist. POST https://api.linear.app/graphql Two ID systems coexist: - UUID (id) — what the API uses everywhere for lookups and mutations. - Identifier (identifier, e.g. ENG-123) — the human-readable key shown in the UI. You can fetch an issue by identifier with issue(id: "ENG-123") (Linear accepts both). Request setup Authentication is handled by the runtime — credentials are injected into outbound requests to this API, so there is nothing to set up. Do not try to create, mint, refresh, or validate tokens or keys. Credential variables exist only to keep requests well-formed; if one is unset, set it to any placeholder value. A persistent 401/403 means the credential isn't configured for this workspace — report that instead of debugging auth. Linear expects the credential in the Authorization he
Explore related resources
Frequently asked questions
What is linear-api?
linear-api is a open-source AI agent skill with Copy skill directory. Read and manage Linear issues, projects, cycles, teams, comments, and labels. Use this whenever the user wants to list their issues, search issues, create or update an issue, move an issue between states, add.
Who is linear-api best for?
linear-api is best for reusing agent instructions, scripts, and references, design and media workflows, writing workflows, research workflows.
How do I install linear-api?
Install or run linear-api using Copy skill directory. Check linear-api for the latest setup command.
Is linear-api actively maintained?
linear-api may need a closer maintenance check before production use.
Auto-fetched from GitHub.
