| name | suxi-ota-revenue-semantic-layer |
| description | 用于回答宿析OS OTA数据、收益指标、AI决策支持、运营执行闭环、定价建议、投资或转让决策相关的数据分析问题。 |
SUXIOS OTA Revenue Semantic Layer
Use this skill before choosing SUXIOS metrics, tables, source precedence, joins, or caveats for analytics work across:
OTA data -> revenue analysis -> AI decisions -> operations management -> investment decisions
Plugin Priority
Use suxi-plugin-priority-router when analytics outputs should become dashboards, reports, worksheets, or decks. Prefer Data Analytics for source-backed reports/dashboards and Spreadsheets for calculation-ready metric tables.
Start Here
- Read
references/semantic-layer.md.
- Use the listed canonical metrics, tables, grains, filters, and caveats.
- Treat the layer as source-selection guidance, not as a substitute for live reads from the database, API, dashboards, or provided exports.
- When source coverage is weak, stale, or conflicts with live data, say so and verify against the cited source.
References
references/semantic-layer.md: metric definitions, tables, query patterns, gotchas, and open questions.
references/source-inventory.md: sources checked, coverage level, gaps, and update boundaries.
references/evidence.md: provenance for the key claims this layer preserves.
Answering Rules
- Keep OTA-channel metrics separate from whole-hotel operating metrics.
- Do not turn missing denominators, failed collection, or absent fields into
0.
- Preserve metric grain, date rules, platform scope, source trace IDs, and data-quality statuses.
- Treat AI outputs as recommendations that need source references, confidence handling, and human confirmation when they affect operations or investment decisions.
- Treat pricing and execution outputs as advisory or manual-review workflows unless a real OTA write-back API, approval, and execution evidence are available.