[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72CE9V8WH8F5CD7MAPARQFZ":3,"skill-same:01M72CE9V8WH8F5CD7MAPARQFZ":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":13,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M72CE9V8WH8F5CD7MAPARQFZ","jira-automation",null,"Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fjira-automation\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: jira-automation\ndescription: \"Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Jira Automation via Rube MCP\n\nAutomate Jira operations through Composio's Jira toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Jira connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`\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\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`\n3. If connection is not ACTIVE, follow the returned auth link to complete Jira OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Search and Filter Issues\n\n**When to use**: User wants to find issues using JQL or browse project issues\n\n**Tool sequence**:\n1. `JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST` - Search with JQL query [Required]\n2. `JIRA_GET_ISSUE` - Get full details of a specific issue [Optional]\n\n**Key parameters**:\n- `jql`: JQL query string (e.g., `project = PROJ AND status = \"In Progress\"`)\n- `maxResults`: Max results per page (default 50, max 100)\n- `startAt`: Pagination offset\n- `fields`: Array of field names to return\n- `issueIdOrKey`: Issue key like 'PROJ-123' for GET_ISSUE\n\n**Pitfalls**:\n- JQL field names are case-sensitive and must match Jira configuration\n- Custom fields use IDs like `customfield_10001`, not display names\n- Results are paginated; check `total` vs `startAt + maxResults` to continue\n\n### 2. Create and Edit Issues\n\n**When to use**: User wants to create new issues or update existing ones\n\n**Tool sequence**:\n1. `JIRA_GET_ALL_PROJECTS` - List projects to find project key [Prerequisite]\n2. `JIRA_GET_FIELDS` - Get available fields and their IDs [Prerequisite]\n3. `JIRA_CREATE_ISSUE` - Create a new issue [Required]\n4. `JIRA_EDIT_ISSUE` - Update fields on an existing issue [Optional]\n5. `JIRA_ASSIGN_ISSUE` - Assign issue to a user [Optional]\n\n**Key parameters**:\n- `project`: Project key (e.g., 'PROJ')\n- `issuetype`: Issue type name (e.g., 'Bug', 'Story', 'Task')\n- `summary`: Issue title\n- `description`: Issue description (Atlassian Document Format or plain text)\n- `issueIdOrKey`: Issue key for edits\n\n**Pitfalls**:\n- Issue types and required fields vary by project; use GET_FIELDS to check\n- Custom fields require exact field IDs, not display names\n- Description may need Atlassian Document Format (ADF) for rich content\n\n### 3. Manage Sprints and Boards\n\n**When to use**: User wants to work with agile boards, sprints, and backlogs\n\n**Tool sequence**:\n1. `JIRA_LIST_BOARDS` - List all boards [Prerequisite]\n2. `JIRA_LIST_SPRINTS` - List sprints for a board [Required]\n3. `JIRA_MOVE_ISSUE_TO_SPRINT` - Move issue to a sprint [Optional]\n4. `JIRA_CREATE_SPRINT` - Create a new sprint [Optional]\n\n**Key parameters**:\n- `boardId`: Board ID from LIST_BOARDS\n- `sprintId`: Sprint ID for move operations\n- `name`: Sprint name for creation\n- `startDate`\u002F`endDate`: Sprint dates in ISO format\n\n**Pitfalls**:\n- Boards and sprints are specific to Jira Software (not Jira Core)\n- Only one sprint can be active at a time per board\n\n### 4. Manage Comments\n\n**When to use**: User wants to add or view comments on issues\n\n**Tool sequence**:\n1. `JIRA_LIST_ISSUE_COMMENTS` - List existing comments [Optional]\n2. `JIRA_ADD_COMMENT` - Add a comment to an issue [Required]\n\n**Key parameters**:\n- `issueIdOrKey`: Issue key like 'PROJ-123'\n- `body`: Comment body (supports ADF for rich text)\n\n**Pitfalls**:\n- Comments support ADF (Atlassian Document Format) for formatting\n- Mentions use account IDs, not usernames\n\n### 5. Manage Projects and Users\n\n**When to use**: User wants to list projects, find users, or manage project roles\n\n**Tool sequence**:\n1. `JIRA_GET_ALL_PROJECTS` - List all projects [Optional]\n2. `JIRA_GET_PROJECT` - Get project details [Optional]\n3. `JIRA_FIND_USERS` \u002F `JIRA_GET_ALL_USERS` - Search for users [Optional]\n4. `JIRA_GET_PROJECT_ROLES` - List project roles [Optional]\n5. `JIRA_ADD_USERS_TO_PROJECT_ROLE` - Add user to role [Optional]\n\n**Key parameters**:\n- `projectIdOrKey`: Project key\n- `query`: Search text for FIND_USERS\n- `roleId`: Role ID for role operations\n\n**Pitfalls**:\n- User operations use account IDs (not email or display name)\n- Project roles differ from global permissions\n\n## Common Patterns\n\n### JQL Syntax\n\n**Common operators**:\n- `project = \"PROJ\"` - Filter by project\n- `status = \"In Progress\"` - Filter by status\n- `assignee = currentUser()` - Current user's issues\n- `created >= -7d` - Created in last 7 days\n- `labels = \"bug\"` - Filter by label\n- `priority = High` - Filter by priority\n- `ORDER BY created DESC` - Sort results\n\n**Combinators**:\n- `AND` - Both conditions\n- `OR` - Either condition\n- `NOT` - Negate condition\n\n### Pagination\n\n- Use `startAt` and `maxResults` parameters\n- Check `total` in response to determine remaining pages\n- Continue until `startAt + maxResults >= total`\n\n## Known Pitfalls\n\n**Field Names**:\n- Custom fields use IDs like `customfield_10001`\n- Use JIRA_GET_FIELDS to discover field IDs and names\n- Field names in JQL may differ from API field names\n\n**Authentication**:\n- Jira Cloud uses account IDs, not usernames\n- Site URL must be configured correctly in the connection\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Search issues (JQL) | JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST | jql, maxResults |\n| Get issue | JIRA_GET_ISSUE | issueIdOrKey |\n| Create issue | JIRA_CREATE_ISSUE | project, issuetype, summary |\n| Edit issue | JIRA_EDIT_ISSUE | issueIdOrKey, fields |\n| Assign issue | JIRA_ASSIGN_ISSUE | issueIdOrKey, accountId |\n| Add comment | JIRA_ADD_COMMENT | issueIdOrKey, body |\n| List comments | JIRA_LIST_ISSUE_COMMENTS | issueIdOrKey |\n| List projects | JIRA_GET_ALL_PROJECTS | (none) |\n| Get project | JIRA_GET_PROJECT | projectIdOrKey |\n| List boards | JIRA_LIST_BOARDS | (none) |\n| List sprints | JIRA_LIST_SPRINTS | boardId |\n| Move to sprint | JIRA_MOVE_ISSUE_TO_SPRINT | sprintId, issues |\n| Create sprint | JIRA_CREATE_SPRINT | name, boardId |\n| Find users | JIRA_FIND_USERS | query |\n| Get fields | JIRA_GET_FIELDS | (none) |\n| List filters | JIRA_LIST_FILTERS | (none) |\n| Project roles | JIRA_GET_PROJECT_ROLES | projectIdOrKey |\n| Project versions | JIRA_GET_PROJECT_VERSIONS | projectIdOrKey |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Jira Automation via Rube MCP\n\nAutomate Jira operations through Composio's Jira toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Jira connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`\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\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`\n3. If connection is not ACTIVE, follow the returned auth link to complete Jira OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Search and Filter Issues\n\n**When to use**: User wants to find issues using JQL or browse project issues\n\n**Tool sequence**:\n1. `JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST` - Search with JQL query [Required]\n2. `JIRA_GET_ISSUE` - Get full details of a specific issue [Optional]\n\n**Key parameters**:\n- `jql`: JQL query string (e.g., `project = PROJ AND status = \"In Progress\"`)\n- `maxResults`: Max results per page (default 50, max 100)\n- `startAt`: Pagination offset\n- `fields`: Array of field names to return\n- `issueIdOrKey`: Issue key like 'PROJ-123' for GET_ISSUE\n\n**Pitfalls**:\n- JQL field names are case-sensitive and must match Jira configuration\n- Custom fields use IDs like `customfield_10001`, not display names\n- Results are paginated; check `total` vs `startAt + maxResults` to continue\n\n### 2. Create and Edit Issues\n\n**When to use**: User wants to create new issues or update existing ones\n\n**Tool sequence**:\n1. `JIRA_GET_ALL_PROJECTS` - List projects to find project key [Prerequisite]\n2. `JIRA_GET_FIELDS` - Get available fields and their IDs [Prerequisite]\n3. `JIRA_CREATE_ISSUE` - Create a new issue [Required]\n4. `JIRA_EDIT_ISSUE` - Update fields on an existing issue [Optional]\n5. `JIRA_ASSIGN_ISSUE` - Assign issue to a user [Optional]\n\n**Key parameters**:\n- `project`: Project key (e.g., 'PROJ')\n- `issuetype`: Issue type name (e.g., 'Bug', 'Story', 'Task')\n- `summary`: Issue title\n- `description`: Issue description (Atlassian Document Format or plain text)\n- `issueIdOrKey`: Issue key for edits\n\n**Pitfalls**:\n- Issue types and required fields vary by project; use GET_FIELDS to check\n- Custom fields require exact field IDs, not display names\n- Description may need Atlassian Document Format (ADF) for rich content\n\n### 3. Manage Sprints and Boards\n\n**When to use**: User wants to work with agile boards, sprints, and backlogs\n\n**Tool sequence**:\n1. `JIRA_LIST_BOARDS` - List all boards [Prerequisite]\n2. `JIRA_LIST_SPRINTS` - List sprints for a board [Required]\n3. `JIRA_MOVE_ISSUE_TO_SPRINT` - Move issue to a sprint [Optional]\n4. `JIRA_CREATE_SPRINT` - Create a new sprint [Optional]\n\n**Key parameters**:\n- `boardId`: Board ID from LIST_BOARDS\n- `sprintId`: Sprint ID for move operations\n- `name`: Sprint name for creation\n- `startDate`\u002F`endDate`: Sprint dates in ISO format\n\n**Pitfalls**:\n- Boards and sprints are specific to Jira Software (not Jira Core)\n- Only one sprint can be active at a time per board\n\n### 4. Manage Comments\n\n**When to use**: User wants to add or view comments on issues\n\n**Tool sequence**:\n1. `JIRA_LIST_ISSUE_COMMENTS` - List existing comments [Optional]\n2. `JIRA_ADD_COMMENT` - Add a comment to an issue [Required]\n\n**Key parameters**:\n- `issueIdOrKey`: Issue key like 'PROJ-123'\n- `body`: Comment body (supports ADF for rich text)\n\n**Pitfalls**:\n- Comments support ADF (Atlassian Document Format) for formatting\n- Mentions use account IDs, not usernames\n\n### 5. Manage Projects and Users\n\n**When to use**: User wants to list projects, find users, or manage project roles\n\n**Tool sequence**:\n1. `JIRA_GET_ALL_PROJECTS` - List all projects [Optional]\n2. `JIRA_GET_PROJECT` - Get project details [Optional]\n3. `JIRA_FIND_USERS` \u002F `JIRA_GET_ALL_USERS` - Search for users [Optional]\n4. `JIRA_GET_PROJECT_ROLES` - List project roles [Optional]\n5. `JIRA_ADD_USERS_TO_PROJECT_ROLE` - Add user to role [Optional]\n\n**Key parameters**:\n- `projectIdOrKey`: Project key\n- `query`: Search text for FIND_USERS\n- `roleId`: Role ID for role operations\n\n**Pitfalls**:\n- User operations use account IDs (not email or display name)\n- Project roles differ from global permissions\n\n## Common Patterns\n\n### JQL Syntax\n\n**Common operators**:\n- `project = \"PROJ\"` - Filter by project\n- `status = \"In Progress\"` - Filter by status\n- `assignee = currentUser()` - Current user's issues\n- `created >= -7d` - Created in last 7 days\n- `labels = \"bug\"` - Filter by label\n- `priority = High` - Filter by priority\n- `ORDER BY created DESC` - Sort results\n\n**Combinators**:\n- `AND` - Both conditions\n- `OR` - Either condition\n- `NOT` - Negate condition\n\n### Pagination\n\n- Use `startAt` and `maxResults` parameters\n- Check `total` in response to determine remaining pages\n- Continue until `startAt + maxResults >= total`\n\n## Known Pitfalls\n\n**Field Names**:\n- Custom fields use IDs like `customfield_10001`\n- Use JIRA_GET_FIELDS to discover field IDs and names\n- Field names in JQL may differ from API field names\n\n**Authentication**:\n- Jira Cloud uses account IDs, not usernames\n- Site URL must be configured correctly in the connection\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Search issues (JQL) | JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST | jql, maxResults |\n| Get issue | JIRA_GET_ISSUE | issueIdOrKey |\n| Create issue | JIRA_CREATE_ISSUE | project, issuetype, summary |\n| Edit issue | JIRA_EDIT_ISSUE | issueIdOrKey, fields |\n| Assign issue | JIRA_ASSIGN_ISSUE | issueIdOrKey, accountId |\n| Add comment | JIRA_ADD_COMMENT | issueIdOrKey, body |\n| List comments | JIRA_LIST_ISSUE_COMMENTS | issueIdOrKey |\n| List projects | JIRA_GET_ALL_PROJECTS | (none) |\n| Get project | JIRA_GET_PROJECT | projectIdOrKey |\n| List boards | JIRA_LIST_BOARDS | (none) |\n| List sprints | JIRA_LIST_SPRINTS | boardId |\n| Move to sprint | JIRA_MOVE_ISSUE_TO_SPRINT | sprintId, issues |\n| Create sprint | JIRA_CREATE_SPRINT | name, boardId |\n| Find users | JIRA_FIND_USERS | query |\n| Get fields | JIRA_GET_FIELDS | (none) |\n| List filters | JIRA_LIST_FILTERS | (none) |\n| Project roles | JIRA_GET_PROJECT_ROLES | projectIdOrKey |\n| Project versions | JIRA_GET_PROJECT_VERSIONS | projectIdOrKey |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":23,"source":24,"date_added":25,"description":7},"critical","community","2026-02-27","main","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Fjira-automation","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Sansar35\u002Fclaude-agent --skill jira-automation",{"tool":38,"command":39},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill jira-automation",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill jira-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fjira-automation\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},".skill-source.json","REFERENCE","参考文档",374,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fjira-automation\u002F.skill-source.json",[53,60,67,74,81,89],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","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\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]