---
name: estudio-creativo
description: "Crea o edita recursos visuales de marca con Kie; consulta modelos y costos y guarda entregables para campañas, webs y apps. Úsalo al pedir recursos con Kie o invocar /estudio-creativo."
---

# Creative studio with Kie

Use this project’s official kie-models integration. Read the course INSTRUCCIONES.md for setup and budget rules. This template is not a connected tool until the integration and authentication have been verified; do not invent a successful setup.

1. Resolve the creative brief: purpose, audience, brand references, desired treatment, output format, destination and quantity. Infer routine details from supplied context; ask only for information that materially changes the result.
2. Query the live Kie catalog and current model schema. Select an appropriate model for the task (generation, reference edit, image-to-video, music or speech) and supported resolution/duration. Explain the choice in one plain sentence. Never treat one remembered model name as permanent or claim it is universally best/cheapest.
3. Quote quantity, credits and USD before any paid task. Use the user’s explicit per-task and aggregate authorization. If the request has no concrete budget approval, present the quote and wait. Do not top up, start batches or change model/price after acceptance without resolving the new scope.
4. Execute the accepted task through the configured tool. Read KIE_API_KEY from the private environment only; never request it in chat, expose it, embed it in files, or place it in a web client. Reference files leave the machine; upload only the specifically approved material.
5. Save the accepted task ID immediately in a private record. Check the API application status as well as HTTP status, poll the same task and download only when it succeeds. Inspect an ambiguous timeout before retrying. Never announce success merely because a request was accepted.
6. Check the downloaded media: correct format, dimensions/duration, completeness, requested content, spelling, brand fidelity and differences from the input. Report limitations honestly. A 3D-looking image is not an editable 3D model.
7. Save inputs, outputs and revisions under the requested project path without overwriting originals. Keep a private generation manifest; export only sanitized public materials. Explain the result and the next useful adjustment briefly.
8. When integration is requested, help Claude build the actual project workflow; the skill itself is not a public API or always-running process. Use server-side secrets, authenticated requests, bounded budgets and recoverable task tracking. Do not deploy, publish, send messages or schedule automatic jobs unless those actions are requested.