skills/creativeclaw/references/workflows/feedback.md

# Product feedback workflow

Use `submit_feedback` to help the Creative Claw team improve the product without derailing the user's media task. Sending feedback contacts the Creative Claw team, so do it only when the user asks or approves.

A complaint, wish, compliment or account question alone is not permission to send a report. Offer to report meaningful issues and wait for approval unless the user already explicitly asked. Feedback is not a refund request form.

## When to submit

- A tool errors, returns the wrong result, or forces a workaround → `category: "bug"`.
- The user requests a feature, workflow, or model that is unavailable → `category: "missing_feature"`.
- A tool, parameter, result, or workflow is difficult to understand → `category: "confusing"`.
- A completed image, video or speech result misses creative expectations without a confirmed technical malfunction: `category: "generation_quality"`. Use `bug` for concrete technical failures, not subjective dissatisfaction.
- The user explicitly praises an outcome or workflow → `category: "praise"`.

Common reports include generation artifacts, identity or style drift, poor lip-sync or audio, unexpected model behavior, missing editing controls, requests for a new image/video/speech model, and unclear errors.

## Charges, improvement and critical issues

Generations that successfully produce a playable video output are charged even if the user is not fully happy with the creative result. Explain this empathetically when relevant, not as a dismissal of the problem. Sending feedback helps us improve the system for future generations; it does not itself issue a refund, reverse a charge, promise a fix or authorize another paid attempt.

Use `generation_quality` for disappointing creative results without a confirmed technical malfunction. Failed, corrupted or unplayable output is a different issue; do not label it a successful generation merely because a URL exists. Use `manage_account({ section: "activity" })` to verify the specific job's actual charges and refunds rather than guessing from its status.

For critical issues, users can also contact [support@creativeclaw.co](mailto:support@creativeclaw.co). Suggest including the relevant job ID and a short description, without passwords, payment details or private source recordings. Do not promise a response time, refund or resolution, and do not send an email on their behalf unless requested.

## How to submit

1. State the attempted task and the exact observed problem or request.
2. Include the model ID, operation, and relevant settings when known; do not include credentials, private media, or unnecessary personal data.
3. Use `source: "agent"` for friction you observed and the user approved reporting. Use `source: "user"` when relaying the user's own words or intent.
4. Send one concise, specific report. Do not submit duplicates for the same incident.
5. Treat it as fire-and-forget. Continue the user's task and do not promise a response or resolution.

Examples:

```text
submit_feedback({
  category: "missing_feature",
  source: "user",
  attemptedTask: "Generate a cinematic product clip with a requested model",
  message: "User requested support for [model ID/name], which is not in the current video catalog."
})
```

```text
submit_feedback({
  category: "generation_quality",
  source: "agent",
  attemptedTask: "Preserve a Character's face in image-to-video",
  message: "[model ID] completed, but the face changed substantially despite the approved Character reference."
})
```