[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718KG3QJ4PNKMBFKC41JSPV":3,"skill-same:01M718KG3QJ4PNKMBFKC41JSPV":76},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":14,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M718KG3QJ4PNKMBFKC41JSPV","cc-bug-report",null,"File a bug report against Claude Code (anthropics\u002Fclaude-code on GitHub), after checking that it hasn't already been reported. Use when the user wants to \"report a Claude Code bug\", \"file an issue with Anthropic\", \"open a bug on claude-code\", or describes Claude Code (the CLI, harness, tools, hooks, plugins, MCP handling) misbehaving. Searches open and closed issues first, offers to comment on a match, and files the issue through Anthropic's live bug_report form only when nothing matches. Not for complaints about what the model said; that is a model-behavior report.","danielrosehill\u002FVendor-Liaison","danielrosehill","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F40233203?v=4","01M718KBPNC6F07QGG856HSH3G","Daniel Rosehill","01M718KBQR1KS2W899YB6JGHSH",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdanielrosehill\u002FVendor-Liaison\u002Fblob\u002Fmaster\u002Fskills\u002Fcc-bug-report\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"report","bug","cc","bug report","cc bug report","with","code","file","when","use","MCP","files","only","open","issues","hooks","for","model","form","harness","2026-11-10 10:12:30",false,"---\nname: cc-bug-report\ndescription: File a bug report against Claude Code (anthropics\u002Fclaude-code on GitHub), after checking that it hasn't already been reported. Use when the user wants to \"report a Claude Code bug\", \"file an issue with Anthropic\", \"open a bug on claude-code\", or describes Claude Code (the CLI, harness, tools, hooks, plugins, MCP handling) misbehaving. Searches open and closed issues first, offers to comment on a match, and files the issue through Anthropic's live bug_report form only when nothing matches. Not for complaints about what the model said; that is a model-behavior report.\n---\n\n# Claude Code bug report\n\nTarget: `anthropics\u002Fclaude-code`. Read `\u003Cplugin-root>\u002Fvendors\u002Fclaude-code\u002Fvendor.json` and `reporting.md` there (`\u003Cplugin-root>` is `${CLAUDE_PLUGIN_ROOT}` in Claude Code)\nfirst. It covers the channels, the form fields and how the repo's duplicate bot behaves.\nIf `CLAUDE_PLUGIN_ROOT` is unset (the skill was loaded on its own), the same facts are\nsummarised here.\n\n## 1. Pin down the bug\n\nFrom the conversation, get:\n- the symptom;\n- what should have happened;\n- steps to reproduce;\n- any exact error text.\n\nAsk only for what is missing, in one batch. If the user has described more than one bug,\neach one gets its own report.\n\nCollect the environment yourself rather than asking:\n\n```bash\nclaude --version\nnpm view @anthropic-ai\u002Fclaude-code version   # latest release\nuname -srm; echo \"$SHELL\"; echo \"${TERM_PROGRAM:-$TERM}\"\n```\n\nIf the installed version is behind, say so. The form's preflight asks you to confirm you're\non the latest version, so suggest updating and reproducing again before filing.\n\n## 2. Search for duplicates (always, before drafting)\n\nSearch open **and** closed issues, without a label filter. Run at least three phrasings:\nthe symptom, the feature or setting involved, and the exact error string.\n\n```bash\ngh search issues --repo anthropics\u002Fclaude-code \"\u003Ckeywords>\" --limit 20 \\\n  --json number,title,state,url,updatedAt,commentsCount\n```\n\nOpen the most likely two or three (`gh issue view \u003Cn> --repo anthropics\u002Fclaude-code\n--comments`) and compare their bodies, not just the titles. `gh` doesn't show why a closed\nissue was closed; get that with `gh api repos\u002Fanthropics\u002Fclaude-code\u002Fissues\u002F\u003Cn> -q .state_reason`\n(`completed`, `not_planned` or `duplicate`). Then decide:\n\n| Finding | Action |\n|---|---|\n| An open issue describes the same bug | Don't file. Give the link and offer a comment adding what is new: version, platform, reproduction, impact. A 👍 on the issue alone is also fine. |\n| Closed as completed, but the bug is back | File a new issue that links the old one and says it's a regression. |\n| Closed as a duplicate | Follow the link to the issue it was closed in favour of, and treat that one as the match. |\n| Closed as not planned | Show it to the user. Re-filing usually goes nowhere. |\n| Nothing matches | Go on to step 3. |\n\nWhen the user says \"file it\", that covers the text of the report, not filing a duplicate.\nIf a match exists, show it before doing anything.\n\n## 3. Draft from the live form\n\n```bash\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fanthropics\u002Fclaude-code\u002Fmain\u002F.github\u002FISSUE_TEMPLATE\u002Fbug_report.yml\n```\n\nBuild the body from whatever fields the form declares now:\n- Skip `type: markdown` items.\n- Each other item becomes `### {label}` followed by its value, in the form's order.\n- Checkboxes are written `- [x] text`.\n- Use the option text verbatim for dropdowns.\n- Write `_No response_` for optional fields left empty.\n- Wrap anything with `render: shell` in a code fence.\n\nThe title is `[BUG] ` plus a specific one-line summary, under about 90 characters.\n\nOnly tick a preflight box if it's true. The search in step 2 makes the first one true.\n\nBefore showing the draft, remove secrets and personal detail:\n- tokens and keys;\n- email addresses;\n- internal hostnames and IPs;\n- home-directory usernames (write `~\u002F`).\n\nTell the user what you removed.\n\n## 4. Confirm, then file\n\nShow the title, the full body and the target repo, and wait for approval. Then:\n\n```bash\ngh issue create --repo anthropics\u002Fclaude-code --title \"$TITLE\" --body-file \"$BODY_FILE\"\n```\n\nDon't pass `--label`, because outside contributors can't set labels. The form's `bug` label\nis **not** applied either: issue-form labels are added only when the form is submitted in\nthe browser, not through `gh issue create` (observed 2026-10-22 on #104378, which arrived\nwith no labels). Anthropic's triage labels it. Report the issue URL.\n\n## 5. After filing\n\nThe repo's bot may post a \"possible duplicate\" comment within minutes. It closes the issue\nafter 3 days unless someone comments afterwards or the issue's author puts a 👎 on the bot\ncomment. Tell the user this. If they think the flag is wrong, the 👎 and a short comment\nexplaining the difference keep the issue open.\n","# Claude Code bug report\n\nTarget: `anthropics\u002Fclaude-code`. Read `\u003Cplugin-root>\u002Fvendors\u002Fclaude-code\u002Fvendor.json` and `reporting.md` there (`\u003Cplugin-root>` is `${CLAUDE_PLUGIN_ROOT}` in Claude Code)\nfirst. It covers the channels, the form fields and how the repo's duplicate bot behaves.\nIf `CLAUDE_PLUGIN_ROOT` is unset (the skill was loaded on its own), the same facts are\nsummarised here.\n\n## 1. Pin down the bug\n\nFrom the conversation, get:\n- the symptom;\n- what should have happened;\n- steps to reproduce;\n- any exact error text.\n\nAsk only for what is missing, in one batch. If the user has described more than one bug,\neach one gets its own report.\n\nCollect the environment yourself rather than asking:\n\n```bash\nclaude --version\nnpm view @anthropic-ai\u002Fclaude-code version   # latest release\nuname -srm; echo \"$SHELL\"; echo \"${TERM_PROGRAM:-$TERM}\"\n```\n\nIf the installed version is behind, say so. The form's preflight asks you to confirm you're\non the latest version, so suggest updating and reproducing again before filing.\n\n## 2. Search for duplicates (always, before drafting)\n\nSearch open **and** closed issues, without a label filter. Run at least three phrasings:\nthe symptom, the feature or setting involved, and the exact error string.\n\n```bash\ngh search issues --repo anthropics\u002Fclaude-code \"\u003Ckeywords>\" --limit 20 \\\n  --json number,title,state,url,updatedAt,commentsCount\n```\n\nOpen the most likely two or three (`gh issue view \u003Cn> --repo anthropics\u002Fclaude-code\n--comments`) and compare their bodies, not just the titles. `gh` doesn't show why a closed\nissue was closed; get that with `gh api repos\u002Fanthropics\u002Fclaude-code\u002Fissues\u002F\u003Cn> -q .state_reason`\n(`completed`, `not_planned` or `duplicate`). Then decide:\n\n| Finding | Action |\n|---|---|\n| An open issue describes the same bug | Don't file. Give the link and offer a comment adding what is new: version, platform, reproduction, impact. A 👍 on the issue alone is also fine. |\n| Closed as completed, but the bug is back | File a new issue that links the old one and says it's a regression. |\n| Closed as a duplicate | Follow the link to the issue it was closed in favour of, and treat that one as the match. |\n| Closed as not planned | Show it to the user. Re-filing usually goes nowhere. |\n| Nothing matches | Go on to step 3. |\n\nWhen the user says \"file it\", that covers the text of the report, not filing a duplicate.\nIf a match exists, show it before doing anything.\n\n## 3. Draft from the live form\n\n```bash\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fanthropics\u002Fclaude-code\u002Fmain\u002F.github\u002FISSUE_TEMPLATE\u002Fbug_report.yml\n```\n\nBuild the body from whatever fields the form declares now:\n- Skip `type: markdown` items.\n- Each other item becomes `### {label}` followed by its value, in the form's order.\n- Checkboxes are written `- [x] text`.\n- Use the option text verbatim for dropdowns.\n- Write `_No response_` for optional fields left empty.\n- Wrap anything with `render: shell` in a code fence.\n\nThe title is `[BUG] ` plus a specific one-line summary, under about 90 characters.\n\nOnly tick a preflight box if it's true. The search in step 2 makes the first one true.\n\nBefore showing the draft, remove secrets and personal detail:\n- tokens and keys;\n- email addresses;\n- internal hostnames and IPs;\n- home-directory usernames (write `~\u002F`).\n\nTell the user what you removed.\n\n## 4. Confirm, then file\n\nShow the title, the full body and the target repo, and wait for approval. Then:\n\n```bash\ngh issue create --repo anthropics\u002Fclaude-code --title \"$TITLE\" --body-file \"$BODY_FILE\"\n```\n\nDon't pass `--label`, because outside contributors can't set labels. The form's `bug` label\nis **not** applied either: issue-form labels are added only when the form is submitted in\nthe browser, not through `gh issue create` (observed 2026-10-22 on #104378, which arrived\nwith no labels). Anthropic's triage labels it. Report the issue URL.\n\n## 5. After filing\n\nThe repo's bot may post a \"possible duplicate\" comment within minutes. It closes the issue\nafter 3 days unless someone comments afterwards or the issue's author puts a 👎 on the bot\ncomment. Tell the user this. If they think the flag is wrong, the 👎 and a short comment\nexplaining the difference keep the issue open.\n",{"name":5,"description":7},"master","e504fb5fc47e6cac00f2fa2bb0dced5951092a9b","skills\u002Fcc-bug-report","https:\u002F\u002Fgithub.com\u002Fdanielrosehill\u002FVendor-Liaison","https:\u002F\u002Fgithub.com\u002Fdanielrosehill","https:\u002F\u002Fwww.danielrosehill.com","Focus: Agentic AI, MCP, and workflow automation (esp. voice assisted).  Exploring: multiagent use-cases for AI & geopol sims. GH activity: Claude assisted.","2026-10-23 04:48:18",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add danielrosehill\u002FVendor-Liaison --skill cc-bug-report",{"tool":68,"command":69},"bunx","bunx skills add danielrosehill\u002FVendor-Liaison --skill cc-bug-report",{"tool":71,"command":72},"pnpm","pnpm dlx skills add danielrosehill\u002FVendor-Liaison --skill cc-bug-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielrosehill\u002FVendor-Liaison\u002Fblob\u002Fmaster\u002Fskills\u002Fcc-bug-report\u002FSKILL.md",true,[],[77,101,121,138,150,168],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":49},"01M718M5YMYBJJVPS8KA4N8KCB","vendor-preferences","Record the user's own preferences for contacting a vendor — which channel they prefer for bugs, feature requests or support, channels to avoid, private addresses, and personal contacts at the company (a developer they know, an account manager, a WhatsApp number, someone met in person). Use when the user says \"I prefer to email X\", \"don't post X stuff on Reddit\", \"I know someone at X\", \"for X feature requests go to …\", or \"remember that for X …\".","https:\u002F\u002Fgithub.com\u002Fdanielrosehill\u002FVendor-Liaison\u002Fblob\u002Fmaster\u002Fskills\u002Fvendor-preferences\u002FSKILL.md",[],[84,85,86,87,88,89,90,91,92,45,93,38,37,94,95,96,97,98,99,100],"preferences","vendor preferences","vendor","account manager","remember","which","bugs","feature","email","company","number","channels","contacts","record","post","reddit","requests",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":49},"01M718M31X6ZD6KYH17SB3VPG9","security-disclosure","Disclose a security vulnerability to a software vendor responsibly, through a private channel only — bug-bounty program, security.txt contact, security@ address, or a trusted contact at the company — never a public tracker, forum or social post. Use when the user has found a vulnerability, data exposure, auth bypass, secret leak or other security flaw in someone else's product and wants to report it.","https:\u002F\u002Fgithub.com\u002Fdanielrosehill\u002FVendor-Liaison\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity-disclosure\u002FSKILL.md",[],[108,109,110,111,112,93,113,41,114,38,37,115,116,117,98,118,119,86,120,29],"security disclosure","security","never","bug-bounty","auth","social","social post","security vulnerability","program","vulnerability","product","tracker","at",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":49},"01M718M002DQVERENHJ4NZ8VVJ","route","Work out where to send something to a software vendor — a bug report, feature request, security vulnerability, support question or general feedback — taking the vendor's own channels and the user's personal preferences and contacts into account. Use when the user asks \"where do I report this to X\", \"how do I request a feature from X\", \"who do I tell about this bug\", or before any of the report, security-disclosure or vendor-specific filing skills.","https:\u002F\u002Fgithub.com\u002Fdanielrosehill\u002FVendor-Liaison\u002Fblob\u002Fmaster\u002Fskills\u002Froute\u002FSKILL.md",[],[123,128,129,91,130,131,132,133,84,38,37,115,117,95,96,134,135,136,86,137],"do","feedback","send","filing","general","question","work","how","support","request",{"skillNo":139,"name":29,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":144,"publishedAt":49},"01M718KX5ENS7DTKN9B2X0Z1DB","Send a bug report, feature request, support question or feedback to a software vendor through the right channel — email, GitHub issue, forum or subreddit post, contact form, in-app form, or a message to a personal contact at the company — after checking it hasn't already been reported. Use when the user says \"report this to X\", \"send X a feature request\", \"email the developer about this bug\", \"tell my contact at X\". For security vulnerabilities use security-disclosure instead.","https:\u002F\u002Fgithub.com\u002Fdanielrosehill\u002FVendor-Liaison\u002Fblob\u002Fmaster\u002Fskills\u002Freport\u002FSKILL.md",[143],{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[29,145,47,129,91,92,45,130,93,133,38,37,98,146,147,136,148,86,137,149],"app","message","github","github issue","about",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":49},"01M718KTWDF57HQF7HXS0HNWYF","op-fr-tracker","Log 1Password feature requests and threads the user posted or joined, and check them for staff replies or shipped features.","https:\u002F\u002Fgithub.com\u002Fdanielrosehill\u002FVendor-Liaison\u002Fblob\u002Fmaster\u002Fskills\u002Fop-fr-tracker\u002FSKILL.md",[],[119,157,158,159,160,161,100,91,45,162,163,164,165,166,167],"op","op fr tracker","replies","1password","threads","features","feature requests","Staff","user","log","check",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":49},"01M718KSDECJSWDM8DB9D1XAQX","op-fr-search","Search the 1Password Community and release notes for an existing feature request or answer before posting a new one.","https:\u002F\u002Fgithub.com\u002Fdanielrosehill\u002FVendor-Liaison\u002Fblob\u002Fmaster\u002Fskills\u002Fop-fr-search\u002FSKILL.md",[],[175,176,157,177,178,160,179,91,45,137,180,181,182,183,184,185],"search","op fr search","community","notes","posting","answer","release","new","release notes","Existing","feature request"]