Render HTML

For each Creative Claw tool call that exposes it, pass the optional skills_used array with creativeclaw-render-html, any other Creative Claw skills actually followed, and guide entries in the form <skill-name>/<relative-guide-path> (for example, creativeclaw-render-html/references/workflow-basics.md). Include only skills and guides followed for that call. Omit attribution if the user declines tracking or the field is unavailable. Never send other plugin names, private data, or local paths.

Not connected yet? If no Creative Claw tools (such as list_models or generate_image) are available, the plugin is installed but the server is not connected. Stop and tell the user to open the plugin's Connectors tab in their app (or the MCP server list in a terminal client), connect Creative Claw, sign in, and ask again. Do not substitute other tools or describe a result that was not generated.

Read shared execution guidance once per task before using tools. It covers existing authorization, model discovery, optional cost checks, imports, and recovery.

Three tools:

• render_html_image: a fixed-size HTML/CSS layout to a PNG. It completes synchronously; do not call check_job for it.
• generate_html_video: Creative Claw's own video agent makes a motion-graphics video. It writes the HyperFrames composition, makes the images, voiceover, music and sound it needs, checks the result, and renders it. You send a prompt, not HTML.
• render_html_video: renders a HyperFrames HTML/CSS/JS composition or project ZIP you supply. It returns a queued job; resolve it with check_job when the final URL is needed.

Which video tool: use generate_html_video unless the user supplied the HTML or project, or you have HyperFrames authoring skills installed in this session (a hyperframes skill in your skill list) and can write and check the composition yourself; in that case author it and use render_html_video. If the user asks for one of the two, follow that.

Older clients may not list generate_html_video. There the same agent is render_html_video with method: "generate", method: "edit" (with cloud_project_id) and method: "status".

This is an explicit-only route. A poster, banner, social card, overlay, intro, outro, or video that needs text is not by itself a reason to use it. Use creativeclaw-generate-image or creativeclaw-generate-video unless the user asks for HTML, CSS, HyperFrames, or code-driven rendering, supplies HTML, accepts the method when offered, or explicitly asks for motion graphics, kinetic typography, animated titles, or an animated explainer. If the user names an image or video model, that choice wins.