[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AKHCNTCWGGARGS8MX8RAMJ":3,"skill-same:01M7AKHCNTCWGGARGS8MX8RAMJ":59},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7AKHCNTCWGGARGS8MX8RAMJ","jira",null,"Use when the user mentions Jira issues (e.g., \"PROJ-123\"), asks about tickets, wants to create\u002Fview\u002Fupdate issues, check sprint status, or manage their Jira workflow. Triggers on keywords like \"jira\", \"issue\", \"ticket\", \"sprint\", \"backlog\", or issue key patterns.","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\u002Fai-research\u002Fjira\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: jira\ndescription: Use when the user mentions Jira issues (e.g., \"PROJ-123\"), asks about tickets, wants to create\u002Fview\u002Fupdate issues, check sprint status, or manage their Jira workflow. Triggers on keywords like \"jira\", \"issue\", \"ticket\", \"sprint\", \"backlog\", or issue key patterns.\n---\n\n# Jira\n\nNatural language interaction with Jira. Supports multiple backends.\n\n## Backend Detection\n\n**Run this check first** to determine which backend to use:\n\n```\n1. Check if jira CLI is available:\n   → Run: which jira\n   → If found: USE CLI BACKEND\n\n2. If no CLI, check for Atlassian MCP:\n   → Look for mcp__atlassian__* tools\n   → If available: USE MCP BACKEND\n\n3. If neither available:\n   → GUIDE USER TO SETUP\n```\n\n| Backend | When to Use | Reference |\n|---------|-------------|-----------|\n| **CLI** | `jira` command available | `references\u002Fcommands.md` |\n| **MCP** | Atlassian MCP tools available | `references\u002Fmcp.md` |\n| **None** | Neither available | Guide to install CLI |\n\n---\n\n## Quick Reference (CLI)\n\n> Skip this section if using MCP backend.\n\n| Intent | Command |\n|--------|---------|\n| View issue | `jira issue view ISSUE-KEY` |\n| List my issues | `jira issue list -a$(jira me)` |\n| My in-progress | `jira issue list -a$(jira me) -s\"In Progress\"` |\n| Create issue | `jira issue create -tType -s\"Summary\" -b\"Description\"` |\n| Move\u002Ftransition | `jira issue move ISSUE-KEY \"State\"` |\n| Assign to me | `jira issue assign ISSUE-KEY $(jira me)` |\n| Unassign | `jira issue assign ISSUE-KEY x` |\n| Add comment | `jira issue comment add ISSUE-KEY -b\"Comment text\"` |\n| Open in browser | `jira open ISSUE-KEY` |\n| Current sprint | `jira sprint list --state active` |\n| Who am I | `jira me` |\n\n---\n\n## Quick Reference (MCP)\n\n> Skip this section if using CLI backend.\n\n| Intent | MCP Tool |\n|--------|----------|\n| Search issues | `mcp__atlassian__searchJiraIssuesUsingJql` |\n| View issue | `mcp__atlassian__getJiraIssue` |\n| Create issue | `mcp__atlassian__createJiraIssue` |\n| Update issue | `mcp__atlassian__editJiraIssue` |\n| Get transitions | `mcp__atlassian__getTransitionsForJiraIssue` |\n| Transition | `mcp__atlassian__transitionJiraIssue` |\n| Add comment | `mcp__atlassian__addCommentToJiraIssue` |\n| User lookup | `mcp__atlassian__lookupJiraAccountId` |\n| List projects | `mcp__atlassian__getVisibleJiraProjects` |\n\nSee `references\u002Fmcp.md` for full MCP patterns.\n\n---\n\n## Triggers\n\n- \"create a jira ticket\"\n- \"show me PROJ-123\"\n- \"list my tickets\"\n- \"move ticket to done\"\n- \"what's in the current sprint\"\n\n---\n\n## Issue Key Detection\n\nIssue keys follow the pattern: `[A-Z]+-[0-9]+` (e.g., PROJ-123, ABC-1).\n\nWhen a user mentions an issue key in conversation:\n- **CLI:** `jira issue view KEY` or `jira open KEY`\n- **MCP:** `mcp__atlassian__jira_get_issue` with the key\n\n---\n\n## Workflow\n\n**Creating tickets:**\n1. Research context if user references code\u002Ftickets\u002FPRs\n2. Draft ticket content\n3. Review with user\n4. Create using appropriate backend\n\n**Updating tickets:**\n1. Fetch issue details first\n2. Check status (careful with in-progress tickets)\n3. Show current vs proposed changes\n4. Get approval before updating\n5. Add comment explaining changes\n\n---\n\n## Before Any Operation\n\nAsk yourself:\n\n1. **What's the current state?** — Always fetch the issue first. Don't assume status, assignee, or fields are what user thinks they are.\n\n2. **Who else is affected?** — Check watchers, linked issues, parent epics. A \"simple edit\" might notify 10 people.\n\n3. **Is this reversible?** — Transitions may have one-way gates. Some workflows require intermediate states. Description edits have no undo.\n\n4. **Do I have the right identifiers?** — Issue keys, transition IDs, account IDs. Display names don't work for assignment (MCP).\n\n---\n\n## NEVER\n\n- **NEVER transition without fetching current status** — Workflows may require intermediate states. \"To Do\" → \"Done\" might fail silently if \"In Progress\" is required first.\n\n- **NEVER assign using display name (MCP)** — Only account IDs work. Always call `lookupJiraAccountId` first, or assignment silently fails.\n\n- **NEVER edit description without showing original** — Jira has no undo. User must see what they're replacing.\n\n- **NEVER use `--no-input` without all required fields (CLI)** — Fails silently with cryptic errors. Check project's required fields first.\n\n- **NEVER assume transition names are universal** — \"Done\", \"Closed\", \"Complete\" vary by project. Always get available transitions first.\n\n- **NEVER bulk-modify without explicit approval** — Each ticket change notifies watchers. 10 edits = 10 notification storms.\n\n---\n\n## Safety\n\n- Always show the command\u002Ftool call before running it\n- Always get approval before modifying tickets\n- Preserve original information when editing\n- Verify updates after applying\n- Always surface authentication issues clearly so the user can resolve them\n\n---\n\n## No Backend Available\n\nIf neither CLI nor MCP is available, guide the user:\n\n```\nTo use Jira, you need one of:\n\n1. **jira CLI** (recommended):\n   https:\u002F\u002Fgithub.com\u002Fankitpokhrel\u002Fjira-cli\n\n   Install: brew install ankitpokhrel\u002Fjira-cli\u002Fjira-cli\n   Setup:   jira init\n\n2. **Atlassian MCP**:\n   Configure in your MCP settings with Atlassian credentials.\n```\n\n---\n\n## Deep Dive\n\n**LOAD reference when:**\n- Creating issues with complex fields or multi-line content\n- Building JQL queries beyond simple filters\n- Troubleshooting errors or authentication issues\n- Working with transitions, linking, or sprints\n\n**Do NOT load reference for:**\n- Simple view\u002Flist operations (Quick Reference above is sufficient)\n- Basic status checks (`jira issue view KEY`)\n- Opening issues in browser\n\n| Task | Load Reference? |\n|------|-----------------|\n| View single issue | No |\n| List my tickets | No |\n| Create with description | **Yes** — CLI needs `\u002Ftmp` pattern |\n| Transition issue | **Yes** — need transition ID workflow |\n| JQL search | **Yes** — for complex queries |\n| Link issues | **Yes** — MCP limitation, need script |\n\nReferences:\n- CLI patterns: `references\u002Fcommands.md`\n- MCP patterns: `references\u002Fmcp.md`\n","# Jira\n\nNatural language interaction with Jira. Supports multiple backends.\n\n## Backend Detection\n\n**Run this check first** to determine which backend to use:\n\n```\n1. Check if jira CLI is available:\n   → Run: which jira\n   → If found: USE CLI BACKEND\n\n2. If no CLI, check for Atlassian MCP:\n   → Look for mcp__atlassian__* tools\n   → If available: USE MCP BACKEND\n\n3. If neither available:\n   → GUIDE USER TO SETUP\n```\n\n| Backend | When to Use | Reference |\n|---------|-------------|-----------|\n| **CLI** | `jira` command available | `references\u002Fcommands.md` |\n| **MCP** | Atlassian MCP tools available | `references\u002Fmcp.md` |\n| **None** | Neither available | Guide to install CLI |\n\n---\n\n## Quick Reference (CLI)\n\n> Skip this section if using MCP backend.\n\n| Intent | Command |\n|--------|---------|\n| View issue | `jira issue view ISSUE-KEY` |\n| List my issues | `jira issue list -a$(jira me)` |\n| My in-progress | `jira issue list -a$(jira me) -s\"In Progress\"` |\n| Create issue | `jira issue create -tType -s\"Summary\" -b\"Description\"` |\n| Move\u002Ftransition | `jira issue move ISSUE-KEY \"State\"` |\n| Assign to me | `jira issue assign ISSUE-KEY $(jira me)` |\n| Unassign | `jira issue assign ISSUE-KEY x` |\n| Add comment | `jira issue comment add ISSUE-KEY -b\"Comment text\"` |\n| Open in browser | `jira open ISSUE-KEY` |\n| Current sprint | `jira sprint list --state active` |\n| Who am I | `jira me` |\n\n---\n\n## Quick Reference (MCP)\n\n> Skip this section if using CLI backend.\n\n| Intent | MCP Tool |\n|--------|----------|\n| Search issues | `mcp__atlassian__searchJiraIssuesUsingJql` |\n| View issue | `mcp__atlassian__getJiraIssue` |\n| Create issue | `mcp__atlassian__createJiraIssue` |\n| Update issue | `mcp__atlassian__editJiraIssue` |\n| Get transitions | `mcp__atlassian__getTransitionsForJiraIssue` |\n| Transition | `mcp__atlassian__transitionJiraIssue` |\n| Add comment | `mcp__atlassian__addCommentToJiraIssue` |\n| User lookup | `mcp__atlassian__lookupJiraAccountId` |\n| List projects | `mcp__atlassian__getVisibleJiraProjects` |\n\nSee `references\u002Fmcp.md` for full MCP patterns.\n\n---\n\n## Triggers\n\n- \"create a jira ticket\"\n- \"show me PROJ-123\"\n- \"list my tickets\"\n- \"move ticket to done\"\n- \"what's in the current sprint\"\n\n---\n\n## Issue Key Detection\n\nIssue keys follow the pattern: `[A-Z]+-[0-9]+` (e.g., PROJ-123, ABC-1).\n\nWhen a user mentions an issue key in conversation:\n- **CLI:** `jira issue view KEY` or `jira open KEY`\n- **MCP:** `mcp__atlassian__jira_get_issue` with the key\n\n---\n\n## Workflow\n\n**Creating tickets:**\n1. Research context if user references code\u002Ftickets\u002FPRs\n2. Draft ticket content\n3. Review with user\n4. Create using appropriate backend\n\n**Updating tickets:**\n1. Fetch issue details first\n2. Check status (careful with in-progress tickets)\n3. Show current vs proposed changes\n4. Get approval before updating\n5. Add comment explaining changes\n\n---\n\n## Before Any Operation\n\nAsk yourself:\n\n1. **What's the current state?** — Always fetch the issue first. Don't assume status, assignee, or fields are what user thinks they are.\n\n2. **Who else is affected?** — Check watchers, linked issues, parent epics. A \"simple edit\" might notify 10 people.\n\n3. **Is this reversible?** — Transitions may have one-way gates. Some workflows require intermediate states. Description edits have no undo.\n\n4. **Do I have the right identifiers?** — Issue keys, transition IDs, account IDs. Display names don't work for assignment (MCP).\n\n---\n\n## NEVER\n\n- **NEVER transition without fetching current status** — Workflows may require intermediate states. \"To Do\" → \"Done\" might fail silently if \"In Progress\" is required first.\n\n- **NEVER assign using display name (MCP)** — Only account IDs work. Always call `lookupJiraAccountId` first, or assignment silently fails.\n\n- **NEVER edit description without showing original** — Jira has no undo. User must see what they're replacing.\n\n- **NEVER use `--no-input` without all required fields (CLI)** — Fails silently with cryptic errors. Check project's required fields first.\n\n- **NEVER assume transition names are universal** — \"Done\", \"Closed\", \"Complete\" vary by project. Always get available transitions first.\n\n- **NEVER bulk-modify without explicit approval** — Each ticket change notifies watchers. 10 edits = 10 notification storms.\n\n---\n\n## Safety\n\n- Always show the command\u002Ftool call before running it\n- Always get approval before modifying tickets\n- Preserve original information when editing\n- Verify updates after applying\n- Always surface authentication issues clearly so the user can resolve them\n\n---\n\n## No Backend Available\n\nIf neither CLI nor MCP is available, guide the user:\n\n```\nTo use Jira, you need one of:\n\n1. **jira CLI** (recommended):\n   https:\u002F\u002Fgithub.com\u002Fankitpokhrel\u002Fjira-cli\n\n   Install: brew install ankitpokhrel\u002Fjira-cli\u002Fjira-cli\n   Setup:   jira init\n\n2. **Atlassian MCP**:\n   Configure in your MCP settings with Atlassian credentials.\n```\n\n---\n\n## Deep Dive\n\n**LOAD reference when:**\n- Creating issues with complex fields or multi-line content\n- Building JQL queries beyond simple filters\n- Troubleshooting errors or authentication issues\n- Working with transitions, linking, or sprints\n\n**Do NOT load reference for:**\n- Simple view\u002Flist operations (Quick Reference above is sufficient)\n- Basic status checks (`jira issue view KEY`)\n- Opening issues in browser\n\n| Task | Load Reference? |\n|------|-----------------|\n| View single issue | No |\n| List my tickets | No |\n| Create with description | **Yes** — CLI needs `\u002Ftmp` pattern |\n| Transition issue | **Yes** — need transition ID workflow |\n| JQL search | **Yes** — for complex queries |\n| Link issues | **Yes** — MCP limitation, need script |\n\nReferences:\n- CLI patterns: `references\u002Fcommands.md`\n- MCP patterns: `references\u002Fmcp.md`\n",{"name":5,"description":7},"main","51493f354fd03e3f941d4df7fd64c0b8c7a2632d","skills\u002Fai-research\u002Fjira","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":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill jira",{"tool":37,"command":38},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill jira",{"tool":40,"command":41},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill jira","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fai-research\u002Fjira\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"README.md","REFERENCE","参考文档",8744,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fai-research\u002Fjira\u002FREADME.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fcommands.md",4594,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fai-research\u002Fjira\u002Freferences\u002Fcommands.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fmcp.md",11894,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fai-research\u002Fjira\u002Freferences\u002Fmcp.md",[60,67,76,83,90,97],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"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",[],[]]