mcp-linear
Call Linear MCP tools via mcporter CLI — issues, projects, teams, comments, cycles, milestones, and more. Use for: 'create Linear issue', 'list my issues', 'update issue status', 'check sprint progress', 'add comment to ticket'. Replaces native Linear MCP plugin to save context window.
What this skill does
<objective> Call Linear MCP tools through the mcporter CLI instead of loading 33 tool definitions into the context window. This skill covers all Linear operations: issues, projects, teams, comments, documents, cycles, milestones, labels, attachments, and users. </objective> <process> ## Call Syntax Two equivalent forms — use whichever is clearer: ```bash # Colon-delimited (shell-friendly, best for simple args) mcporter call linear.TOOL_NAME key:value key2:value2 --output json # Function-call style (better for complex args) mcporter call 'linear.TOOL_NAME(key: "value", key2: "value2")' --output json ``` Always use `--output json` for machine-readable results you'll parse. ## Issues ```bash # List issues (assignee "me" = current user) mcporter call linear.list_issues assignee:me limit:10 --output json # Search issues by text mcporter call linear.list_issues query:"search terms" team:ENG --output json # Get single issue by ID mcporter call linear.get_issue id:ENG-123 --output json # Get issue with relations (blocking/blocked-by/duplicates) mcporter call linear.get_issue id:ENG-123 includeRelations:true --output json # Create issue mcporter call 'linear.create_issue(title: "Bug: login broken", team: "ENG", priority: 2, assignee: "me")' --output json # Create issue with labels mcporter call 'linear.create_issue(title: "Fix deploy", team: "ENG", labels: "[\"Bug\",\"Infra\"]")' --output json # Update issue (state, priority, assignee, etc.) mcporter call 'linear.update_issue(id: "ENG-123", state: "In Progress", priority: 1)' --output json # Filter by state, label, project, priority, delegate mcporter call linear.list_issues state:started label:bug project:infra priority:2 --output json # Filter by date (ISO-8601 durations) mcporter call 'linear.list_issues(team: "ENG", createdAt: "-P7D")' --output json mcporter call 'linear.list_issues(team: "ENG", updatedAt: "-P1D")' --output json # Include archived issues mcporter call linear.list_issues team:ENG includeArchived:true --output json ``` ## Comments ```bash # List comments on an issue mcporter call linear.list_comments issueId:ISSUE_UUID --output json # Create comment (body is markdown) mcporter call 'linear.create_comment(issueId: "ISSUE_UUID", body: "Comment text here")' --output json ``` ## Teams ```bash mcporter call linear.list_teams --output json mcporter call linear.get_team query:ENG --output json ``` ## Projects ```bash # List/get projects mcporter call linear.list_projects --output json mcporter call linear.get_project query:infra --output json mcporter call linear.get_project query:infra includeMilestones:true --output json # Create project mcporter call 'linear.create_project(name: "Q2 Platform", description: "Platform improvements for Q2", teams: "[\"ENG\"]")' --output json # Update project mcporter call 'linear.update_project(id: "PROJECT_UUID", state: "started", description: "Updated scope")' --output json # List project labels mcporter call linear.list_project_labels --output json ``` ## Users ```bash mcporter call linear.list_users --output json mcporter call linear.get_user query:me --output json ``` ## Extended Operations Milestones, Documents, Attachments, Cycles, Labels, Statuses, and other tools are documented in `references/tool-catalog.md`. Or run `mcporter list linear --all-parameters` to see all tools. </process> <tips> - Use `--output json` for all calls when you need to parse the result. - Issue identifiers (like ENG-123) work for `get_issue` but UUIDs are needed for `update_issue`, `list_comments`, etc. Get the UUID from `get_issue` first. - Discover all tools and parameters: `mcporter list linear --all-parameters` - **Priority values**: 0=None, 1=Urgent, 2=High, 3=Normal, 4=Low - **State** accepts type names (backlog, unstarted, started, completed, cancelled) or specific state names. - The `assignee` field accepts "me", a user name, email, or UUID. - For creating issues with labels, use: `labels:'["Bug","Frontend"]'` - **Date filters**: Use ISO-8601 durations — `-P1D` (last day), `-P7D` (last week), `-P30D` (last month), `-P90D` (last quarter). - First call in a session may take ~2s for OAuth token refresh; subsequent calls are faster. </tips>
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.