[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D7XYDGRZZ86FSSZP5RWF8A":3,"skill-same:01M7D7XYDGRZZ86FSSZP5RWF8A":70},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":5,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7D7XYDGRZZ86FSSZP5RWF8A","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.","tangyixiao\u002Ftangyixiao-skills","tangyixiao","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F115929632?v=4","01M7D582YK6A4M63CAK4CSY4EW","Tang Yixiao","01M7D582Z64DMRSYR872SR34SA",2,"MIT","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fjira\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\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","2a870f189175a48c39f5f7e26a6d93b0be9cd13b",0,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills","https:\u002F\u002Ftangyixiao.github.io\u002Ftangyixiao-skills\u002F","https:\u002F\u002Fgithub.com\u002Ftangyixiao","http:\u002F\u002Fwww.sxyz.net\u002F","I am Tang Yixiao, a student in Shaoxing No.1 High School. I am eager to learn on GitHub and contribute my part to this community.","2026-11-11 15:45:59",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add tangyixiao\u002Ftangyixiao-skills --skill jira",{"tool":40,"command":41},"bunx","bunx skills add tangyixiao\u002Ftangyixiao-skills --skill jira",{"tool":43,"command":44},"pnpm","pnpm dlx skills add tangyixiao\u002Ftangyixiao-skills --skill jira","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fjira\u002FSKILL.md",true,[48,54,58,62,66],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"INSTALL-SOURCE.json","REFERENCE","参考文档",204,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fjira\u002FINSTALL-SOURCE.json",{"path":55,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":16},"LICENSE","许可证",1072,{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"README.md",8744,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fjira\u002FREADME.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fcommands.md",4594,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fjira\u002Freferences\u002Fcommands.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fmcp.md",11894,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fjira\u002Freferences\u002Fmcp.md",[71,80,88,96,104,112],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":20},"01M7D8JK8FYBFNNAJXWD89CFH7","xlsx","Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fxlsx\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fxlsx\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":20},"01M7D8JG8ERGGQQAMX0DWCG9GR","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-shape\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":20},"01M7D8JE672GW3EHSE8EF185M4","writing-fragments","Writing, explore: mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-fragments\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-fragments\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":20},"01M7D8JBK572YDFMND8Q6CEYJW","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-for-agents\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":20},"01M7D8J5QPWEXX61EGBKYH73R8","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-clearly-and-concisely\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":20},"01M7D8J36YWC8WZS5DK5AH03CD","writing-beats","Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-beats\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-beats\u002FSKILL.md",[],[]]