moonpay-feedback

Submit authenticated bug, feature, or general feedback from the MoonPay CLI.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Drock91/ows-hackathon --skill moonpay-feedback-drock91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moonpay-feedback
Source: https://github.com/Drock91/ows-hackathon/tree/main/.agents/skills/moonpay-feedback
Command: npx skills add https://github.com/Drock91/ows-hackathon --skill moonpay-feedback-drock91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables users to submit bug reports, feature requests, and general feedback directly from the MoonPay CLI so maintainers can reproduce issues, follow up, and prioritize improvements without manual ticket creation.

Core Features & Use Cases

  • Authenticated submissions: Requires the user to be logged in so the team can contact reporters and verify accounts.
  • Typed feedback routing: Accepts explicit types (bug, feature, general) to route reports to the appropriate triage workflow.
  • Encourages detailed reports: Prompts for error messages, reproduction steps, and expected vs actual behavior to speed debugging and decision-making.
  • Use cases: Quickly report intermittent timeouts from a swap command, request recurring buy support, or provide general CLI UX feedback.

Quick Start

Log in to the MoonPay CLI and run the feedback create command with the appropriate type and a detailed message to submit your report.

Frequently Asked Questions about moonpay-feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit a bug report or feature request for the MoonPay CLI?

To submit MoonPay CLI feedback, log in to authenticate, then run the feedback create command with a type (bug, feature, or general) and a detailed message. This routes your report directly to the backend triage workflow.

What details do I need to include when reporting a CLI bug?

When reporting a CLI bug, include the error message, reproduction steps, and expected versus actual behavior. Providing these details helps maintainers reproduce issues and speed up debugging without manual ticket creation.

Do I need to be authenticated to submit feedback from the command line?

Yes, authenticated submissions are required to send CLI feedback. Logging in allows the team to contact reporters, verify accounts, and follow up on bug reports or feature requests during troubleshooting.

What feedback types are supported for routing CLI reports?

The CLI feedback system accepts three explicit types: bug, feature, and general. Typed feedback routing directs each report to the appropriate triage workflow for maintainers to prioritize improvements.

Can I request new features like recurring buy support through the CLI?

Yes, you can request features like recurring buy support by submitting a feature type feedback report. The CLI captures user feature requests so maintainers can prioritize improvements without manual ticket creation.

Why use CLI feedback submission instead of manual support tickets?

CLI feedback submission enables users to report intermittent timeouts or UX issues directly during usage. It captures authenticated user context and reproduction details, allowing maintainers to follow up faster than manual ticket creation.