Manage Linear issues, projects, and workflows via CLI. This skill should be used when the user wants to create, list, update, or search Linear issues, manage projects or milestones, or interact with their Linear workspace. Triggers on "create a task", "add a Linear issue", "list my issues", "update GLE-123", "what's in my backlog", or any Linear-related request.
npx skills add https://github.com/glebis/claude-skills --skill linear
Standalone CLI for the Linear issue tracker. Zero dependencies beyond Python 3.
On first use, authenticate via browser OAuth (no API keys needed):
linear auth
Opens the browser for Linear authorization. Uses MCP Dynamic Client Registration + PKCE — credentials are stored at ~/.config/linear/ with 0600 permissions.
The CLI script is bundled at scripts/linear within this skill directory. Execute it directly or reference its absolute path.
linear create "Issue title" \
--team GLE \
--state Todo \
--assignee me \
--due today \
--priority high \
--description "Markdown description" \
--label "Bug"
Priority: urgent, high, medium, low, none (or 0-4).
Due date: YYYY-MM-DD, today, tomorrow.
linear list --mine --status "In Progress"
linear list --team GLE --status Todo --limit 10
linear list --priority high --json
linear show GLE-123
linear show GLE-123 --json
linear update GLE-123 --state "In Progress"
linear update GLE-123 --priority urgent --due 2026-05-01
linear update GLE-123 --assignee me --title "New title"
linear comment GLE-123 "This is done, merging now"
linear teams
linear me
linear statuses --team GLE
linear labels --team GLE
GLE), not full team name, in --team flags.me unless specified otherwise.Todo.--due today for same-day tasks.--json for machine-readable output.Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Comprehensive technology-agnostic prompt for analyzing and documenting project folder structures. Auto-detects project types (.NET, Java, React, Angular, Python, Node.js, Flutter), generates detailed blueprints with visualization options, naming conventions, file placement patterns, and extension templates for maintaining consistent code organization across diverse technology stacks.
Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope.
Multi-agent workflow examples to work together on the OpenServ Platform. Covers agent discovery, multi-agent workspaces, task dependencies, and workflow orchestration using the Platform Client. Read reference.md for the full API reference. Read openserv-agent-sdk and openserv-client for building and running agents.
> Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md.
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
Patterns for automating GitHub workflows with AI assistance, inspired by [Gemini CLI](https://github.com/google-gemini/gemini-cli) and modern DevOps practices.
Groups existing components into logical business domains to plan service-based architecture. Use when asking "which components belong together?", "group these into services", "organize by domain", "component-to-domain mapping", or planning service extraction from an existing codebase. Do NOT use for identifying new domains from scratch (use domain-analysis) or analyzing coupling (use coupling-analysis).
Take glebis/linear from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.