Loading...
Loading...
Found 4 Skills
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.
Standards and best practices for writing LookML tests to ensure data integrity, accuracy, and logic validation.
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.
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.