Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Interact with Reveal feedback infrastructure to manage products, create review tasks, read AI-analyzed user feedback, get sentiment insights, view submission...
Interact with Reveal feedback infrastructure to manage products, create review tasks, read AI-analyzed user feedback, get sentiment insights, view submission...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
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.
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: Authorization: Bearer $REVEAL_API_KEY Base URL: https://www.testreveal.ai/api/v1 (Override with REVEAL_BASE_URL env var if set.)
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
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
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
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
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: { "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
Close, pause, or modify an existing review task. Steps: PATCH /review-tasks/{taskId} with fields to update (status, title, description, requiredReviewers) Confirm the update
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
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}
Set up real-time event notifications. Steps: POST /webhooks with body: { "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.
Steps: GET /webhooks Present each webhook: URL, subscribed events, active status
All API responses follow this structure: Success: { "data": { ... } } Error: { "error": { "code": "ERROR_CODE", "message": "description" } }
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
Data access, storage, extraction, analysis, reporting, and insight generation.
Largest current source with strong distribution and engagement signals.