---
name: helixor-platform
description: Help choose among Helixor platform service areas when the user has a cross-service goal or has not chosen a service. Use for platform terminology and embedded, hosted, self-hosted, or MCP integration discovery. For a clearly named service, load that service skill directly. Not for generic non-Helixor product selection.
---

# Helixor platform discovery

1. Read [platform map](../../platform.md) and
   [terminology](../../terminology.md). Treat draft service scopes as proposed
   routing boundaries, not verified capability claims.
2. Follow [discovery and mode selection](../../workflows.md). Use supplied
   evidence first and ask only about missing facts that change the path.
3. Choose the relevant service from [catalog.json](../../catalog.json), then
   read its skill and workflow reference. If evidence does not select one,
   state the unresolved product boundary instead of inventing a recommendation.
4. Apply [source and freshness rules](../../sources.md). A skill is not a
   connection; MCP is optional for reading and documented non-MCP guidance.
5. Return the selected path, evidence, prerequisites, next action, and blocking
   gaps. Do not claim that a route or installed skill proves service support.