ghost-exo
exo
One front door for the exo workflow lifecycle. This skill is a router. It classifies the request into one of three intents, loads the shared substrate, then loads the matching intent recipe and follows it.
Prerequisites
Exo is an agent workflow platform. Every intent drives it through an exo MCP server.
Pick the connection
Several exo connections coexist normally, one per workspace, sometimes several on one deployment. Enumerate the exo MCP servers this session has before doing anything else.
With exactly one, use it. With more than one, ask which through the structured question tool and stop until the user answers, because a wrong guess writes to the wrong workspace. Do not switch connections partway through an intent. Start over if the target changes.
Call whoami on the chosen server. It confirms the connection and returns the workspace ID. Report that ID so the user can see which workspace they are about to change. If no exo MCP tools are present or whoami fails, read resources/bootstrap.md and follow it, then call whoami again. Do not classify an intent until it succeeds.
scripts/exo-skill.py reaches the same workspace over REST, and it has to reach the same one. It reads EXO_API_URL, EXO_API_KEY, and EXO_WORKSPACE_ID from the process environment, falling back to the profile named by --profile, which is the file ${XDG_CONFIG_HOME:-~/.config}/exo/<name>.env. Pass --profile with the name of the MCP server you chose on every call, so the two cannot point at different workspaces.