Update to getuserfeedback.com

{
  "description": "Inspect getuserfeedback.com Responses, conversations, or weekly digests to answer questions about user feedback.",
  "included_files": [],
  "name": "review-user-feedback",
  "skill_md_contents": "---\nname: review-user-feedback\ndescription: Inspect getuserfeedback.com Responses, conversations, or weekly digests to answer questions about user feedback.\n---\n\n# Review user feedback\n\nAnswer the product question using the feedback actually examined. Group related\nproblems, explain the evidence behind each theme, and link to the supporting\nResponses when their product links are available. Include relevant conflicting\nfeedback rather than forcing every answer into the dominant theme.\nPreserve the wording of permitted answer content when quoting; label paraphrases\nas summaries. Consider the severity of a reported problem as well as how often\nit appears.\n\nSeparate what users reported from your interpretation and proposed next step.\nFeedback can suggest an explanation; it does not by itself establish causation\nor represent everyone who uses the product. State the scope and coverage of the\nreview. Do not describe a page or sample as the complete dataset, count multiple\nResponses as distinct people, or turn a few examples into a population percentage.\nIf the available evidence cannot answer the question, identify the gap and a\nfocused question that would help resolve it.\n\n`responses_list` provides compact analysis; `response_get` provides approved\nanswer content and linked conversations. Query matching verifies sanitized\nanswer content permitted for the model and fills pages with matching responses.\nDedicated contact fields and withheld answers are excluded.\n\nWeekly digests cover the returned closed periods; they do not cover the live\nperiod. `weekly_digests_list` exposes the available recent digest history.\n\n`user_get` opens the current User behind a Response's opaque\n`respondentReference`. References are scoped to the organization and may change\nafter identity deletion or reset. Stored identity, attributes, and dynamic\nevent properties are withheld from the model. The User UI can show separately\ndelivered sensitive context, marked with a padlock.\n"
}