✓ Verified 💻 Development ✓ Enhanced Data

Reveal Feedback

Interact with Reveal feedback infrastructure to manage products, create review tasks, read AI-analyz

Rating
4 (299 reviews)
Downloads
817 downloads
Version
1.0.0

Overview

Interact with Reveal feedback infrastructure to manage products, create review tasks, read AI-analyzed user.

Complete Documentation

View Source →

Reveal Feedback Infrastructure

Reveal is a universal feedback platform where human reviewers screen-record themselves using products and provide AI-analyzed feedback. This skill connects to the Reveal REST API to manage the full feedback lifecycle.

Authentication

All API calls require the REVEAL_API_KEY environment variable. The key is a vendor API key generated from the Reveal dashboard under Settings → API Keys.

Every request uses this header:

text
Authorization: Bearer $REVEAL_API_KEY

Base URL: https://www.testreveal.ai/api/v1 (Override with REVEAL_BASE_URL env var if set.)

Capabilities

1. Check dashboard overview

Fetch products, active review tasks, and unread notifications to give the user a quick status update.

Steps:

  • GET /products to list vendor products
  • GET /review-tasks?status=active to list active tasks
  • GET /notifications?unread=true&limit=5 to get unread notifications
  • Summarize: product count, active tasks with submission progress, and recent notifications

2. Get feedback insights for a product

Fetch AI-aggregated insights: top issues, top positives, sentiment distribution, and suggestions.

Steps:

  • GET /products to find the product ID matching the user's request
  • GET /insights/{productId} to get aggregated insights
  • Present: sentiment breakdown, top issues ranked by frequency, top positives, unique issue count

3. Get product analytics

Fetch quantitative metrics for a product.

Steps:

  • GET /products/{productId}/analytics
  • Present: total submissions, analyzed count, average completion rate, sentiment distribution, top issues, top positives

4. View review submissions

Get individual review submissions with transcripts, AI analysis, sentiment, and issue counts.

Steps:

  • GET /review-tasks?status=active&limit=5 to find the relevant task (or use a task ID if provided)
  • GET /review-tasks/{taskId}/submissions to get all submissions
  • For each submission, present: status, sentiment, issue count, positive count, transcript preview

5. Create a review task

Create a new user-testing task so reviewers can test a product.

Steps:

  • GET /products to find the product matching the user's description
  • Extract from the user's message: title, objective, steps, feedback focus, reviewer count
  • POST /review-tasks with body:
json
{
  "title": "extracted title",
  "productId": "matched product ID",
  "requiredReviewers": 5,
  "instructions": {
    "objective": "what the reviewer should accomplish",
    "steps": "step-by-step instructions",
    "feedback": "what feedback to focus on"
  }
}
  • Confirm creation with task ID and details

6. Update a review task

Close, pause, or modify an existing review task.

Steps:

  • PATCH /review-tasks/{taskId} with fields to update (status, title, description, requiredReviewers)
  • Confirm the update

7. List products

Show all products registered on the vendor's Reveal account.

Steps:

  • GET /products?limit=50
  • Present each product: name, category, platform support (web/mobile), website

8. Get notifications

Check for new activity on Reveal.

Steps:

  • GET /notifications?unread=true&limit=20
  • Present notification messages with timestamps
  • If user says to mark as read: PATCH /notifications with {"markAllRead": true}

9. Register a webhook

Set up real-time event notifications.

Steps:

  • POST /webhooks with body:
json
{
  "url": "https://user-provided-url",
  "events": ["review.submitted", "review.analyzed", "task.completed", "video.generated"]
}
  • Return the webhook ID and signing secret. Instruct user to store the secret securely.

10. List webhooks

Steps:

  • GET /webhooks
  • Present each webhook: URL, subscribed events, active status

Response format

All API responses follow this structure:

  • Success: { "data": { ... } }
  • Error: { "error": { "code": "ERROR_CODE", "message": "description" } }

Guardrails

  • Never expose or log the API key in responses to the user
  • If an API call fails with 401, tell the user their API key may be invalid or expired
  • If a product is not found, suggest listing products first
  • When creating review tasks, always confirm the details with the user before sending the POST
  • Do not fabricate feedback data — only report what the API returns

Installation

Terminal bash

openclaw install reveal-feedback
    
Copied!

💻Code Examples

3. POST `/review-tasks` with body:

3-post-review-tasks-with-body.json
{
  "title": "extracted title",
  "productId": "matched product ID",
  "requiredReviewers": 5,
  "instructions": {
    "objective": "what the reviewer should accomplish",
    "steps": "step-by-step instructions",
    "feedback": "what feedback to focus on"
  }
}

1. POST `/webhooks` with body:

1-post-webhooks-with-body.json
{
  "url": "https://user-provided-url",
  "events": ["review.submitted", "review.analyzed", "task.completed", "video.generated"]
}

Tags

#web_and-frontend-development

Quick Info

Category Development
Model Claude 3.5
Complexity One-Click
Author tolulopeayo
Last Updated 3/10/2026
🚀
Optimized for
Claude 3.5
🧠

Ready to Install?

Get started with this skill in seconds

openclaw install reveal-feedback