DatoCMS Feedback

Prefilled datocms.com/support URL when a DatoCMS skills/MCP workflow is stuck. Escape hatch, not a fixing workflow.

Before doing anything visible

• User explicitly asked to report/file/summarize feedback about DatoCMS skills/MCP → generate immediately.
• Frustration or dead end inferred → do not generate. Offer once, wait for confirmation.
• Credible retry exists → do not mention feedback. Stay in the active DatoCMS workflow.

Not for trial-and-correction. Single failed command, MCP call, API error, validation response, schema miss, missing env value, or setup failure stays with the active workflow when a retry path exists.

Project/schema/frontend/migration/plugin issue still fixable → route to the relevant DatoCMS skill.

If frustration is inferred

Offer once, then wait: