← CubeCONTENT HISTORY
WHAT CHANGED
Update to Cube
Snapshot Nov 4, 2026 · 00:11 UTC · version 1.1.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Cube and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Edit a Cube semantic model on a development branch and verify the result with Cube MCP tools. Use for requests to add or change a measure, dimension, view, cube, join, or pre-aggregation.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 185
}
],
"name": "cube-build-model",
"skill_md_contents": "---\nname: cube-build-model\ndescription: Edit a Cube semantic model on a development branch and verify the result with Cube MCP tools. Use for requests to add or change a measure, dimension, view, cube, join, or pre-aggregation.\nlicense: Apache-2.0\n---\n\n# Edit the Cube semantic model\n\nUse the Cube MCP server. Identify the deployment and read the compiled model plus the relevant source files before editing. Preserve the project's naming and file conventions. If a requested business definition is ambiguous, ask before encoding it in SQL.\n\n1. Start an isolated edit with `startDataModelEdit`; retain the returned `branchName` for every subsequent call. If the user named a branch, pass it explicitly when the tool supports it.\n2. Read files with `listDataModelFiles` and `readDataModelFile`. `writeDataModelFile` replaces a whole file, so send the complete revised content. Resolve validation errors before proceeding.\n3. Review the change with `getDataModelChanges` or `getBranchDiff`. Search and query the modified model with the same `branchName` to verify that the member is exposed and returns the intended result.\n4. Report the development branch, diff, validation result, and query check. The published Cube plugin does not currently expose a commit or merge tool, so explain that the user must finish review and commit in Cube.\n\nA successful compile does not establish that the metric is correct; report the actual query check. For a pre-aggregation, inspect `getPreAggregationStatus` before `buildPreAggregation`, which runs warehouse work.\n"
}SHA-256 of public snapshot: a67a99e3fd0304379b9b52f1271e0942d776152608c7ee3c137f18beccb01f12