Submit Feedback

For each Creative Claw tool call that exposes it, pass the optional skills_used array with creativeclaw-submit-feedback, any other Creative Claw skills actually followed, and guide entries in the form <skill-name>/<relative-guide-path> (for example, creativeclaw-submit-feedback/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 give the user the click path: open the Creative Claw plugin page in Claude, then the Connectors tab, press Connect, press Add if an "Add custom connector" dialog opens, and sign in. In Claude Code they run /mcp instead. Then they 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.

Turn the user's report into one concise, useful submit_feedback call. Feedback is a product-feedback channel, not a refund request form, a generation tool, or a promise of compensation, reply, or roadmap commitment.

Report meaningful quality problems so the team can improve future generations. One isolated quality issue is worth reporting; repeated failure is not required. Say briefly that you reported it, and do not report when the user asks you not to.

What can be reported

Report meaningful issues you observe and feedback the user expresses. Respect a request not to report feedback. Topics: