add-vendorResearch 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",
cc-bug-reportFile a bug report against Claude Code (anthropics/claude-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,
op-bug-reportReport a 1Password bug on the Community — version check against latest release, duplicate search, environment details, tagged topic.
op-community-engageEngage in the 1Password Community — +1 or add a use case to a feature request, reply to threads, answer questions, browse new topics.
op-feature-requestDraft and submit a feature request to 1Password as a Community topic tagged Feature Request, after a duplicate check and approval.
op-fr-searchSearch the 1Password Community and release notes for an existing feature request or answer before posting a new one.
op-fr-trackerLog 1Password feature requests and threads the user posted or joined, and check them for staff replies or shipped features.
reportSend 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
routeWork 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",
security-disclosureDisclose 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 expo
vendor-preferencesRecord 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