qntweb/simplebooking
SimpleBooking data analysis skills (reservations, revenue, content, demand) for hotel customers, built on the IBE and BackOffice MCP connectors.
Diagnostic over three terms: the destination's demand, the searches on the property's own booking engine, and actual Back Office reservations. Says whether a property captures its destination's demand and, when it doesn't, which leg loses it — visibility or conversion. Orchestrates sb-revenue-lens (area demand, availability, restrictions, parity) and sb-reservation-insights (pickup, channel mix, markets, lead time), and owns first-party demand directly. Use ALWAYS for: "am I keeping up with the market", "I have demand but I'm not selling", "do they even find me", "searches that found nothing", "requests I turned away", "who searches vs who books", "am I opening sales too late", "which property captures demand best". Do NOT use for: a single metric in isolation (sb-reservation-insights); demand, availability or price without sales (sb-revenue-lens); the fixed weekly brief (sb-monday-brief); direct booking provenance (sb-direct-attribution).
Structured audit of hotel content on the SimpleBooking platform. Checks missing translations, text quality, and information completeness across all enabled languages. Use when the user asks to check, audit, or verify content, translations, or localization of a hotel on SimpleBooking, or mentions "content audit". Trigger italiani: verifica traduzioni, controllo contenuti hotel, auditare i contenuti.
Query a hotel's reservations via run_reservation_aggregation of the Simple Booking BackOffice MCP, for management, revenue management, front office and marketing. USE FOR: pick-up, on the books, "how is the month going", year-over-year pace, channel mix, direct vs OTA, commission cost, portal performance, cancellations, booking window, last minute, length of stay, MinLOS, arrivals and departures, in-house guests, source markets, ancillary services, payment methods; also any question on reservations, rooms sold, ADR or revenue without naming the tool. Trigger italiani: camere vendute, come sta andando settembre, siamo avanti o indietro, quanto mi costano le OTA, anticipo di prenotazione, permanenza media, arrivi e partenze, presenze in casa, mercati di provenienza. NON per: provenienza del diretto, UTM, campagne (sb-direct-attribution); date chiuse (sb-inventory-guard); tariffe e domanda d'area (sb-revenue-lens); traffico AI (sb-ai-traffic); sito (sb-website-audit); domanda vs vendite (sb-demand-capture).
Demand-driven revenue diagnostic for hotels, SimpleBooking MCP only. The user asks a question about a hotel+period and the skill cross-references area demand, availability, restrictions and prices: answer in chat, branded report on request. Use ALWAYS for: "where am I losing money", "unsold risk", "weak dates", "my restrictions", "MinLOS", "minimum stay", "direct vs OTA", "rate parity", "which dates do I still have rooms", "how much lead time do I have", "revenue opportunity", "money leak", "requests I turned away", "searches that found nothing", "period check", "analyze period X". Do NOT use for: events (sb-event-radar), AI traffic (sb-ai-traffic), content audit (sb-hotel-content-audit), site crawl (qnt-site-inspector), comparison with actual reservations (sb-demand-capture).