Loading...
Loading...
Found 23 Skills
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.
Manages Power BI semantic models, including tables, columns, measures, relationships, field parameters, DAX, Import, DirectQuery and Direct Lake designs, sources, connections, permissions, refresh, and deployment. Load this skill before acting on a semantic model, unless it is part of publishing a PBIP project, which powerbi-report-cli owns. For natural-language data questions use fabriciq; for visuals use powerbi-report-cli.
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.
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.
Plan, design, author, preview, publish, and manage Power BI reports across requirements, page design, local PBIR/PBIP edits, validation, screenshots, Fabric upload/download, and rebinding. Use for report lifecycle work; use semantic-model-authoring for model or DAX changes and fabriciq for data questions. Triggers: plan Power BI report, design report page, edit PBIR, preview PBIP, publish report, rebind report
Use when creating or modifying dbt Semantic Layer components including semantic models, metrics, and dimensions leveraging MetricFlow.
Use Fabric CLI for Power BI operations — semantic models, reports, DAX queries, refresh, gateways. Activate when users work with Power BI items, need to refresh datasets, execute DAX, manage reports, or troubleshoot refresh failures.
Create and edit Omni Analytics semantic model definitions — views, topics, dimensions, measures, relationships, and query views — using YAML through the Omni CLI. Use this skill whenever someone wants to add a field, create a new dimension or measure, define a topic, set up joins between tables, modify the data model, build a new view, add a calculated field, create a relationship, edit YAML, work on a branch, promote model changes, or any variant of "model this data", "add this metric", "create a view for", or "set up a join between". Also use for migrating modeling patterns since Omni's YAML is conceptually similar to other semantic layer definitions.
Discover and inspect Omni Analytics models, topics, views, fields, dimensions, measures, and relationships using the Omni CLI. Use this skill whenever someone wants to understand what data is available in Omni, explore their semantic model, find specific fields or views, check how tables join together, see what topics exist, or asks any variant of "what can I query", "what fields are available", "show me the model", "what data do we have", or "how is this data modeled". Also use when you need to understand the Omni model structure before building or modifying anything.
Search and inspect a Cube semantic model — cubes, views, measures, dimensions, joins, and the files they live in — using the Cube CLI. Use whenever someone wants to know what data is available in Cube, where a metric is defined, which cube a field belongs to, how two cubes join, or what a change would affect. Triggers on "what can I query", "what measures do we have", "where is revenue defined", "show me the data model", "what's in this deployment", "which cube has customer email", and impact questions like "what breaks if I rename this". Read the model with this skill before changing it. To edit the model use cube-build-model; to run a query and get numbers back use cube-run-query; to browse workbooks, dashboards and reports use cube-explore-content.
Salesforce Data 360 reports, dashboards, report types, reportability of DMOs and calculated insights, dashboard limits, consumption insights, and semantic model analytics. TRIGGER when: the user creates, reviews, packages, or debugs Data 360 reports, dashboards, report types, KPI dashboards, or analytics built on DMOs, CIOs, or semantic models.
Author and change a Cube semantic model — add or edit cubes, views, measures, dimensions, joins and pre-aggregations in YAML — using the Cube CLI, on a dev-mode branch, then commit and build. Use whenever someone wants to add a metric, define a measure or dimension, create a cube or view, join two cubes, fix a model error, rename a field, or expose a field to business users. Triggers on "add a metric", "define revenue", "create a view for", "expose this field", "join orders to customers", "fix the model", "add a pre-aggregation". Read the model first with cube-explore-model. To run a query against the result use cube-run-query; to deploy or check build status use cube-deploy.