以下为本文档的中文说明该技能用于通过Rube MCPComposio自动化Linear项目管理平台的任务操作。Linear是现代化软件开发团队广泛使用的项目管理工具此技能支持问题Issue创建与更新、项目Project管理、周期Cycle规划、团队Team设置和标签Label管理等核心功能。开发者可以利用此技能将Linear操作集成到自动化工作流中实现从代码提交到任务状态更新的自动同步。适用于使用Linear进行项目管理的开发团队帮助减少手动更新任务状态的重复劳动提高项目追踪的准确性和团队协作效率。该技能始终在操作前搜索匹配项以避免重复工作。该技能提供了详细的操作指南和最佳实践帮助用户快速上手并深入掌握。通过系统的功能模块划分和丰富的应用场景说明用户可以在实际项目中有效运用该技能提升工作效率。该技能注重实用性和可操作性涵盖从基础配置到高级功能的完整知识体系满足不同层次用户的学习需求。持续更新和优化的内容确保用户始终能够接触到最新的技术发展和行业实践。通过此技能的学习和应用用户可以减少摸索时间快速获得可用的解决方案将精力集中在核心业务逻辑和创新工作上从而在技术快速迭代的环境中保持竞争力。该技能的模块化设计使其易于扩展和定制用户可以根据自身需求灵活调整应用方式实现最大化的价值产出。该技能整合了常见的设计模式和最佳实践提供了清晰的学习路径和参考资料帮助用户在短时间内建立起完整的知识框架并有能力在实际项目中灵活运用所学内容解决问题。Linear Automation via Rube MCPAutomate Linear operations through Composio’s Linear toolkit via Rube MCP.PrerequisitesRube MCP must be connected (RUBE_SEARCH_TOOLS available)Active Linear connection viaRUBE_MANAGE_CONNECTIONSwith toolkitlinearAlways callRUBE_SEARCH_TOOLSfirst to get current tool schemasSetupGet Rube MCP: Addhttps://rube.app/mcpas an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.Verify Rube MCP is available by confirmingRUBE_SEARCH_TOOLSrespondsCallRUBE_MANAGE_CONNECTIONSwith toolkitlinearIf connection is not ACTIVE, follow the returned auth link to complete Linear OAuthConfirm connection status shows ACTIVE before running any workflowsCore Workflows1. Manage IssuesWhen to use: User wants to create, search, update, or list Linear issuesTool sequence:LINEAR_GET_ALL_LINEAR_TEAMS- Get team IDs [Prerequisite]LINEAR_LIST_LINEAR_STATES- Get workflow states for a team [Prerequisite]LINEAR_CREATE_LINEAR_ISSUE- Create a new issue [Optional]LINEAR_SEARCH_ISSUES/LINEAR_LIST_LINEAR_ISSUES- Find issues [Optional]LINEAR_GET_LINEAR_ISSUE- Get issue details [Optional]LINEAR_UPDATE_ISSUE- Update issue properties [Optional]Key parameters:team_id: Team ID (required for creation)title: Issue titledescription: Issue description (Markdown supported)state_id: Workflow state IDassignee_id: Assignee user IDpriority: 0 (none), 1 (urgent), 2 (high), 3 (medium), 4 (low)label_ids: Array of label IDsPitfalls:Team ID is required when creating issues; use GET_ALL_LINEAR_TEAMS firstState IDs are team-specific; use LIST_LINEAR_STATES with the correct teamPriority uses integer values 0-4, not string names2. Manage ProjectsWhen to use: User wants to create or update Linear projectsTool sequence:LINEAR_LIST_LINEAR_PROJECTS- List existing projects [Optional]LINEAR_CREATE_LINEAR_PROJECT- Create a new project [Optional]LINEAR_UPDATE_LINEAR_PROJECT- Update project details [Optional]Key parameters:name: Project namedescription: Project descriptionteam_ids: Array of team IDs associated with the projectstate: Project state (e.g., ‘planned’, ‘started’, ‘completed’)Pitfalls:Projects span teams; they can be associated with multiple teams3. Manage CyclesWhen to use: User wants to work with Linear cycles (sprints)Tool sequence:LINEAR_GET_ALL_LINEAR_TEAMS- Get team ID [Prerequisite]LINEAR_GET_CYCLES_BY_TEAM_ID/LINEAR_LIST_LINEAR_CYCLES- List cycles [Required]Key parameters:team_id: Team ID for cycle operationsnumber: Cycle numberPitfalls:Cycles are team-specific; always scope by team_id4. Manage Labels and CommentsWhen to use: User wants to create labels or comment on issuesTool sequence:LINEAR_CREATE_LINEAR_LABEL- Create a new label [Optional]LINEAR_CREATE_LINEAR_COMMENT- Comment on an issue [Optional]LINEAR_UPDATE_LINEAR_COMMENT- Edit a comment [Optional]Key parameters:name: Label namecolor: Label color (hex)issue_id: Issue ID for commentsbody: Comment body (Markdown)Pitfalls:Labels can be team-scoped or workspace-scopedComment body supports Markdown formatting5. Custom GraphQL QueriesWhen to use: User needs advanced queries not covered by standard toolsTool sequence:LINEAR_RUN_QUERY_OR_MUTATION- Execute custom GraphQL [Required]Key parameters:query: GraphQL query or mutation stringvariables: Variables for the queryPitfalls:Requires knowledge of Linear’s GraphQL schemaRate limits apply to GraphQL queriesCommon PatternsID ResolutionTeam name - Team ID:1. Call LINEAR_GET_ALL_LINEAR_TEAMS 2. Find team by name in response 3. Extract id fieldState name - State ID:1. Call LINEAR_LIST_LINEAR_STATES with team_id 2. Find state by name 3. Extract id fieldPaginationLinear tools return paginated resultsCheck for pagination cursors in responsesPass cursor to next request for additional pagesKnown PitfallsTeam Scoping:Issues, states, and cycles are team-specificAlways resolve team_id before creating issuesPriority Values:0 No priority, 1 Urgent, 2 High, 3 Medium, 4 LowUse integer values, not string namesQuick ReferenceTaskTool SlugKey ParamsList teamsLINEAR_GET_ALL_LINEAR_TEAMS(none)Create issueLINEAR_CREATE_LINEAR_ISSUEteam_id, title, descriptionSearch issuesLINEAR_SEARCH_ISSUESqueryList issuesLINEAR_LIST_LINEAR_ISSUESteam_id, filtersGet issueLINEAR_GET_LINEAR_ISSUEissue_idUpdate issueLINEAR_UPDATE_ISSUEissue_id, fieldsList statesLINEAR_LIST_LINEAR_STATESteam_idList projectsLINEAR_LIST_LINEAR_PROJECTS(none)Create projectLINEAR_CREATE_LINEAR_PROJECTname, team_idsUpdate projectLINEAR_UPDATE_LINEAR_PROJECTproject_id, fieldsList cyclesLINEAR_LIST_LINEAR_CYCLESteam_idGet cyclesLINEAR_GET_CYCLES_BY_TEAM_IDteam_idCreate labelLINEAR_CREATE_LINEAR_LABELname, colorCreate commentLINEAR_CREATE_LINEAR_COMMENTissue_id, bodyUpdate commentLINEAR_UPDATE_LINEAR_COMMENTcomment_id, bodyList usersLINEAR_LIST_LINEAR_USERS(none)Current userLINEAR_GET_CURRENT_USER(none)Run GraphQLLINEAR_RUN_QUERY_OR_MUTATIONquery, variablesWhen to UseThis skill is applicable to execute the workflow or actions described in the overview.LimitationsUse 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.