From file to useful result
How to ask with this skill installed
Installing the skill gives your AI a method. Your request still has to provide the case-specific facts, constraints and expected output.
Describe the decision or deliverable, not just the topic.
Add source material, audience, limits and known facts.
Set format, quality criteria and checks.
When to use it
- Weekly review of all guest feedback to identify urgent issues
- Monthly sentiment analysis to identify trends and systemic problems
- Tracking the impact of a recent operational change (renovation, new service, staff change)
- Investigating a specific complaint category (e.g., "the elevators are slow again")
- Identifying top-performing staff for recognition programs
- Preparing a guest experience report for management or ownership
Mistakes to avoid
- Reporting feedback data without investigating the root cause — "we got 8 AC complaints this week" is useless without knowing WHY; always pair the complaint count with the investigation
- Responding defensively to negative reviews on public platforms — never argue with a guest's experience; acknowledge it, apologize for it, and explain what you're doing to prevent it; a defensive response makes the situation worse and becomes the story instead of the original complaint
- Not tracking positive staff mentions — feedback about specific staff members is the most valuable data you have; if a guest praises "Sarah at the front desk" by name, that needs to go into Sarah's file and Sarah's manager needs to know
- Ignoring neutral/passive feedback — the 3-star reviews contain the most actionable data; these guests weren't upset enough to complain, but weren't happy enough to become promoters; contact them directly and ask what would have made their experience better
- Compiling a feedback report that nobody acts on — if the report goes to management and nothing changes operationally as a result, you are wasting everyone's time; every report should have 3 maximum action items with owners and deadlines