linear-lifecycle
Use when working with Linear issues, issue tracking, or project management. Uses the Linear CLI for zero-context issue management as a CLI alternative to MCP.
What this skill does
# Linear Lifecycle Management with Linear CLI ## Table of Contents - [Overview](#overview) - [Setup](#setup) - [When to Use](#when-to-use) - [Token Check](#token-check) - [Quick Reference](#quick-reference) - [Reference Files](#reference-files) ## Overview **Core principle:** Use the Linear CLI for all Linear operations instead of loading the 20k token Linear MCP. CLI returns structured output for parsing without context overhead. **Tool:** [linear-cli](https://github.com/schpet/linear-cli) - Linear CLI with ~1000 token footprint vs 13k+ for MCP. Install via `brew install schpet/tap/linear`. **Context savings:** 100% at session start. No MCP loaded, just bash commands. See [advanced.md](reference/advanced.md) for the full comparison table. ## Setup **One-time install:** Use `/linear-setup` to install the Linear CLI and authenticate (required for this skill to work). **Authentication:** Run `linear auth login` after creating an API key at linear.app/settings/account/security. See [troubleshooting.md](reference/troubleshooting.md) for auth issues. **Get your token:** Linear Settings > Security & Access > Personal API keys ## When to Use **Use this skill when:** - Starting work on a Linear issue (need issue details) - Creating new issues from bugs or features discovered - Updating issue status during development - Adding comments or progress updates - Searching for issues across teams/projects **Don't use when:** - Issue tracking not needed for current work - Working on non-Linear projects ## Token Check **IMPORTANT: Always verify auth on first Linear operation in a skill invocation:** ```bash linear issue list ``` If the command fails with an auth error, prompt the user to run `linear auth login` and provide their API token. ## Quick Reference | Operation | Command Pattern | |-----------|----------------| | List recent issues | `linear issue list` | | Get issue details | `linear issue view ABC-123` | | Create issue | `linear issue create -t "Title" -d "Desc" --team TEAM_KEY` | | Update status | `linear issue update ABC-123 -s "In Progress"` | | Add comment | `linear issue comment add ABC-123 "Comment text"` | | List teams | `linear team list` | **Key rules for issue creation:** - Use `--team TEAM_KEY` (e.g. BET, ENG) - Use `-t` for title, `-d` for description - Use `-s` for state changes on update ## Reference Files Detailed walkthroughs, troubleshooting, and advanced usage are in reference files that load on demand: - [Command Examples](reference/examples.md) - Step-by-step walkthroughs for each operation - [Troubleshooting](reference/troubleshooting.md) - Common mistakes, error handling patterns, and auth setup issues - [Advanced Usage](reference/advanced.md) - Multi-team operations and context budget comparison table
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.