Cube agent skills run in your coding agent. They are not Agent Skills in Cube, which your data team authors in the semantic model and runs from Analytics Chat.
Choose the right Cube integration
Install
Claude Code
Run these commands inside Claude Code:/mcp, select plugin:cube:cube, and sign in to Cube. Some skills also need the
Cube CLI.
The plugin uses the same endpoint as the Cube connector, so you don’t need both. For how
Claude Code handles a server that is configured twice, see
MCP scope precedence.
Codex, GitHub Copilot, Gemini CLI, and other compatible agents
Install the skills from skills.sh:cube-js/cube-agent-skills.
Install the Cube CLI
The skills use the Cube MCP server when it is connected, and the Cube CLI otherwise. The CLI is required forcube-admin, cube-embed, and most of cube-deploy, and for finding
saved content with cube-explore-content — work the MCP server does not cover.
On Linux or macOS, run:
CUBE_API_URL and CUBE_API_KEY instead. See
Cube CLI authentication for both methods.
Available skills
Use the skills
Skills activate automatically when a request matches their description. You can also name a skill explicitly:Troubleshooting
- Cube tools are missing in Claude Code: Run
/mcp, selectplugin:cube:cube, and sign in. - The agent says the Cube CLI is missing: Install it from the Cube CLI reference, then start a new agent session.
- CLI authentication fails: Run
cube whoami. If needed, sign in again withcube login --url https://TENANT.cubecloud.dev. - The request targets the wrong tenant: Run
cube context listand tell the agent which context to use. - A skill does not activate automatically: Name it in the request, for example,
Use cube-explore-model to find the revenue measure.