Loading...
Loading...
Found 8 Skills
Create, edit, and troubleshoot RevOS segments — saved audiences defined over the org's semantic model — through the RevOS MCP server, and attach them to a table so its rows are scoped. Use this whenever the user wants to save, define, or change an audience or list ("companies with an active subscription", "deals over 50k in the EMEA pipeline", "users who ordered twice"), add or change a condition on an existing segment, show only some rows in a table ("only the stalled deals", "filter this table to…"), or asks why a segment is FAILED, empty, or showing the wrong rows — even if they never say the word "segment". Read it before the first api_write on the `segments` or `table-views` resource.
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.
Read, create, edit, and delete the cube definitions behind an org's RevOS semantic model, through the RevOS MCP server. Use this whenever the user wants to change what the semantic model contains, even if they never say "cube": model a new table or source stream ("make HubSpot tickets queryable"), add or fix a dimension or measure ("add a revenue sum", "the close date should be a time field"), join two cubes ("link deals to companies"), rename or remove a field, delete a cube, see how a cube is defined ("show me the SQL behind crm_deals"), or find out why the semantic model or a table suddenly fails to load. Read it before any api_write or api_delete on the `cubes` resource. For answering business questions from the data, use query-semantic-model instead; for audiences, use segments.
Read, build, and fix RevOS dashboards of metric cards through the RevOS MCP server. A card is one metric (a numeric measure), counted over a segment's rows or the card's own conditions, optionally broken down by a dimension. Use this whenever the user wants to see what's on a dashboard ("what's on our sales dashboard", "what does the pipeline card show"), put a metric or KPI on one ("add open pipeline to the board", "add revenue by stage as a donut"), change, reorder, move, or remove a card, create, rename, or delete a dashboard, or asks why a card shows "unavailable" or a number that looks wrong — even if they never say "dashboard" or "card". Read it before the first api_write or api_delete on `dashboards` or `dashboard-cards`.
Run a Cube.js query against the semantic model and show the result inline in chat as an ASCII table and (where it makes sense) an ASCII bar chart. Use whenever the user asks a business question that can be answered from the cubes — "how many orders…", "top N…", "revenue by…", "trend over time", "compare X to Y" — or explicitly asks to "query the semantic model", "run a cube query", "show me a chart", "plot…", "graph…". Discovers measures and dimensions via `revos cubes meta`, executes the query with `revos cubes query`, and renders the results without leaving the chat.
Inspect, run, and debug RevOS actions — the operations an integration performs per table row (sync a company to NetSuite, enrich a contact, push a deal to HubSpot) — and their runs, through the RevOS MCP server. Use this whenever something failed, did not sync, or came out wrong ("why didn't this deal reach NetSuite?", "the sync is red", "what does this error mean?"), when the user wants to see which actions exist or what an action column did, or wants an action run or re-run for some or all rows — even if they never say the word "action". Read it before the first api_read or api_write on the `action-runs` resource.
Answer business questions about the org's RevOS data directly in chat by querying its live semantic model over MCP — "how many orders…", "revenue by…", "top N…", "trend over time…", "compare X to Y…" — and schema-discovery questions like "what's in my semantic model", "what can I query", "list cubes/datasets/fields", "describe a cube" — or when explicitly asked to "query the semantic model", "run a cube query", "show me a chart", "plot…", "graph…". Use this whenever you would otherwise call the RevOS api_read tool against the `cubes` resource directly — this skill is what turns its raw JSON into a rendered table, a chart when the shape fits, a safe choice of join path when a query spans multiple cubes, and a plain-English explanation, instead of a dumped tool result. This applies even when the question names a specific source system (HubSpot, Zammad, Exact Online, …) — answer aggregate/analytical questions from the semantic model, not a direct source connector.
Find and explore RevOS metrics — the measures of the org's semantic model, as the app's Metrics page lists them — through the RevOS MCP server: which metrics exist, what each one aggregates and how it's formatted, which tables, segments, and dashboard cards use it, and what its value is right now, counted over a segment or a few conditions and optionally broken down by a dimension. Use this whenever the user asks "what metrics do we have", "is there a metric for win rate / ARR / open pipeline", "where is this metric used", "what's open pipeline for the EMEA segment", "deal amount by stage", or wants a metric's value the same way a dashboard card would show it — even if they never say "metric". For putting a metric on a dashboard, use the dashboards skill; it builds on this one.