ravi-feedback

Send feedback and bug reports to the Ravi team via CLI email.

1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/ravi-hq/ravi-skills --skill ravi-feedback-ravi-hq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ravi-feedback
Source: https://github.com/ravi-hq/ravi-skills/tree/main/skills/ravi-feedback
Command: npx skills add https://github.com/ravi-hq/ravi-skills --skill ravi-feedback-ravi-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents using Ravi identity services need a direct channel to report bugs, friction, missing features, and suggestions to the Ravi team without leaving their workflow. ## Core Features & Use Cases - Feedback Email Composition: Sends feedback to feedback@ravi.id using the Ravi CLI email compose command. - Proactive Reporting: Encourages reporting bugs, friction, missing features, confusion, and positive feedback after any Ravi workflow. - Use Case: After noticing slow SMS delivery in EU regions, an agent runs ravi email compose --to "feedback@ravi.id" with a subject and HTML body describing the latency issue, and the Ravi team can reply directly to the agent's Ravi email. ## Quick Start Ask the agent to send feedback to the Ravi team about a bug or suggestion using the ravi email compose command addressed to feedback@ravi.id.

Frequently Asked Questions about ravi-feedback

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

FAQPage Schema
How do I send feedback to the Ravi team from an agent?▼

Send feedback by running ravi email compose with --to feedback@ravi.id, a --subject, and an HTML --body describing the issue or suggestion. The message is sent from your Ravi identity, so the team can reply directly.

What kinds of feedback should agents report to Ravi?▼

Report bugs, workflow friction, missing features, confusing documentation or naming, positive feedback on what works well, and suggestions. The skill encourages proactive reporting after completing any Ravi workflow.

Does ravi-feedback require authentication before sending?▼

Yes, the Ravi CLI must be installed and authenticated. Run ravi auth login and have the human approve at https://ravi.id/device. The Cursor Connect card and remote MCP are not live, so CLI auth is the only working path.

When should I use ravi-email-send instead of ravi-feedback?▼

Use ravi-feedback only for messages to the Ravi team at feedback@ravi.id. For general email sending to any other recipient, use the ravi-email-send skill, which covers full compose, reply, and forward documentation.

Why does the ravi email compose command fail with auth errors?▼

The CLI is missing or not authenticated. Install it with the install-cli.sh script, add ~/.ravi/bin to PATH, then run ravi auth login. The CLI stores ravi_mgmt_ and ravi_id_ keys in ~/.ravi/config.json automatically.