Reveal Reviewer skills
Analysis
The skill is a coherent Reveal review helper, but it should be reviewed carefully because it can use your Reveal API key to create and submit persistent review records and screenshot links without a clear final confirmation step.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
"Fallback" ... "If no matching/aligned task exists, use Proactive Self-Review Mode" ... "POST `/self-reviews`" ... "Step 5: Submit the review" ... "POST `/submissions`"
The workflow authorizes the agent to switch into a write path and create or submit review records through the external API. The artifact shows the write operations but does not clearly require the user to approve the proactive self-review creation or final submission payload first.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
"REVEAL_REVIEWER_API_KEY" environment variable ... "Authorization: Bearer $REVEAL_REVIEWER_API_KEY"
The skill uses a Reveal reviewer API key for authenticated calls. This is expected for the integration, but it gives the agent delegated authority over the user's reviewer account actions.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
"Take a screenshot using agent-browser's snapshot feature" ... "Screenshots should be URLs if your agent-browser supports image capture/upload"
The skill relies on another browser automation skill to capture screenshots and may submit uploaded screenshot URLs to Reveal. This is purpose-aligned, but the screenshot storage/upload boundary is not fully described in the artifact.
