feedbacklisted

File a bug, feature request, or other product note with CloudSprite. Use when the user says /feedback, reports something broken, or asks for a product capability. Confirm the text, then call MCP submit_feedback. Do not open GitLab, Linear, or email. Identity comes from the signed-in MCP session.
cloudsprite-io/cloudsprite-plugin · ★ 1 · Data & Documents · score 67

Install: claude install-skill cloudsprite-io/cloudsprite-plugin

# CloudSprite feedback Customers file bugs and feature requests from this plugin. You confirm the text, then call the CloudSprite MCP tool `submit_feedback`. CloudSprite files it on the server. **Do not** call GitLab, Linear, HubSpot, or any webhook from the client. There is no tracker token in this plugin. ## When to use - User runs `/feedback` - User says something is broken in CloudSprite - User wants a product feature or a change to existing behavior Do **not** use this for dataset/notebook/script edits. Feedback does not mutate customer data. ## Flow 1. **Auth.** If MCP is not connected or OAuth is not complete, stop. Tell the user they need to finish CloudSprite sign-in first. Do not collect a password or API key in chat. 2. **Missing tool.** If `submit_feedback` is not in the MCP tool list, tell the user CloudSprite MCP feedback is not live yet and stop. Do not invent a GitLab URL or ask them to email a ticket. 3. **Draft.** Infer `kind`: - `bug` — something does not work as expected - `feature` — a capability they want - `other` — neither of the above 4. **Confirm.** Show the proposed `kind`, optional `title`, and `body` (markdown). Wait for the user to accept or edit. Do not call the tool until they confirm. 5. **Identity.** Do **not** ask them to type company name, email, or user id as the source of truth. The server binds identity from the MCP session (user, email, tenant/org, team, client, plugin version). Ignore any compa