skills/integrations/linear/linear-update-tickets/SKILL.md
Update Linear ticket status or add comments. Load when user says "update linear ticket", "mark ticket as done", "move CLI-XXX to [status]", "change ticket status", "add comment to ticket", or "close ticket".
npx skillsauth add beam-ai-team/beam-next-skills linear-update-ticketsInstall 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.
Update existing Linear tickets - change status, add comments, or modify fields.
Modify Linear tickets discussed in meetings or that need status updates. Supports state changes, adding comments, and batch updates.
Requirements: Linear API key in .env
# Add to .env (NO Bearer prefix when using!)
LINEAR_API_KEY=lin_api_xxxxx
API Endpoint: https://api.linear.app/graphql
Auth Header: Authorization: {LINEAR_API_KEY} (NO "Bearer" prefix!)
State IDs (Clients team): | State | ID | |-------|-----| | Todo | d8899534-a204-4446-a06b-681cbc4c6e04 | | In Progress | 9a2c9ba8-5931-491e-8298-c9fb761aab23 | | In Review | 7866c5ad-5654-4516-849f-b3f7462613d6 | | Done | 40112a2a-870e-48ca-aeff-7f16356acd90 |
Get ticket identifier:
Options:
Update Status:
mutation UpdateIssue($id: String!, $input: IssueUpdateInput!) {
issueUpdate(id: $id, input: $input) {
success
issue {
identifier
title
state { name }
}
}
}
Variables:
{
"id": "issue-uuid",
"input": {
"stateId": "40112a2a-870e-48ca-aeff-7f16356acd90"
}
}
Add Comment:
mutation AddComment($issueId: String!, $body: String!) {
commentCreate(input: {
issueId: $issueId,
body: $body
}) {
success
comment { id body }
}
}
Updated CLI-123:
- Status: In Progress → Done
- Comment added: "Completed per meeting discussion"
To update a ticket, you need its UUID (not the CLI-XXX identifier):
query GetIssue($identifier: String!) {
issue(id: $identifier) {
id
identifier
title
state { id name }
}
}
Get current state IDs for any team:
query($teamId: String!) {
team(id: $teamId) {
states { nodes { id name type } }
}
}
For multiple tickets:
Update tickets CLI-123, CLI-124, CLI-125 to Done
Process each sequentially and report results:
Updated 3 tickets:
- CLI-123: In Progress → Done
- CLI-124: Todo → Done
- CLI-125: In Review → Done
| Error | Cause | Solution | |-------|-------|----------| | 401 Unauthorized | Wrong auth format | NO "Bearer" prefix | | Issue not found | Invalid identifier | Verify ticket exists | | Invalid state | Wrong state ID | Query team states first |
linear-create-tickets - Create new ticketscreate-weekly-update - Report on ticket changesprocess-client-meeting - May update tickets from discussionVersion: 1.0 Integration: Linear GraphQL API Owner: Hassaan Ahmed
development
--- name: taste-skill type: skill version: '1.0' author: Leonxlnx (packaged by Zhichao Li) category: general tags: - frontend - design - anti-slop - landing-page updated: '2026-06-11' visibility: public description: Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check. license: MIT.
development
Use when communicating quantitative information in any form — Slack updates, emails, reports, decks, dashboards, landing pages, product UI, public talks. Covers two integrated layers: (1) making numbers semantically meaningful (translation, anchoring, simplification, story-pairing) and (2) showing numbers cleanly (chart vs table vs prose, chart-by-message, pre-attentive emphasis, color discipline, decluttering). Distilled and integrated from *Show Me the Numbers* (Stephen Few) and *Make Numbers Count* (Chip Heath & Karla Starr). Not for raw data analysis or statistics — this is about communication of numbers, not their derivation.
development
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
tools
Stateful multi-session tutor adapted for Beam — teach a stakeholder to understand, trust, and operate a specific agent, or teach a Solution Engineer a client's business process for delivery. Grounds every lesson in Knowledge Hub sources (real agent graphs, real tasks, transcripts, Linear) before any web resource. Also works for any general topic. Trigger on "teach me", "beam teach", "教我", "onboard <person> on <agent>", "help <stakeholder> understand the agent", "learn this client's process".