Loading...
Loading...
Found 2 Skills
Run queries against a Cube deployment's semantic layer and interpret the results, from the terminal. Use whenever someone wants numbers out of Cube — pull a metric, check a total, compare periods, verify that a measure returns what it should, sanity-check a model change. Triggers on "how many", "what's the total", "show me revenue by month", "did that measure work", "what's our MoM growth", "pull the numbers for", and any request to verify a model change against real data. To find out what is queryable first use cube-explore-model; to change the model use cube-build-model; to save a result as a report or dashboard use cube-build-content.
Create, read, and edit RevOS tables (scoring models), and scope their rows with a segment, through the RevOS MCP server. A table's rows come from a cube, and its columns are read from cubes, stored in RevOS, or filled by actions. Use this whenever the user wants a table or list in RevOS ("make a table of our companies", "a table of the stalled deals"), wants to add, change, rename, hide, or remove a column, pull a field from a related object into a table ("add the company's industry to the deals table"), add an action column, see how a table is built, or delete a table, even if they never say the word "table". Read it before the first api_write on the `tables` or `table-views` resource.