Renderful Generation
PassAudited by ClawScan on May 1, 2026.
Overview
The skill is coherent for Renderful media generation, but users should notice the account, payment, generation, and webhook-related actions before approving them.
This appears safe to install as an instruction-only Renderful integration. Before use, review quotes before generation, approve any credit-spending or payment-related action, confirm the account/API key being used, and do not allow webhook setup unless you trust and control the destination.
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.
A generation request may consume credits or create media through the Renderful service.
The skill can trigger media generation, a side-effecting external action, but it explicitly instructs quoting first and later says side effects should wait for user approval.
Run `renderful_quote` before `renderful_generate`.
Approve generation only after reviewing the selected model, prompt/inputs, quoted cost, and expected output.
The agent may interact with a Renderful account, balance, or payment flow on the user's behalf.
The workflow can use or create Renderful account access, which is expected for the integration but involves delegated service authority.
Run `renderful_register_agent` if no API key is available.
Confirm which Renderful account or API key is being used before registration, balance checks, payment handling, or generation.
If used, generation status or related data could be sent to a configured webhook endpoint.
Webhook setup is listed as an available plugin tool, which can create an external callback/data flow, but the artifact does not instruct automatic use.
- `renderful_set_webhook`
Only set a webhook when the destination URL, ownership, data sent, and purpose are clear and explicitly approved.