[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718KSDECJSWDM8DB9D1XAQX":3,"skill-same:01M718KSDECJSWDM8DB9D1XAQX":62},{"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":18,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":14,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M718KSDECJSWDM8DB9D1XAQX","op-fr-search",null,"Search the 1Password Community and release notes for an existing feature request or answer before posting a new one.","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\u002Fop-fr-search\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"search","op fr search","op","community","notes","1password","posting","feature","for","request","answer","release","new","release notes","Existing","feature request","2026-11-10 10:12:30",false,"---\nname: op-fr-search\ndescription: Search the 1Password Community and release notes for an existing feature request or answer before posting a new one.\n---\n\n# Search 1Password feature requests\n\nRun this before every new 1Password feature request, and when the user asks \"has anyone\nasked 1Password for X\", \"is there a thread about X\", or \"does 1Password do X yet\".\n\n## Inputs\n\n- The capability in plain words (e.g. \"per-app SSH agent approval\").\n- Optional product area: home, work, developers.\n\n## Steps\n\n1. **Shipped already?** Check release notes. Fetch\n   `https:\u002F\u002Freleases.1password.com\u002Findex.xml` (or the product section in\n   `${CLAUDE_PLUGIN_ROOT}\u002Fvendors\u002F1password\u002Fchannels.json`) and look for the capability. Also check the product's\n   support docs with a web search scoped to `support.1password.com` \u002F\n   `developer.1password.com`. If it shipped, stop and say where.\n2. **Title search, no browser.** Run the helper from the plugin root:\n\n   ```bash\n   python3 ${CLAUDE_PLUGIN_ROOT}\u002Fvendors\u002F1password\u002Fscripts\u002Fcommunity.py search \u003C2-4 keywords> [--category developers]\n   ```\n\n   Try two or three phrasings with synonyms (`autofill`\u002F`fill`, `passkey`\u002F`webauthn`,\n   `cli`\u002F`op`). Slugs are titles only, so a miss here is not proof of absence.\n3. **Read the top candidates.** For up to five plausible hits:\n\n   ```bash\n   python3 ${CLAUDE_PLUGIN_ROOT}\u002Fvendors\u002F1password\u002Fscripts\u002Fcommunity.py topic \u003Curl>\n   ```\n\n   This gives the opening post, date, likes and reply count. It does not include replies\n   or tags.\n4. **Browser search for body text and tags.** The forum search runs client-side, so use\n   Claude in Chrome (open your own tab). Open\n   `https:\u002F\u002Fwww.1password.community\u002Fsearch\u002Findex?q=Feature%20Request&search_type=tag`\n   for the Feature Request tag, and `https:\u002F\u002Fwww.1password.community\u002Fsearch?q=\u003Cterms>`\n   for keywords. Read the result list; open a thread to see replies, staff responses and\n   whether it is locked.\n5. **The user's own topics.** Open the user's profile activity\n   (`\u002Fmembers\u002F\u003Chandle>-\u003Cid>`, linked from the avatar) and check they haven't asked this\n   already. Their earlier topics can be filed as *Question* with a non-standard title,\n   which the sitemap search misses (2026-10-22: topic 25245 duplicated 24516).\n6. **Optional: GitHub.** For SDK, Terraform, Connect, operator or shell-plugin requests,\n   search issues in the matching `github.com\u002F1Password\u002F\u003Crepo>`.\n\n## Output\n\nReport as JSON-shaped lines, most relevant first:\n\n```json\n{\"verdict\": \"shipped | existing-thread | none-found\",\n \"matches\": [{\"url\": \"...\", \"title\": \"...\", \"created\": \"...\", \"likes\": 0, \"replies\": 0,\n              \"staff_replied\": true, \"locked\": false, \"fit\": \"exact | partial\"}],\n \"searched\": [\"release notes\", \"sitemap: \u003Cterms>\", \"forum tag search\", \"forum keyword search\"]}\n```\n\nThen one line of advice: reply to the existing thread (hand off to\n`op-community-engage`), or post new (hand off to `op-feature-request`). An exact match\nmeans a supportive reply that adds the user's use case, posted by default, not a\ndead end.\n\n## Notes\n\n- Do not report \"none found\" from the sitemap step alone. The browser search is what\n  covers post bodies.\n- The `\u002Fideas` board is empty and unused; ignore it.\n","# Search 1Password feature requests\n\nRun this before every new 1Password feature request, and when the user asks \"has anyone\nasked 1Password for X\", \"is there a thread about X\", or \"does 1Password do X yet\".\n\n## Inputs\n\n- The capability in plain words (e.g. \"per-app SSH agent approval\").\n- Optional product area: home, work, developers.\n\n## Steps\n\n1. **Shipped already?** Check release notes. Fetch\n   `https:\u002F\u002Freleases.1password.com\u002Findex.xml` (or the product section in\n   `${CLAUDE_PLUGIN_ROOT}\u002Fvendors\u002F1password\u002Fchannels.json`) and look for the capability. Also check the product's\n   support docs with a web search scoped to `support.1password.com` \u002F\n   `developer.1password.com`. If it shipped, stop and say where.\n2. **Title search, no browser.** Run the helper from the plugin root:\n\n   ```bash\n   python3 ${CLAUDE_PLUGIN_ROOT}\u002Fvendors\u002F1password\u002Fscripts\u002Fcommunity.py search \u003C2-4 keywords> [--category developers]\n   ```\n\n   Try two or three phrasings with synonyms (`autofill`\u002F`fill`, `passkey`\u002F`webauthn`,\n   `cli`\u002F`op`). Slugs are titles only, so a miss here is not proof of absence.\n3. **Read the top candidates.** For up to five plausible hits:\n\n   ```bash\n   python3 ${CLAUDE_PLUGIN_ROOT}\u002Fvendors\u002F1password\u002Fscripts\u002Fcommunity.py topic \u003Curl>\n   ```\n\n   This gives the opening post, date, likes and reply count. It does not include replies\n   or tags.\n4. **Browser search for body text and tags.** The forum search runs client-side, so use\n   Claude in Chrome (open your own tab). Open\n   `https:\u002F\u002Fwww.1password.community\u002Fsearch\u002Findex?q=Feature%20Request&search_type=tag`\n   for the Feature Request tag, and `https:\u002F\u002Fwww.1password.community\u002Fsearch?q=\u003Cterms>`\n   for keywords. Read the result list; open a thread to see replies, staff responses and\n   whether it is locked.\n5. **The user's own topics.** Open the user's profile activity\n   (`\u002Fmembers\u002F\u003Chandle>-\u003Cid>`, linked from the avatar) and check they haven't asked this\n   already. Their earlier topics can be filed as *Question* with a non-standard title,\n   which the sitemap search misses (2026-10-22: topic 25245 duplicated 24516).\n6. **Optional: GitHub.** For SDK, Terraform, Connect, operator or shell-plugin requests,\n   search issues in the matching `github.com\u002F1Password\u002F\u003Crepo>`.\n\n## Output\n\nReport as JSON-shaped lines, most relevant first:\n\n```json\n{\"verdict\": \"shipped | existing-thread | none-found\",\n \"matches\": [{\"url\": \"...\", \"title\": \"...\", \"created\": \"...\", \"likes\": 0, \"replies\": 0,\n              \"staff_replied\": true, \"locked\": false, \"fit\": \"exact | partial\"}],\n \"searched\": [\"release notes\", \"sitemap: \u003Cterms>\", \"forum tag search\", \"forum keyword search\"]}\n```\n\nThen one line of advice: reply to the existing thread (hand off to\n`op-community-engage`), or post new (hand off to `op-feature-request`). An exact match\nmeans a supportive reply that adds the user's use case, posted by default, not a\ndead end.\n\n## Notes\n\n- Do not report \"none found\" from the sitemap step alone. The browser search is what\n  covers post bodies.\n- The `\u002Fideas` board is empty and unused; ignore it.\n",{"name":5,"description":7},"master","e504fb5fc47e6cac00f2fa2bb0dced5951092a9b","skills\u002Fop-fr-search","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":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add danielrosehill\u002FVendor-Liaison --skill op-fr-search",{"tool":54,"command":55},"bunx","bunx skills add danielrosehill\u002FVendor-Liaison --skill op-fr-search",{"tool":57,"command":58},"pnpm","pnpm dlx skills add danielrosehill\u002FVendor-Liaison --skill op-fr-search","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielrosehill\u002FVendor-Liaison\u002Fblob\u002Fmaster\u002Fskills\u002Fop-fr-search\u002FSKILL.md",true,[],[63,88,110,126,143,159],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":35},"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",[],[70,71,72,73,74,75,76,26,77,27,78,79,80,81,82,83,84,85,86,87],"preferences","vendor preferences","vendor","account manager","remember","which","bugs","email","company","use","when","number","channels","contacts","record","post","reddit","requests",{"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":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":35},"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",[],[95,96,97,98,99,78,100,101,102,79,80,103,104,105,85,106,107,72,108,109],"security disclosure","security","never","bug-bounty","auth","social","only","social post","security vulnerability","program","vulnerability","product","tracker","at","report",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":35},"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",[],[112,117,118,26,119,120,121,122,70,79,80,103,105,82,83,123,124,125,72,28],"do","feedback","send","filing","general","question","work","how","support",{"skillNo":127,"name":109,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":136,"publishedAt":35},"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",[131],{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[109,137,138,118,26,77,27,119,78,122,79,80,85,139,140,125,141,72,28,142],"app","form","message","github","github issue","about",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":35},"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",[],[107,21,150,151,24,152,87,26,27,153,154,155,156,157,158],"op fr tracker","replies","threads","features","feature requests","Staff","user","log","check",{"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":35},"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",[],[26,28,166,21,34,167,22,168,24,169,170,171,172,158],"op feature request","draft","as","duplicate","submit","tagged","approval"]