Del archivo al resultado útil
Cómo pedir trabajo con esta skill instalada
Instalar la skill da un método a tu IA. Tu petición todavía debe aportar los hechos del caso, las restricciones y el entregable esperado.
1Nombra la tarea real
Describe la decisión o el entregable, no solo el tema.
2Aporta la información
Añade materiales, público, límites y hechos conocidos.
3Define qué significa acabado
Fija formato, criterios de calidad y comprobaciones.
Ejemplo de origen
Sustituye los corchetes por tu caso
Cuándo usarla
- Setting daily room rates for the next 90 days
- Evaluating a group booking request — should you accept it? At what rate?
- Managing channel mix: direct vs. OTA vs. GDS vs. wholesale
- Running a rate shopping analysis against the competitive set
- Setting up yield management restrictions (minimum length of stay, advance purchase)
- Planning pricing strategy for a high-demand event or holiday
- Calculating whether to accept a discounted group booking vs. selling the rooms individually
Errores que conviene evitar
- Opening OTA channels on high-demand nights without inventory restrictions — if you give an OTA 20 rooms on a night you're forecasting 95% occupancy and they sell 20 of them at $249, you've given away $40+/night in commission on rooms you could have sold direct at $319
- Ignoring the GDS channel for corporate business — a property that doesn't appear in the GDS (Amadeus, Sabre) won't receive corporate booking requests; GDS should always remain open for corporate accounts even when OTAs are closed
- Setting rates without checking your own website — the most common competitor to rate-shop is yourself; if your website is showing $299 for a date and the OTA shows $289, you're directing all your direct traffic to the OTA
- Accepting a group rate that doesn't account for the true displaced revenue — always do the displacement analysis before accepting any discounted group; the group rate that "looks fine" is often significantly below what those rooms would have earned at BAR