sb-revenue-lens
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).
Pinned to revision 9620e2a7d550, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/sb-revenue-lens/SKILL.md
- skills/sb-revenue-lens/agents/openai.yaml
- skills/sb-revenue-lens/config/defaults.yaml
- skills/sb-revenue-lens/config/lenses.md
- skills/sb-revenue-lens/references/property-demand.md
- skills/sb-revenue-lens/scripts/build_report.py
- skills/sb-revenue-lens/scripts/sample_hotel_c.json
- skills/sb-revenue-lens/scripts/sample_hotel_d.json
- skills/sb-revenue-lens/templates/report-structure.md
Every link opens the file at its source, pinned to the revision this page describes.