[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718KX5ENS7DTKN9B2X0Z1DB":3,"skill-same:01M718KX5ENS7DTKN9B2X0Z1DB":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":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":14,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M718KX5ENS7DTKN9B2X0Z1DB","report",null,"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.","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\u002Freport\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"use","about","request","vendor","github issue","support","github","message","post","when","question","company","send","for","email","feature","feedback","form","app","2026-11-10 10:12:30",false,"---\nname: report\ndescription: 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.\n---\n\n# Report to a vendor\n\n## 1. Route\n\nRun the `route` skill, which calls `scripts\u002Fliaison.py route \u003Cvendor> \u003Cpurpose>`. If the\nresult names a vendor-specific `skill`, hand off to it and stop here. Otherwise use the\ntop channel, unless the user picks another.\n\nIf the purpose is `security`, stop and use `security-disclosure`.\n\n## 2. Check it hasn't been reported\n\nRun this on every channel, including private ones: a private email about a problem that\nis already on the public tracker wastes the vendor's time.\n\n- Follow the channel's `dedupe` instruction where it has one.\n- Otherwise search the vendor's public channels from its data (issue tracker, forum,\n  subreddit) with two or three short phrasings, and check its release notes or changelog\n  in case the problem is already fixed or the feature already shipped.\n- If an existing report matches, show it. Offer to add to it (comment, reply or vote)\n  instead of filing a new one. When you send privately anyway, reference the public\n  thread.\n\n## 3. Collect what the vendor needs\n\nUse the vendor's `rules` for which fields it needs. For a bug, the usual set is:\n- product and version;\n- OS or device;\n- steps to reproduce;\n- what should happen and what actually happens;\n- exact error text.\n\nCollect environment facts by running commands rather than asking. Ask for anything still\nmissing in a single batch.\n\n## 4. Draft for the channel\n\n| Channel type | Draft |\n|---|---|\n| `email` | Subject line that says what's wrong or what's wanted (\"Bug: …\", \"Feature request: …\"); short body; product and version near the top |\n| `github-issues`, `issue-tracker` | Fetch and follow the repo's issue template; one problem per issue |\n| `forum`, `reddit`, `discord`, `slack` | Follow the community's posting rules and flair; a title that matches what someone else would search for |\n| `contact-form`, `in-app` | Text sized to the form; tell the user which fields to fill if you can't drive it |\n| `contact`, `whatsapp`, `signal`, `telegram` | A personal, short message in the register of the relationship; follow the contact's `etiquette` notes |\n| `in-person`, `phone` | Talking points for the user, not a script |\n| `app-store-review` | Only when the user wants a public rating; never as a substitute for a bug report |\n\nRemove secrets and personal detail before showing the draft:\n- tokens and keys;\n- account IDs;\n- other people's data;\n- internal hostnames.\n\nTell the user what you removed.\n\n## 5. Approve, send, log\n\nShow the exact text, the destination and the sender. Send only after the user approves.\nUse whatever tool the environment provides for that channel type:\n- `gh` for GitHub;\n- the user's email tool for email;\n- a signed-in browser for forums and forms;\n- a messaging tool for chat apps.\n\nIf no tool can send it, give the user the text and the destination to send themselves.\n\nAfter sending, add one line to `\u003Coverlay_dir>\u002Freports.jsonl` (the path comes from\n`liaison.py paths`):\n\n```json\n{\"date\": \"YYYY-MM-DD\", \"vendor\": \"\u003Cid>\", \"purpose\": \"\u003Cpurpose>\", \"channel\": \"\u003Cchannel id>\", \"ref\": \"\u003CURL, message id or ''>\", \"summary\": \"\u003Cone line>\"}\n```\n","# Report to a vendor\n\n## 1. Route\n\nRun the `route` skill, which calls `scripts\u002Fliaison.py route \u003Cvendor> \u003Cpurpose>`. If the\nresult names a vendor-specific `skill`, hand off to it and stop here. Otherwise use the\ntop channel, unless the user picks another.\n\nIf the purpose is `security`, stop and use `security-disclosure`.\n\n## 2. Check it hasn't been reported\n\nRun this on every channel, including private ones: a private email about a problem that\nis already on the public tracker wastes the vendor's time.\n\n- Follow the channel's `dedupe` instruction where it has one.\n- Otherwise search the vendor's public channels from its data (issue tracker, forum,\n  subreddit) with two or three short phrasings, and check its release notes or changelog\n  in case the problem is already fixed or the feature already shipped.\n- If an existing report matches, show it. Offer to add to it (comment, reply or vote)\n  instead of filing a new one. When you send privately anyway, reference the public\n  thread.\n\n## 3. Collect what the vendor needs\n\nUse the vendor's `rules` for which fields it needs. For a bug, the usual set is:\n- product and version;\n- OS or device;\n- steps to reproduce;\n- what should happen and what actually happens;\n- exact error text.\n\nCollect environment facts by running commands rather than asking. Ask for anything still\nmissing in a single batch.\n\n## 4. Draft for the channel\n\n| Channel type | Draft |\n|---|---|\n| `email` | Subject line that says what's wrong or what's wanted (\"Bug: …\", \"Feature request: …\"); short body; product and version near the top |\n| `github-issues`, `issue-tracker` | Fetch and follow the repo's issue template; one problem per issue |\n| `forum`, `reddit`, `discord`, `slack` | Follow the community's posting rules and flair; a title that matches what someone else would search for |\n| `contact-form`, `in-app` | Text sized to the form; tell the user which fields to fill if you can't drive it |\n| `contact`, `whatsapp`, `signal`, `telegram` | A personal, short message in the register of the relationship; follow the contact's `etiquette` notes |\n| `in-person`, `phone` | Talking points for the user, not a script |\n| `app-store-review` | Only when the user wants a public rating; never as a substitute for a bug report |\n\nRemove secrets and personal detail before showing the draft:\n- tokens and keys;\n- account IDs;\n- other people's data;\n- internal hostnames.\n\nTell the user what you removed.\n\n## 5. Approve, send, log\n\nShow the exact text, the destination and the sender. Send only after the user approves.\nUse whatever tool the environment provides for that channel type:\n- `gh` for GitHub;\n- the user's email tool for email;\n- a signed-in browser for forums and forms;\n- a messaging tool for chat apps.\n\nIf no tool can send it, give the user the text and the destination to send themselves.\n\nAfter sending, add one line to `\u003Coverlay_dir>\u002Freports.jsonl` (the path comes from\n`liaison.py paths`):\n\n```json\n{\"date\": \"YYYY-MM-DD\", \"vendor\": \"\u003Cid>\", \"purpose\": \"\u003Cpurpose>\", \"channel\": \"\u003Cchannel id>\", \"ref\": \"\u003CURL, message id or ''>\", \"summary\": \"\u003Cone line>\"}\n```\n",{"name":5,"description":7},"master","e504fb5fc47e6cac00f2fa2bb0dced5951092a9b","skills\u002Freport","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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add danielrosehill\u002FVendor-Liaison --skill report",{"tool":62,"command":63},"bunx","bunx skills add danielrosehill\u002FVendor-Liaison --skill report",{"tool":65,"command":66},"pnpm","pnpm dlx skills add danielrosehill\u002FVendor-Liaison --skill report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielrosehill\u002FVendor-Liaison\u002Fblob\u002Fmaster\u002Fskills\u002Freport\u002FSKILL.md",true,[],[71,90,111,123,141,159],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":43},"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",[],[78,79,27,80,81,82,83,39,38,37,35,24,33,84,85,86,87,32,88,89],"preferences","vendor preferences","account manager","remember","which","bugs","number","channels","contacts","record","reddit","requests",{"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":43},"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",[],[97,98,99,100,101,35,102,103,104,24,33,105,106,107,32,108,109,27,110,5],"security disclosure","security","never","bug-bounty","auth","social","only","social post","security vulnerability","program","vulnerability","product","tracker","at",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":43},"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",[],[113,118,40,39,36,119,120,34,78,24,33,105,107,85,86,121,122,29,27,26],"do","filing","general","work","how",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":43},"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",[],[109,130,131,132,133,134,89,39,37,135,136,137,138,139,140],"op","op fr tracker","replies","1password","threads","features","feature requests","Staff","user","log","check",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":43},"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",[],[148,149,130,150,151,133,152,39,37,26,153,154,155,156,157,158],"search","op fr search","community","notes","posting","answer","release","new","release notes","Existing","feature request",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":43},"01M718KQGATY2VA015JW7B4CCT","op-feature-request","Draft and submit a feature request to 1Password as a Community topic tagged Feature Request, after a duplicate check and approval.","https:\u002F\u002Fgithub.com\u002Fdanielrosehill\u002FVendor-Liaison\u002Fblob\u002Fmaster\u002Fskills\u002Fop-feature-request\u002FSKILL.md",[],[39,26,166,130,158,167,150,168,133,169,170,171,172,140],"op feature request","draft","as","duplicate","submit","tagged","approval"]