[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718KD4XHCWBSW6R89GMH6SS":3,"skill-same:01M718KD4XHCWBSW6R89GMH6SS":71},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M718KD4XHCWBSW6R89GMH6SS","add-vendor",null,"Research how a software vendor takes bug reports, feature requests, security reports and support, and record it as structured channel data (vendor.json) so routing works for that vendor. Use when a vendor isn't known yet, when the user says \"add X to vendor liaison\", \"find out how X takes feedback\", or when a vendor's channels have changed or died.","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\u002Fadd-vendor\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"vendor","add","add vendor","bug","json","find","support","how","requests","research","record","routing","reports","channels","when","use","for","feature","feedback","as","2026-11-10 10:12:30",false,"---\nname: add-vendor\ndescription: Research how a software vendor takes bug reports, feature requests, security reports and support, and record it as structured channel data (vendor.json) so routing works for that vendor. Use when a vendor isn't known yet, when the user says \"add X to vendor liaison\", \"find out how X takes feedback\", or when a vendor's channels have changed or died.\n---\n\n# Add or update a vendor\n\n## 1. Research the channels\n\nCheck each of these for the vendor, and record where each fact came from:\n\n- The website's footer, contact, support and help pages.\n- `\u002F.well-known\u002Fsecurity.txt`, a security page or bug-bounty listing, and `SECURITY.md`.\n- App store listings. These usually give the developer's contact email.\n- Public issue trackers: GitHub or GitLab issues and their issue templates, and whether\n  blank issues are allowed.\n- Community spaces: the forum, subreddit, Discord or Slack. Note any flair or tag used\n  for feature requests and bugs.\n- Feature boards (Canny, Productboard portal, UserVoice, and so on), and whether they are\n  actually in use.\n- In-app feedback.\n- Release notes or a changelog, for checking against before reporting.\n\nFor each channel, test the address or URL where you can. Mark the channel `confirmed`\nonly if you loaded the page or saw the address published; mark it `inferred` if it came\nfrom a secondary source; mark it `dead` (and keep it) if it's gone, so nobody adds it\nagain.\n\nAlso find out how each public channel can be searched for duplicates, and record the\nworking method in `dedupe`. For example, Reddit's `.json` endpoints refuse anonymous\nrequests but `search.rss` works.\n\n## 2. Write the record\n\nPublic vendor: `vendors\u002F\u003Cid>\u002Fvendor.json` in the plugin repo. The field reference is in\n`vendors\u002FREADME.md`, and existing vendors are examples. Required fields:\n- `id`, `name` and `verified` (YYYY-MM-DD);\n- `channels`, each with `id`, `type`, `target`, `visibility`, `purposes` and `status`;\n- `routing`: the recommended channel order per purpose;\n- `rules`: the vendor's requirements, in imperative sentences.\n\nOptional: a `reporting.md` for long-form notes, and `skills` when a vendor-specific skill\nexists.\n\nAnything personal to the user (unpublished addresses, contacts, preferences) goes in\ntheir overlay through `vendor-preferences`, never here. A vendor the user doesn't want\npublished goes under `vendor` in their overlay file.\n\n## 3. Validate\n\n```bash\npython3 \u003Cplugin-root>\u002Fscripts\u002Fliaison.py validate \u003Cid>\npython3 \u003Cplugin-root>\u002Fscripts\u002Fliaison.py route \u003Cid> bug\n```\n\nThe validator rejects routing that points at undefined channels, a channel that doesn't\nlist the purpose it's routed for, and any public channel in `routing.security`. A public\nvendor file is a change to the plugin repository: commit it there (or open a pull\nrequest upstream) and add a row to the vendor table in the top-level README.\n","# Add or update a vendor\n\n## 1. Research the channels\n\nCheck each of these for the vendor, and record where each fact came from:\n\n- The website's footer, contact, support and help pages.\n- `\u002F.well-known\u002Fsecurity.txt`, a security page or bug-bounty listing, and `SECURITY.md`.\n- App store listings. These usually give the developer's contact email.\n- Public issue trackers: GitHub or GitLab issues and their issue templates, and whether\n  blank issues are allowed.\n- Community spaces: the forum, subreddit, Discord or Slack. Note any flair or tag used\n  for feature requests and bugs.\n- Feature boards (Canny, Productboard portal, UserVoice, and so on), and whether they are\n  actually in use.\n- In-app feedback.\n- Release notes or a changelog, for checking against before reporting.\n\nFor each channel, test the address or URL where you can. Mark the channel `confirmed`\nonly if you loaded the page or saw the address published; mark it `inferred` if it came\nfrom a secondary source; mark it `dead` (and keep it) if it's gone, so nobody adds it\nagain.\n\nAlso find out how each public channel can be searched for duplicates, and record the\nworking method in `dedupe`. For example, Reddit's `.json` endpoints refuse anonymous\nrequests but `search.rss` works.\n\n## 2. Write the record\n\nPublic vendor: `vendors\u002F\u003Cid>\u002Fvendor.json` in the plugin repo. The field reference is in\n`vendors\u002FREADME.md`, and existing vendors are examples. Required fields:\n- `id`, `name` and `verified` (YYYY-MM-DD);\n- `channels`, each with `id`, `type`, `target`, `visibility`, `purposes` and `status`;\n- `routing`: the recommended channel order per purpose;\n- `rules`: the vendor's requirements, in imperative sentences.\n\nOptional: a `reporting.md` for long-form notes, and `skills` when a vendor-specific skill\nexists.\n\nAnything personal to the user (unpublished addresses, contacts, preferences) goes in\ntheir overlay through `vendor-preferences`, never here. A vendor the user doesn't want\npublished goes under `vendor` in their overlay file.\n\n## 3. Validate\n\n```bash\npython3 \u003Cplugin-root>\u002Fscripts\u002Fliaison.py validate \u003Cid>\npython3 \u003Cplugin-root>\u002Fscripts\u002Fliaison.py route \u003Cid> bug\n```\n\nThe validator rejects routing that points at undefined channels, a channel that doesn't\nlist the purpose it's routed for, and any public channel in `routing.security`. A public\nvendor file is a change to the plugin repository: commit it there (or open a pull\nrequest upstream) and add a row to the vendor table in the top-level README.\n",{"name":5,"description":7},"master","e504fb5fc47e6cac00f2fa2bb0dced5951092a9b","skills\u002Fadd-vendor","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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add danielrosehill\u002FVendor-Liaison --skill add-vendor",{"tool":63,"command":64},"bunx","bunx skills add danielrosehill\u002FVendor-Liaison --skill add-vendor",{"tool":66,"command":67},"pnpm","pnpm dlx skills add danielrosehill\u002FVendor-Liaison --skill add-vendor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielrosehill\u002FVendor-Liaison\u002Fblob\u002Fmaster\u002Fskills\u002Fadd-vendor\u002FSKILL.md",true,[],[72,91,113,127,144,162],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":44},"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",[],[79,80,24,81,82,83,84,41,85,40,86,39,38,87,37,88,34,89,90,32],"preferences","vendor preferences","account manager","remember","which","bugs","email","company","number","contacts","post","reddit",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":44},"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",[],[98,99,100,101,102,86,103,104,105,39,38,106,107,108,89,109,110,24,111,112],"security disclosure","security","never","bug-bounty","auth","social","only","social post","security vulnerability","program","vulnerability","product","tracker","at","report",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":44},"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",[],[115,120,42,41,121,122,123,124,79,39,38,106,108,37,88,125,31,30,24,126],"do","send","filing","general","question","work","request",{"skillNo":128,"name":112,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":137,"publishedAt":44},"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",[132],{"categoryNo":133,"categoryName":134,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[112,138,139,42,41,85,40,121,86,124,39,38,89,140,141,30,142,24,126,143],"app","form","message","github","github issue","about",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":44},"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",[],[110,151,152,153,154,155,32,41,40,156,157,158,159,160,161],"op","op fr tracker","replies","1password","threads","features","feature requests","Staff","user","log","check",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":44},"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",[],[169,170,151,171,172,154,173,41,40,126,174,175,176,177,178,179],"search","op fr search","community","notes","posting","answer","release","new","release notes","Existing","feature request"]