[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718KQGATY2VA015JW7B4CCT":3,"skill-same:01M718KQGATY2VA015JW7B4CCT":60},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":14,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M718KQGATY2VA015JW7B4CCT","op-feature-request",null,"Draft and submit a feature request to 1Password as a Community topic tagged Feature Request, after a duplicate check and approval.","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-feature-request\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"feature","request","op feature request","op","feature request","draft","community","as","1password","duplicate","submit","tagged","approval","check","2026-11-10 10:12:30",false,"---\nname: op-feature-request\ndescription: Draft and submit a feature request to 1Password as a Community topic tagged Feature Request, after a duplicate check and approval.\n---\n\n# Submit a 1Password feature request\n\nUse when the user says \"request a feature from 1Password\", \"file a 1Password FR\", \"tell\n1Password they should…\", or \"post this to the 1Password community\".\n\nRead `${CLAUDE_PLUGIN_ROOT}\u002Fvendors\u002F1password\u002Fposting-guide.md` and `${CLAUDE_PLUGIN_ROOT}\u002Fvendors\u002F1password\u002Fchannels.json` first.\n\n## Inputs\n\n- What the user wants and why, in their words (a voice note transcript is fine).\n- Product\u002Fplatform if known.\n\n## Steps\n\n1. **Duplicate check.** Run `op-fr-search`. If it finds an exact match, do not open a\n   new topic and do not stop empty-handed: hand off to `op-community-engage` (\"Support\n   an existing feature request\") and post a supportive reply that adds the user's use\n   case. That is the default outcome of a duplicate, posted without asking; the\n   original request is the permission. Open a new topic only if the thread is locked\n   or the user insists. A partial match gets linked in the new post.\n2. **Gather facts.** Fill gaps the request needs: platform, plan, app or CLI version.\n   Get versions from the machine where possible (`op --version`, the app's About\n   screen) rather than asking. Ask the user only for the use case if it is missing.\n3. **Pick the route.**\n   - Default: Community topic, category home (`fid=31`), work (`fid=58`) or\n     developers (`fid=69`).\n   - SDK \u002F Terraform \u002F Connect \u002F operator \u002F shell-plugin: offer a GitHub issue on the\n     matching `1Password\u002F\u003Crepo>` using its feature-request template as an alternative\n     or addition.\n4. **Draft** with the template in `posting-guide.md`. Title starts\n   `Feature Request: `. Strip any account email, vault or item names, Secret Key,\n   order numbers.\n5. **Post by default.** Asking for a feature request is permission to post it. Go\n   straight to step 6, and show the final category, tags, title and body in the\n   report afterwards. Stop at the draft and wait for approval only when the user asks\n   for that (\"draft it\", \"let me see it first\", \"pause before posting\").\n6. **Post** with Claude in Chrome (open your own tab):\n   1. Open `https:\u002F\u002Fwww.1password.community\u002Ftopic\u002Fnew?fid=\u003C31|58|69>`.\n   2. If the page shows a login prompt, stop and ask the user to sign in to the\n      community account in that window. It is a separate account from 1Password\n      itself. Do not type credentials.\n   3. **Topic type:** the form opens on *Question*. Select **Conversation** for a\n      feature request.\n   4. **Title:** plain text input (`placeholder=\"Enter title here\"`); click and type.\n      Typing it makes the form show a *Related topics* list: one last duplicate check.\n   5. **Body:** a CKEditor 4 instance (`editor1`). Typing loses structure; set HTML\n      instead, with `javascript_tool`:\n      `Object.values(CKEDITOR.instances)[0].setData(html)`. Use `\u003Cp>\u003Cstrong>` for\n      headings and `\u003Cul>\u003Cli>\u003Ca>` for related links.\n   6. **Category** is preselected from `?fid=`.\n   7. **Tags:** click *Add tags*, type `Feature Request`, then click the dropdown\n      suggestion (Enter alone does not add it). Product tags then appear as\n      `\u003CTag> +` chips under the field; click the right one. Read the chips back before\n      submitting.\n   8. Click **Create**. The page redirects to the new topic.\n7. **Verify.** Read back the published topic URL. Confirm title, body and tags render.\n   Run `python3 ${CLAUDE_PLUGIN_ROOT}\u002Fvendors\u002F1password\u002Fscripts\u002Fcommunity.py topic \u003Curl>` once it is in the\n   sitemap (can lag).\n8. **Log** via `op-fr-tracker` (add entry).\n\n## Data storage\n\nLogged requests live in\n`${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME\u002F.local\u002Fshare}\u002Fclaude-plugins}\u002Fonepassword-feedback\u002Fdata\u002Frequests.json`.\nNothing is written elsewhere.\n\n## Notes\n\n- Posting is public and attributed to the user's community account. Default is to post;\n  pause at the draft only when the user asks.\n- If the tag picker, URL or form layout differs from this file, finish the job, then\n  update this skill and `channels.json` with what you found and the date.\n","# Submit a 1Password feature request\n\nUse when the user says \"request a feature from 1Password\", \"file a 1Password FR\", \"tell\n1Password they should…\", or \"post this to the 1Password community\".\n\nRead `${CLAUDE_PLUGIN_ROOT}\u002Fvendors\u002F1password\u002Fposting-guide.md` and `${CLAUDE_PLUGIN_ROOT}\u002Fvendors\u002F1password\u002Fchannels.json` first.\n\n## Inputs\n\n- What the user wants and why, in their words (a voice note transcript is fine).\n- Product\u002Fplatform if known.\n\n## Steps\n\n1. **Duplicate check.** Run `op-fr-search`. If it finds an exact match, do not open a\n   new topic and do not stop empty-handed: hand off to `op-community-engage` (\"Support\n   an existing feature request\") and post a supportive reply that adds the user's use\n   case. That is the default outcome of a duplicate, posted without asking; the\n   original request is the permission. Open a new topic only if the thread is locked\n   or the user insists. A partial match gets linked in the new post.\n2. **Gather facts.** Fill gaps the request needs: platform, plan, app or CLI version.\n   Get versions from the machine where possible (`op --version`, the app's About\n   screen) rather than asking. Ask the user only for the use case if it is missing.\n3. **Pick the route.**\n   - Default: Community topic, category home (`fid=31`), work (`fid=58`) or\n     developers (`fid=69`).\n   - SDK \u002F Terraform \u002F Connect \u002F operator \u002F shell-plugin: offer a GitHub issue on the\n     matching `1Password\u002F\u003Crepo>` using its feature-request template as an alternative\n     or addition.\n4. **Draft** with the template in `posting-guide.md`. Title starts\n   `Feature Request: `. Strip any account email, vault or item names, Secret Key,\n   order numbers.\n5. **Post by default.** Asking for a feature request is permission to post it. Go\n   straight to step 6, and show the final category, tags, title and body in the\n   report afterwards. Stop at the draft and wait for approval only when the user asks\n   for that (\"draft it\", \"let me see it first\", \"pause before posting\").\n6. **Post** with Claude in Chrome (open your own tab):\n   1. Open `https:\u002F\u002Fwww.1password.community\u002Ftopic\u002Fnew?fid=\u003C31|58|69>`.\n   2. If the page shows a login prompt, stop and ask the user to sign in to the\n      community account in that window. It is a separate account from 1Password\n      itself. Do not type credentials.\n   3. **Topic type:** the form opens on *Question*. Select **Conversation** for a\n      feature request.\n   4. **Title:** plain text input (`placeholder=\"Enter title here\"`); click and type.\n      Typing it makes the form show a *Related topics* list: one last duplicate check.\n   5. **Body:** a CKEditor 4 instance (`editor1`). Typing loses structure; set HTML\n      instead, with `javascript_tool`:\n      `Object.values(CKEDITOR.instances)[0].setData(html)`. Use `\u003Cp>\u003Cstrong>` for\n      headings and `\u003Cul>\u003Cli>\u003Ca>` for related links.\n   6. **Category** is preselected from `?fid=`.\n   7. **Tags:** click *Add tags*, type `Feature Request`, then click the dropdown\n      suggestion (Enter alone does not add it). Product tags then appear as\n      `\u003CTag> +` chips under the field; click the right one. Read the chips back before\n      submitting.\n   8. Click **Create**. The page redirects to the new topic.\n7. **Verify.** Read back the published topic URL. Confirm title, body and tags render.\n   Run `python3 ${CLAUDE_PLUGIN_ROOT}\u002Fvendors\u002F1password\u002Fscripts\u002Fcommunity.py topic \u003Curl>` once it is in the\n   sitemap (can lag).\n8. **Log** via `op-fr-tracker` (add entry).\n\n## Data storage\n\nLogged requests live in\n`${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME\u002F.local\u002Fshare}\u002Fclaude-plugins}\u002Fonepassword-feedback\u002Fdata\u002Frequests.json`.\nNothing is written elsewhere.\n\n## Notes\n\n- Posting is public and attributed to the user's community account. Default is to post;\n  pause at the draft only when the user asks.\n- If the tag picker, URL or form layout differs from this file, finish the job, then\n  update this skill and `channels.json` with what you found and the date.\n",{"name":5,"description":7},"master","e504fb5fc47e6cac00f2fa2bb0dced5951092a9b","skills\u002Fop-feature-request","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":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add danielrosehill\u002FVendor-Liaison --skill op-feature-request",{"tool":52,"command":53},"bunx","bunx skills add danielrosehill\u002FVendor-Liaison --skill op-feature-request",{"tool":55,"command":56},"pnpm","pnpm dlx skills add danielrosehill\u002FVendor-Liaison --skill op-feature-request","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielrosehill\u002FVendor-Liaison\u002Fblob\u002Fmaster\u002Fskills\u002Fop-feature-request\u002FSKILL.md",true,[],[61,87,109,125,142,157],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":33},"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",[],[68,69,70,71,72,73,74,19,75,76,77,78,79,80,81,82,83,84,85,86],"preferences","vendor preferences","vendor","account manager","remember","which","bugs","email","for","company","use","when","number","channels","contacts","record","post","reddit","requests",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":33},"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",[],[94,95,96,97,98,77,99,100,101,78,79,102,103,104,84,105,106,70,107,108],"security disclosure","security","never","bug-bounty","auth","social","only","social post","security vulnerability","program","vulnerability","product","tracker","at","report",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":33},"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",[],[111,116,117,19,118,119,120,121,68,78,79,102,104,81,82,122,123,124,70,20],"do","feedback","send","filing","general","question","work","how","support",{"skillNo":126,"name":108,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":135,"publishedAt":33},"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",[130],{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[108,136,137,117,19,75,76,118,77,121,78,79,84,138,139,124,140,70,20,141],"app","form","message","github","github issue","about",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":33},"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",[],[106,22,149,150,27,151,86,19,76,152,153,154,155,156,32],"op fr tracker","replies","threads","features","feature requests","Staff","user","log",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":33},"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",[],[164,165,22,25,166,27,167,19,76,20,168,169,170,171,172,23],"search","op fr search","notes","posting","answer","release","new","release notes","Existing"]