[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ARJC509Y6DTAX0RYBA93M8":3,"skill-same:01M7ARJC509Y6DTAX0RYBA93M8":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ARJC509Y6DTAX0RYBA93M8","linear-automation",null,"Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.","GongYuanCaiJi\u002Fdsh-claude-code-templates","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7AK39QPS2RAJKRQY0EPQJPZ",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Flinear-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: linear-automation\ndescription: \"Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Linear Automation via Rube MCP\n\nAutomate Linear operations through Composio's Linear toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Linear connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `linear`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `linear`\n3. If connection is not ACTIVE, follow the returned auth link to complete Linear OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage Issues\n\n**When to use**: User wants to create, search, update, or list Linear issues\n\n**Tool sequence**:\n1. `LINEAR_GET_ALL_LINEAR_TEAMS` - Get team IDs [Prerequisite]\n2. `LINEAR_LIST_LINEAR_STATES` - Get workflow states for a team [Prerequisite]\n3. `LINEAR_CREATE_LINEAR_ISSUE` - Create a new issue [Optional]\n4. `LINEAR_SEARCH_ISSUES` \u002F `LINEAR_LIST_LINEAR_ISSUES` - Find issues [Optional]\n5. `LINEAR_GET_LINEAR_ISSUE` - Get issue details [Optional]\n6. `LINEAR_UPDATE_ISSUE` - Update issue properties [Optional]\n\n**Key parameters**:\n- `team_id`: Team ID (required for creation)\n- `title`: Issue title\n- `description`: Issue description (Markdown supported)\n- `state_id`: Workflow state ID\n- `assignee_id`: Assignee user ID\n- `priority`: 0 (none), 1 (urgent), 2 (high), 3 (medium), 4 (low)\n- `label_ids`: Array of label IDs\n\n**Pitfalls**:\n- Team ID is required when creating issues; use GET_ALL_LINEAR_TEAMS first\n- State IDs are team-specific; use LIST_LINEAR_STATES with the correct team\n- Priority uses integer values 0-4, not string names\n\n### 2. Manage Projects\n\n**When to use**: User wants to create or update Linear projects\n\n**Tool sequence**:\n1. `LINEAR_LIST_LINEAR_PROJECTS` - List existing projects [Optional]\n2. `LINEAR_CREATE_LINEAR_PROJECT` - Create a new project [Optional]\n3. `LINEAR_UPDATE_LINEAR_PROJECT` - Update project details [Optional]\n\n**Key parameters**:\n- `name`: Project name\n- `description`: Project description\n- `team_ids`: Array of team IDs associated with the project\n- `state`: Project state (e.g., 'planned', 'started', 'completed')\n\n**Pitfalls**:\n- Projects span teams; they can be associated with multiple teams\n\n### 3. Manage Cycles\n\n**When to use**: User wants to work with Linear cycles (sprints)\n\n**Tool sequence**:\n1. `LINEAR_GET_ALL_LINEAR_TEAMS` - Get team ID [Prerequisite]\n2. `LINEAR_GET_CYCLES_BY_TEAM_ID` \u002F `LINEAR_LIST_LINEAR_CYCLES` - List cycles [Required]\n\n**Key parameters**:\n- `team_id`: Team ID for cycle operations\n- `number`: Cycle number\n\n**Pitfalls**:\n- Cycles are team-specific; always scope by team_id\n\n### 4. Manage Labels and Comments\n\n**When to use**: User wants to create labels or comment on issues\n\n**Tool sequence**:\n1. `LINEAR_CREATE_LINEAR_LABEL` - Create a new label [Optional]\n2. `LINEAR_CREATE_LINEAR_COMMENT` - Comment on an issue [Optional]\n3. `LINEAR_UPDATE_LINEAR_COMMENT` - Edit a comment [Optional]\n\n**Key parameters**:\n- `name`: Label name\n- `color`: Label color (hex)\n- `issue_id`: Issue ID for comments\n- `body`: Comment body (Markdown)\n\n**Pitfalls**:\n- Labels can be team-scoped or workspace-scoped\n- Comment body supports Markdown formatting\n\n### 5. Custom GraphQL Queries\n\n**When to use**: User needs advanced queries not covered by standard tools\n\n**Tool sequence**:\n1. `LINEAR_RUN_QUERY_OR_MUTATION` - Execute custom GraphQL [Required]\n\n**Key parameters**:\n- `query`: GraphQL query or mutation string\n- `variables`: Variables for the query\n\n**Pitfalls**:\n- Requires knowledge of Linear's GraphQL schema\n- Rate limits apply to GraphQL queries\n\n## Common Patterns\n\n### ID Resolution\n\n**Team name -> Team ID**:\n```\n1. Call LINEAR_GET_ALL_LINEAR_TEAMS\n2. Find team by name in response\n3. Extract id field\n```\n\n**State name -> State ID**:\n```\n1. Call LINEAR_LIST_LINEAR_STATES with team_id\n2. Find state by name\n3. Extract id field\n```\n\n### Pagination\n\n- Linear tools return paginated results\n- Check for pagination cursors in responses\n- Pass cursor to next request for additional pages\n\n## Known Pitfalls\n\n**Team Scoping**:\n- Issues, states, and cycles are team-specific\n- Always resolve team_id before creating issues\n\n**Priority Values**:\n- 0 = No priority, 1 = Urgent, 2 = High, 3 = Medium, 4 = Low\n- Use integer values, not string names\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List teams | LINEAR_GET_ALL_LINEAR_TEAMS | (none) |\n| Create issue | LINEAR_CREATE_LINEAR_ISSUE | team_id, title, description |\n| Search issues | LINEAR_SEARCH_ISSUES | query |\n| List issues | LINEAR_LIST_LINEAR_ISSUES | team_id, filters |\n| Get issue | LINEAR_GET_LINEAR_ISSUE | issue_id |\n| Update issue | LINEAR_UPDATE_ISSUE | issue_id, fields |\n| List states | LINEAR_LIST_LINEAR_STATES | team_id |\n| List projects | LINEAR_LIST_LINEAR_PROJECTS | (none) |\n| Create project | LINEAR_CREATE_LINEAR_PROJECT | name, team_ids |\n| Update project | LINEAR_UPDATE_LINEAR_PROJECT | project_id, fields |\n| List cycles | LINEAR_LIST_LINEAR_CYCLES | team_id |\n| Get cycles | LINEAR_GET_CYCLES_BY_TEAM_ID | team_id |\n| Create label | LINEAR_CREATE_LINEAR_LABEL | name, color |\n| Create comment | LINEAR_CREATE_LINEAR_COMMENT | issue_id, body |\n| Update comment | LINEAR_UPDATE_LINEAR_COMMENT | comment_id, body |\n| List users | LINEAR_LIST_LINEAR_USERS | (none) |\n| Current user | LINEAR_GET_CURRENT_USER | (none) |\n| Run GraphQL | LINEAR_RUN_QUERY_OR_MUTATION | query, variables |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Linear Automation via Rube MCP\n\nAutomate Linear operations through Composio's Linear toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Linear connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `linear`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `linear`\n3. If connection is not ACTIVE, follow the returned auth link to complete Linear OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage Issues\n\n**When to use**: User wants to create, search, update, or list Linear issues\n\n**Tool sequence**:\n1. `LINEAR_GET_ALL_LINEAR_TEAMS` - Get team IDs [Prerequisite]\n2. `LINEAR_LIST_LINEAR_STATES` - Get workflow states for a team [Prerequisite]\n3. `LINEAR_CREATE_LINEAR_ISSUE` - Create a new issue [Optional]\n4. `LINEAR_SEARCH_ISSUES` \u002F `LINEAR_LIST_LINEAR_ISSUES` - Find issues [Optional]\n5. `LINEAR_GET_LINEAR_ISSUE` - Get issue details [Optional]\n6. `LINEAR_UPDATE_ISSUE` - Update issue properties [Optional]\n\n**Key parameters**:\n- `team_id`: Team ID (required for creation)\n- `title`: Issue title\n- `description`: Issue description (Markdown supported)\n- `state_id`: Workflow state ID\n- `assignee_id`: Assignee user ID\n- `priority`: 0 (none), 1 (urgent), 2 (high), 3 (medium), 4 (low)\n- `label_ids`: Array of label IDs\n\n**Pitfalls**:\n- Team ID is required when creating issues; use GET_ALL_LINEAR_TEAMS first\n- State IDs are team-specific; use LIST_LINEAR_STATES with the correct team\n- Priority uses integer values 0-4, not string names\n\n### 2. Manage Projects\n\n**When to use**: User wants to create or update Linear projects\n\n**Tool sequence**:\n1. `LINEAR_LIST_LINEAR_PROJECTS` - List existing projects [Optional]\n2. `LINEAR_CREATE_LINEAR_PROJECT` - Create a new project [Optional]\n3. `LINEAR_UPDATE_LINEAR_PROJECT` - Update project details [Optional]\n\n**Key parameters**:\n- `name`: Project name\n- `description`: Project description\n- `team_ids`: Array of team IDs associated with the project\n- `state`: Project state (e.g., 'planned', 'started', 'completed')\n\n**Pitfalls**:\n- Projects span teams; they can be associated with multiple teams\n\n### 3. Manage Cycles\n\n**When to use**: User wants to work with Linear cycles (sprints)\n\n**Tool sequence**:\n1. `LINEAR_GET_ALL_LINEAR_TEAMS` - Get team ID [Prerequisite]\n2. `LINEAR_GET_CYCLES_BY_TEAM_ID` \u002F `LINEAR_LIST_LINEAR_CYCLES` - List cycles [Required]\n\n**Key parameters**:\n- `team_id`: Team ID for cycle operations\n- `number`: Cycle number\n\n**Pitfalls**:\n- Cycles are team-specific; always scope by team_id\n\n### 4. Manage Labels and Comments\n\n**When to use**: User wants to create labels or comment on issues\n\n**Tool sequence**:\n1. `LINEAR_CREATE_LINEAR_LABEL` - Create a new label [Optional]\n2. `LINEAR_CREATE_LINEAR_COMMENT` - Comment on an issue [Optional]\n3. `LINEAR_UPDATE_LINEAR_COMMENT` - Edit a comment [Optional]\n\n**Key parameters**:\n- `name`: Label name\n- `color`: Label color (hex)\n- `issue_id`: Issue ID for comments\n- `body`: Comment body (Markdown)\n\n**Pitfalls**:\n- Labels can be team-scoped or workspace-scoped\n- Comment body supports Markdown formatting\n\n### 5. Custom GraphQL Queries\n\n**When to use**: User needs advanced queries not covered by standard tools\n\n**Tool sequence**:\n1. `LINEAR_RUN_QUERY_OR_MUTATION` - Execute custom GraphQL [Required]\n\n**Key parameters**:\n- `query`: GraphQL query or mutation string\n- `variables`: Variables for the query\n\n**Pitfalls**:\n- Requires knowledge of Linear's GraphQL schema\n- Rate limits apply to GraphQL queries\n\n## Common Patterns\n\n### ID Resolution\n\n**Team name -> Team ID**:\n```\n1. Call LINEAR_GET_ALL_LINEAR_TEAMS\n2. Find team by name in response\n3. Extract id field\n```\n\n**State name -> State ID**:\n```\n1. Call LINEAR_LIST_LINEAR_STATES with team_id\n2. Find state by name\n3. Extract id field\n```\n\n### Pagination\n\n- Linear tools return paginated results\n- Check for pagination cursors in responses\n- Pass cursor to next request for additional pages\n\n## Known Pitfalls\n\n**Team Scoping**:\n- Issues, states, and cycles are team-specific\n- Always resolve team_id before creating issues\n\n**Priority Values**:\n- 0 = No priority, 1 = Urgent, 2 = High, 3 = Medium, 4 = Low\n- Use integer values, not string names\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List teams | LINEAR_GET_ALL_LINEAR_TEAMS | (none) |\n| Create issue | LINEAR_CREATE_LINEAR_ISSUE | team_id, title, description |\n| Search issues | LINEAR_SEARCH_ISSUES | query |\n| List issues | LINEAR_LIST_LINEAR_ISSUES | team_id, filters |\n| Get issue | LINEAR_GET_LINEAR_ISSUE | issue_id |\n| Update issue | LINEAR_UPDATE_ISSUE | issue_id, fields |\n| List states | LINEAR_LIST_LINEAR_STATES | team_id |\n| List projects | LINEAR_LIST_LINEAR_PROJECTS | (none) |\n| Create project | LINEAR_CREATE_LINEAR_PROJECT | name, team_ids |\n| Update project | LINEAR_UPDATE_LINEAR_PROJECT | project_id, fields |\n| List cycles | LINEAR_LIST_LINEAR_CYCLES | team_id |\n| Get cycles | LINEAR_GET_CYCLES_BY_TEAM_ID | team_id |\n| Create label | LINEAR_CREATE_LINEAR_LABEL | name, color |\n| Create comment | LINEAR_CREATE_LINEAR_COMMENT | issue_id, body |\n| Update comment | LINEAR_UPDATE_LINEAR_COMMENT | comment_id, body |\n| List users | LINEAR_LIST_LINEAR_USERS | (none) |\n| Current user | LINEAR_GET_CURRENT_USER | (none) |\n| Run GraphQL | LINEAR_RUN_QUERY_OR_MUTATION | query, variables |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-02-27","main","51493f354fd03e3f941d4df7fd64c0b8c7a2632d","skills\u002Fworkflow-automation\u002Flinear-automation","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 02:24:07",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill linear-automation",{"tool":40,"command":41},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill linear-automation",{"tool":43,"command":44},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill linear-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Flinear-automation\u002FSKILL.md",true,[],[49,56,65,72,79,86],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7ARMYTZ5D4B7N5SKFXV345V","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":61,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7ARMX1BVNEAR98SBANMDF2V","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7ARMPR4RQ417MG1HMPGNQHH","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7ARMHBERDMKGDMV7K6MQ6YP","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7ARME0A7KFT330Q2H25HE2B","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7ARM8D87V18WDG0GEZS11ZT","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]