Update to getuserfeedback.com

{
  "description": "Create or edit getuserfeedback.com Flows to collect product feedback. Use when a user wants to ask their users a question or change an existing Flow.",
  "included_files": [],
  "name": "collect-product-feedback",
  "skill_md_contents": "---\nname: collect-product-feedback\ndescription: Create or edit getuserfeedback.com Flows to collect product feedback. Use when a user wants to ask their users a question or change an existing Flow.\n---\n\n# Collect product feedback\n\nStart from what the user wants to learn or decide. When that is clear, propose\na short Flow rather than turning setup into a questionnaire for the user.\nAsk about one thing at a time, use neutral wording, and keep the effort\nproportionate to the question. Prefer a concrete recent experience over a\nhypothetical prediction. A low rating can identify a problem without explaining\nits cause. An open question can help uncover what to investigate next.\nKeep wording and scales consistent when comparing results over time. Consider\nwho can see the Flow and when they see it: an in-app question cannot reach\npeople who never return. Avoid collecting personal information the question\ndoes not need.\n\nWhen improving an existing Flow, preserve questions and settings unrelated to\nthe requested change. Edits to a live Flow take effect immediately, so say so\nbefore changing one. Saving a Flow's first delivery rule makes it live. Explain\nthe chosen delivery surface and audience without assuming they are already\nconfigured.\n\n`flow_templates_list` returns actionable template IDs. `flow_create` accepts\neither a template or custom pages, not both. Flow content is page-first. The\nschema and editing semantics are at `getuserfeedback://docs/flow-content`.\n\n`flow_get.flow.editableContent` is the safe editing projection. Its `versionId`\nis the revision required by `flow_content_update`. Null means the content is\nunavailable for editing through MCP. `currentVersion` is a read projection and\nmay contain omissions.\n\nLaunch surface, delivery rule, and live window are distinct settings.\n`flow_get` exposes them through `launchPlan`, `flowSchedule`, and\n`deliveryRuleAuthoring`. Delivery-rule edits replace the complete rule and use\nits automation version ID. Launch and rule changes can return\n`confirmation_required` when they affect pending deliveries.\n\nA `cacheInvalidationWarning` describes a committed write whose cache refresh\nfailed, rather than a failed write.\n"
}