mcp-feedback
Record a user's feedback about the Unbounce MCP tools — a bug, praise, a feature request, confusion, or anything else — straight to the team via the submit_feedback tool, with no copy/paste. Use when the user wants to report a bug, share feedback, praise something, request a feature, or flag that a tool was confusing. Also covers login/connection issues — the user can't connect the MCP in their client, sees an OAuth error ("access denied", "invalid_grant", a failed redirect), or keeps getting asked to log in again. You may also offer it after a hard MCP tool failure. It confirms the exact content with the user and redacts secrets before anything is stored.
Install
With your agent
Install OMGSkills skill "unbounce/agent-plugins:plugins/unbounce-mcp/skills/mcp-feedback" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/unbounce/agent-plugins /tmp/agent-plugins && ln -s /tmp/agent-plugins/plugins/unbounce-mcp/skills/mcp-feedback ~/.claude/skills/mcp-feedbackFrom README
Submit Unbounce MCP feedback Record the user's feedback about the Unbounce MCP tools to the team's store by calling the submitfeedback tool. The tool persists the record server-side, so nothing has to be copied out of the conversation into Slack or anywhere else. The mcp- prefix here means "pertains to Unbounce MCP," not "about a page." This skill is about capturing feedback on the MCP tools themselves — whether they broke, delighted, confused, or fell short. Hard rule: report, don't repair Do NOT try to fix, retry, or work around the thing being reported. This skill records feedback on what already happened. Never invent tool-call arguments or error text — anything not actually present is unknown. (Fixing the underlying task, if the user wants that, is separate work done after the feedback is recorded.) Gather the feedback Settle two things — from the conversation where possible, asking only what you can't infer: type — one of bug · praise · featurerequest · confusion · other.