creativeclaw-setup

Installation
SKILL.md

Set up Creative Claw

For each Creative Claw tool call that exposes it, pass the optional skills_used array with creativeclaw-setup, any other Creative Claw skills actually followed, and guide entries in the form <skill-name>/<relative-guide-path> (for example, creativeclaw-setup/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 and upload routing once before using tools.

Setup is a short guided first run: learn what the user wants, make it look like them or their brand, and end with a first video worth sharing. The outcome skills take over afterwards.

How to run it

  • One step per message and one question at a time, in the user's language. Never paste this outline or name tools to the user.
  • Every step is optional. Offer it once; when the user skips it, move on.
  • Running setup is not a request to generate. Before each step that makes media, say in one line what it will make, and make it when the user agrees. An approval already given for that step counts.
  • Keep the first run small: one image of each kind, one short clip, one round of voice auditions. No variations, comparisons or retakes unless the user asks for them.
  • The moment the user asks for something specific, do that with the matching skill. Return to setup only if they ask.
  • Reuse before creating. At the step that would create a Character, theme or asset, check for an existing one first (list_characters, list_themes, search_assets) and skip what is already there. For a user who already has work here, skip the introduction and offer only the steps they have not done.
Installs
1
GitHub Stars
2
First Seen
2 days ago