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
- Creating a new seasonal package (summer, winter holiday, Valentine's Day)
- Building a packages for a corporate group or wedding party
- Designing a spa and dining weekend package for the hotel's direct booking channel
- Pricing a package that competes with OTA package rates
- Reviewing existing package performance to retire or refresh underperforming packages
- Training front desk agents on package upsell conversations
Mistakes to avoid
- Building packages that require the guest to do too much work to redeem components — if the guest has to book their own spa treatment, call the restaurant for reservations, and coordinate their own activity, the package creates stress rather than luxury
- Not tracking package components in the PMS — when a housekeeper doesn't know the guest has a champagne amenity because it wasn't noted in the system, the guest arrives and the amenity isn't there; every component must be tracked and actioned
- Pricing packages to match or beat OTA prices without accounting for commission — an OTA package at $250 with 20% commission is not the same as a direct book at $250 with no commission; your direct package must be ABOVE the OTA net price or you're better off with the OTA taking the booking
- Over-packaging (too many components) — guests buy packages for the headline benefit, not the long list of add-ons; 3 well-chosen components beat 7 mediocre ones
- Not setting minimum length of stay (MLOS) requirements — packages should drive incremental revenue, not simply replace full-rate short stays with discounted multi-night stays