[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CGE8GYJCFAEPP9JATEGWEH":3,"skill-same:01M6CGE8GYJCFAEPP9JATEGWEH":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6CGE8GYJCFAEPP9JATEGWEH","jira-brief",null,"Use when mms-planning delegates ticket identification or a brief, and when the engineer asks to understand a Jira ticket. Write .briefs\u002F\u003CISSUE-KEY>.md with the Goal, Decisions Already Made, Open Decisions, and Code Surfaces sections. Name the path in chat. Do not paste the file or write to Jira. Do not edit product code, and do not say that in chat.","MetaMask\u002Fskills","MetaMask","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11744586?v=4","01M6CGATQAN8ZP8HWEZH2379WJ","01M6CGATVJDE1ZMSRM20CFJ5S8",25,"MIT","https:\u002F\u002Fgithub.com\u002FMetaMask\u002Fskills\u002Fblob\u002Fmain\u002Fdomains\u002Fplanning\u002Fskills\u002Fjira-brief\u002Fskill.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"jira brief","jira","brief","delegates","with","chat","when","ticket","identification","code","file","decisions","use","open","engineer","goal","planning","product","say","do","2026-11-10 10:12:30",false,"---\nname: jira-brief\ndescription: >-\n  Use when mms-planning delegates ticket identification or a brief, and\n  when the engineer asks to understand a Jira ticket. Write\n  .briefs\u002F\u003CISSUE-KEY>.md with the Goal, Decisions Already Made, Open\n  Decisions, and Code Surfaces sections. Name the path in chat. Do not paste the\n  file or write to Jira. Do not edit product code, and do not say that in chat.\nmaturity: experimental\n---\n\n# Jira brief\n\nInstalled name: `mms-jira-brief`. `mms-planning` calls it for ticket identification. The engineer can invoke it directly. Do not edit product code, and do not say that in chat. Do not write to Jira. Do not embed a Mermaid diagram of this procedure, and do not put one in `.briefs\u002F`.\n\n## When to use\n\n- `mms-planning` calls this skill.\n- The engineer asks to understand a Jira ticket.\n\n## Workflow\n\n1. When the engineer invokes this skill directly and there is no browse URL and no key, ask which ticket. Then continue with the answer. When `mms-planning` delegates and there is no candidate browse URL or key, return no ticket identified. Do not ask.\n2. A browse URL whose path contains `\u002Fbrowse\u002F\u003CKEY>` is a ticket. Do not ask.\n3. A bare `\u003CPROJECT>-\u003Cnumber>` token is not a ticket from the pattern alone. `MCWP` is the mobile platform project, not the only valid project. There is no project allowlist.\n4. Ignore tokens that are clearly not Jira issues, without a question. Examples: `EIP-7702`, `CAIP-19`, and `HIP-3`.\n5. A bare token is a ticket when Jira resolves it, or when the engineer confirms it. When no URL is present and a token might be a Jira issue but Jira does not resolve it, or the lookup is inconclusive, infer from surrounding words such as ticket, Jira, or issue. If still unsure, ask whether that token is a Jira issue. Yes continues the brief flow. No treats it as not a ticket.\n6. Not a ticket: stop. Do not write a file.\n7. Each resolved key produces one `.briefs\u002F\u003CISSUE-KEY>.md`. Several keys produce one file each. `.briefs\u002F` is local and not team-shared storage. Do not stage it.\n8. If `.briefs\u002F\u003CISSUE-KEY>.md` already exists and the engineer did not ask to regenerate it, open the issue and compare its updated time with the `Jira updated:` line in the brief. A failure file is never a fresh brief. It has no `Jira updated:` line. If the times match, read the file and do not regenerate it. If they differ, or the line is missing, regenerate the file. If the issue does not open, read the existing file and say that freshness was not checked.\n9. Otherwise open the issue in Jira. If it opens, write the file with these headings, in this order: `## Goal`, `## Decisions Already Made`, `## Open Decisions`, `## Code Surfaces`. End the file with `Jira updated:` and the updated time Jira returned. If it does not open, do not block. Write `.briefs\u002F\u003CKEY>.md` that records the key, the failure, and any ticket text the user already provided. Say what was missing. A failure file has no `Jira updated:` line.\n10. Do not copy secrets, tokens, credentials, or customer data into the file.\n11. In chat, name the path. Do not paste the file. Do not write to Jira. Do not say that code will not change.\n\nWhen `mms-planning` delegates and no ticket is identified, return no ticket identified and stop. Do not ask for a ticket. Do not suggest creating one. `mms-planning` then continues. A revert does not call this skill.\n","# Jira brief\n\nInstalled name: `mms-jira-brief`. `mms-planning` calls it for ticket identification. The engineer can invoke it directly. Do not edit product code, and do not say that in chat. Do not write to Jira. Do not embed a Mermaid diagram of this procedure, and do not put one in `.briefs\u002F`.\n\n## When to use\n\n- `mms-planning` calls this skill.\n- The engineer asks to understand a Jira ticket.\n\n## Workflow\n\n1. When the engineer invokes this skill directly and there is no browse URL and no key, ask which ticket. Then continue with the answer. When `mms-planning` delegates and there is no candidate browse URL or key, return no ticket identified. Do not ask.\n2. A browse URL whose path contains `\u002Fbrowse\u002F\u003CKEY>` is a ticket. Do not ask.\n3. A bare `\u003CPROJECT>-\u003Cnumber>` token is not a ticket from the pattern alone. `MCWP` is the mobile platform project, not the only valid project. There is no project allowlist.\n4. Ignore tokens that are clearly not Jira issues, without a question. Examples: `EIP-7702`, `CAIP-19`, and `HIP-3`.\n5. A bare token is a ticket when Jira resolves it, or when the engineer confirms it. When no URL is present and a token might be a Jira issue but Jira does not resolve it, or the lookup is inconclusive, infer from surrounding words such as ticket, Jira, or issue. If still unsure, ask whether that token is a Jira issue. Yes continues the brief flow. No treats it as not a ticket.\n6. Not a ticket: stop. Do not write a file.\n7. Each resolved key produces one `.briefs\u002F\u003CISSUE-KEY>.md`. Several keys produce one file each. `.briefs\u002F` is local and not team-shared storage. Do not stage it.\n8. If `.briefs\u002F\u003CISSUE-KEY>.md` already exists and the engineer did not ask to regenerate it, open the issue and compare its updated time with the `Jira updated:` line in the brief. A failure file is never a fresh brief. It has no `Jira updated:` line. If the times match, read the file and do not regenerate it. If they differ, or the line is missing, regenerate the file. If the issue does not open, read the existing file and say that freshness was not checked.\n9. Otherwise open the issue in Jira. If it opens, write the file with these headings, in this order: `## Goal`, `## Decisions Already Made`, `## Open Decisions`, `## Code Surfaces`. End the file with `Jira updated:` and the updated time Jira returned. If it does not open, do not block. Write `.briefs\u002F\u003CKEY>.md` that records the key, the failure, and any ticket text the user already provided. Say what was missing. A failure file has no `Jira updated:` line.\n10. Do not copy secrets, tokens, credentials, or customer data into the file.\n11. In chat, name the path. Do not paste the file. Do not write to Jira. Do not say that code will not change.\n\nWhen `mms-planning` delegates and no ticket is identified, return no ticket identified and stop. Do not ask for a ticket. Do not suggest creating one. `mms-planning` then continues. A revert does not call this skill.\n",{"name":5,"maturity":43,"description":7},"experimental","main","d1f7d69b18eea97c7252269f0e3d930765a6037d","domains\u002Fplanning\u002Fskills\u002Fjira-brief",11,"https:\u002F\u002Fgithub.com\u002FMetaMask\u002Fskills","https:\u002F\u002Fgithub.com\u002FMetaMask","https:\u002F\u002Fmetamask.io","MetaMask brings Ethereum to your web browser","2026-11-11 08:15:52",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add MetaMask\u002Fskills --skill jira-brief",{"tool":59,"command":60},"bunx","bunx skills add MetaMask\u002Fskills --skill jira-brief",{"tool":62,"command":63},"pnpm","pnpm dlx skills add MetaMask\u002Fskills --skill jira-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMetaMask\u002Fskills\u002Fblob\u002Fmain\u002Fdomains\u002Fplanning\u002Fskills\u002Fjira-brief\u002Fskill.md",true,[67,73],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"repos\u002Fmetamask-extension.md","REFERENCE","参考文档",154,"https:\u002F\u002Fgithub.com\u002FMetaMask\u002Fskills\u002Fblob\u002Fmain\u002Fdomains\u002Fplanning\u002Fskills\u002Fjira-brief\u002Frepos\u002Fmetamask-extension.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"repos\u002Fmetamask-mobile.md",148,"https:\u002F\u002Fgithub.com\u002FMetaMask\u002Fskills\u002Fblob\u002Fmain\u002Fdomains\u002Fplanning\u002Fskills\u002Fjira-brief\u002Frepos\u002Fmetamask-mobile.md",[78,105,124,131,165,190],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":38},"01M70PKJH3WSTFMSA8VYQWNDW9","recipe-performance","Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold\u002Fwarm\u002Fbackground-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout\u002Fpaint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.","https:\u002F\u002Fgithub.com\u002FMetaMask\u002Fskills\u002Fblob\u002Fmain\u002Fdomains\u002Fagentic\u002Fskills\u002Frecipe-performance\u002Fskill.md",[],[85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104],"performance","recipe performance","recipe","app","cold","critical","analysis","tasks","react","browser","layout","screen","network","metamask","flow","recipes","deterministic","harness","mm","sentry",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":38},"01M6CGJ7AEJCZSRGF3PBE6EWBG","x402-payments","Build x402 payment flows using MetaMask Smart Accounts Kit, machine to machine payments over HTTP with ERC-7710 delegations and ERC-7715 Advanced Permissions","https:\u002F\u002Fgithub.com\u002FMetaMask\u002Fskills\u002Fblob\u002Fmain\u002Fdomains\u002Fweb3-tools\u002Fskills\u002Fx402-payments\u002Fskill.md",[],[112,113,114,115,116,117,118,22,119,120,121,122,98,123],"payments","x402 payments","x402","permissions","smart accounts kit","http","build","payment","advanced","flows","machine","kit",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":38},"01M6CGJ4AEKJZJWJ704SZTWQ5T","smart-accounts-kit","Build dApps with MetaMask Smart Accounts Kit — ERC-4337 smart accounts, delegations, and Advanced Permissions (ERC-7715)","https:\u002F\u002Fgithub.com\u002FMetaMask\u002Fskills\u002Fblob\u002Fmain\u002Fdomains\u002Fweb3-tools\u002Fskills\u002Fsmart-accounts-kit\u002Fskill.md",[],[116,123,115,118,22,120,98],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":142,"publishedAt":38},"01M6CGJ11KGB6862Z1ADYTMKYZ","oh-my-opencode","Multi-agent orchestration plugin for OpenCode. Use when the user wants to install, configure, or operate oh-my-opencode — including agent delegation, ultrawork mode, Prometheus planning, background tasks, category-based task routing, model resolution, tmux integration, or any oh-my-opencode feature. Covers installation, configuration, all agents (Sisyphus, Oracle, Librarian, Explore, Atlas, Prometheus, Metis, Momus), all categories, slash commands, hooks, skills, MCPs, and troubleshooting.","https:\u002F\u002Fgithub.com\u002FMetaMask\u002Fskills\u002Fblob\u002Fmain\u002Fdomains\u002Fweb3-tools\u002Fskills\u002Foh-my-opencode\u002Fskill.md",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":140,"taxonomyTypeDesc":141},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[143,144,145,146,147,148,149,150,151,152,153,154,27,92,155,156,157,158,159,34,30,160,161,162,163,164,24],"opencode","oh my opencode","my","model","explore","hooks","delegation","librarian","agent orchestration","oracle","orchestration","configure","ultrawork","install","multi-agent","tmux","prometheus","categories","operate","mode","metis","momus",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":38},"01M6CGHY9SVTXK2DK18H794EHE","gator-cli","Use when you need to operate the @metamask\u002Fgator-cli to initialize profiles, upgrade EOA to EIP-7702, grant, redeem, and revoke ERC-7710 delegations, or inspect balances and delegations. Covers commands, required flags, grant scopes, redeem action types, configuration locations, and common usage flows.","https:\u002F\u002Fgithub.com\u002FMetaMask\u002Fskills\u002Fblob\u002Fmain\u002Fdomains\u002Fweb3-tools\u002Fskills\u002Fgator-cli\u002Fskill.md",[],[172,173,174,175,176,156,177,30,178,179,180,161,181,182,183,184,121,185,123,186,24,187,188,189],"cli","gator cli","initialize","https","node","flags","docs","configuration","common","usage","types","balances","inspect","profiles","upgrade","you","io","commands",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":201,"publishedAt":38},"01M6CGHVB2A8SMD9X84ZTH9RHV","ui-development","UI component development standards for MetaMask clients: the strict design-system-first component hierarchy, availability checks before building custom components, styling with design tokens, and required imports. Use when building, restyling, or reviewing any UI component, or when choosing between a design-system, component-library, or custom component.","https:\u002F\u002Fgithub.com\u002FMetaMask\u002Fskills\u002Fblob\u002Fmain\u002Fdomains\u002Fui\u002Fskills\u002Fui-development\u002Fskill.md",[196],{"categoryNo":197,"categoryName":198,"taxonomyType":199,"taxonomyTypeDesc":200},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[202,203,204,205,206,207,208,209,210,211,212,213,214,30,215,216,217,218,219,220,221,222,24,22,223,224],"development","ui development","ui","standards","component","first","system","before building","ui component","design","design tokens","design-system","styling","library","components","availability","for","component development","tokens","custom","true","hierarchy","imports"]