以下为本文档的中文说明

该技能用于通过Rube MCP（Composio）自动化Linear项目管理平台的任务操作。Linear是现代化软件开发团队广泛使用的项目管理工具，此技能支持问题（Issue）创建与更新、项目（Project）管理、周期（Cycle）规划、团队（Team）设置和标签（Label）管理等核心功能。开发者可以利用此技能将Linear操作集成到自动化工作流中，实现从代码提交到任务状态更新的自动同步。适用于使用Linear进行项目管理的开发团队，帮助减少手动更新任务状态的重复劳动，提高项目追踪的准确性和团队协作效率。该技能始终在操作前搜索匹配项以避免重复工作。该技能提供了详细的操作指南和最佳实践，帮助用户快速上手并深入掌握。通过系统的功能模块划分和丰富的应用场景说明，用户可以在实际项目中有效运用该技能提升工作效率。该技能注重实用性和可操作性，涵盖从基础配置到高级功能的完整知识体系，满足不同层次用户的学习需求。持续更新和优化的内容确保用户始终能够接触到最新的技术发展和行业实践。通过此技能的学习和应用，用户可以减少摸索时间，快速获得可用的解决方案，将精力集中在核心业务逻辑和创新工作上，从而在技术快速迭代的环境中保持竞争力。该技能的模块化设计使其易于扩展和定制，用户可以根据自身需求灵活调整应用方式，实现最大化的价值产出。该技能整合了常见的设计模式和最佳实践，提供了清晰的学习路径和参考资料，帮助用户在短时间内建立起完整的知识框架，并有能力在实际项目中灵活运用所学内容解决问题。

Linear Automation via Rube MCP

Automate Linear operations through Composio’s Linear toolkit via Rube MCP.

Prerequisites

• Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
• Active Linear connection viaRUBE_MANAGE_CONNECTIONSwith toolkitlinear
• Always callRUBE_SEARCH_TOOLSfirst to get current tool schemas

Setup

Get Rube MCP: Addhttps://rube.app/mcpas an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

1. Verify Rube MCP is available by confirmingRUBE_SEARCH_TOOLSresponds
2. CallRUBE_MANAGE_CONNECTIONSwith toolkitlinear
3. If connection is not ACTIVE, follow the returned auth link to complete Linear OAuth
4. Confirm connection status shows ACTIVE before running any workflows

Core Workflows

1. Manage Issues

When to use: User wants to create, search, update, or list Linear issues

Tool sequence:

1. LINEAR_GET_ALL_LINEAR_TEAMS- Get team IDs [Prerequisite]
2. LINEAR_LIST_LINEAR_STATES- Get workflow states for a team [Prerequisite]
3. LINEAR_CREATE_LINEAR_ISSUE- Create a new issue [Optional]
4. LINEAR_SEARCH_ISSUES/LINEAR_LIST_LINEAR_ISSUES- Find issues [Optional]
5. LINEAR_GET_LINEAR_ISSUE- Get issue details [Optional]
6. LINEAR_UPDATE_ISSUE- Update issue properties [Optional]

Key parameters:

• team_id: Team ID (required for creation)
• title: Issue title
• description: Issue description (Markdown supported)
• state_id: Workflow state ID
• assignee_id: Assignee user ID
• priority: 0 (none), 1 (urgent), 2 (high), 3 (medium), 4 (low)
• label_ids: Array of label IDs

Pitfalls:

• Team ID is required when creating issues; use GET_ALL_LINEAR_TEAMS first
• State IDs are team-specific; use LIST_LINEAR_STATES with the correct team
• Priority uses integer values 0-4, not string names

2. Manage Projects

When to use: User wants to create or update Linear projects

Tool sequence:

1. LINEAR_LIST_LINEAR_PROJECTS- List existing projects [Optional]
2. LINEAR_CREATE_LINEAR_PROJECT- Create a new project [Optional]
3. LINEAR_UPDATE_LINEAR_PROJECT- Update project details [Optional]

Key parameters:

• name: Project name
• description: Project description
• team_ids: Array of team IDs associated with the project
• state: Project state (e.g., ‘planned’, ‘started’, ‘completed’)

Pitfalls:

• Projects span teams; they can be associated with multiple teams

3. Manage Cycles

When to use: User wants to work with Linear cycles (sprints)

Tool sequence:

1. LINEAR_GET_ALL_LINEAR_TEAMS- Get team ID [Prerequisite]
2. LINEAR_GET_CYCLES_BY_TEAM_ID/LINEAR_LIST_LINEAR_CYCLES- List cycles [Required]

Key parameters:

• team_id: Team ID for cycle operations
• number: Cycle number

Pitfalls:

• Cycles are team-specific; always scope by team_id

4. Manage Labels and Comments

When to use: User wants to create labels or comment on issues

Tool sequence:

1. LINEAR_CREATE_LINEAR_LABEL- Create a new label [Optional]
2. LINEAR_CREATE_LINEAR_COMMENT- Comment on an issue [Optional]
3. LINEAR_UPDATE_LINEAR_COMMENT- Edit a comment [Optional]

Key parameters:

• name: Label name
• color: Label color (hex)
• issue_id: Issue ID for comments
• body: Comment body (Markdown)

Pitfalls:

• Labels can be team-scoped or workspace-scoped
• Comment body supports Markdown formatting

5. Custom GraphQL Queries

When to use: User needs advanced queries not covered by standard tools

Tool sequence:

1. LINEAR_RUN_QUERY_OR_MUTATION- Execute custom GraphQL [Required]

Key parameters:

• query: GraphQL query or mutation string
• variables: Variables for the query

Pitfalls:

• Requires knowledge of Linear’s GraphQL schema
• Rate limits apply to GraphQL queries

Common Patterns

ID Resolution

Team name -> Team ID:

1. Call LINEAR_GET_ALL_LINEAR_TEAMS 2. Find team by name in response 3. Extract id field

State name -> State ID:

1. Call LINEAR_LIST_LINEAR_STATES with team_id 2. Find state by name 3. Extract id field

Pagination

• Linear tools return paginated results
• Check for pagination cursors in responses
• Pass cursor to next request for additional pages

Known Pitfalls

Team Scoping:

• Issues, states, and cycles are team-specific
• Always resolve team_id before creating issues

Priority Values:

• 0 = No priority, 1 = Urgent, 2 = High, 3 = Medium, 4 = Low
• Use integer values, not string names

Quick Reference

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.