[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASR6TH7HA1PQ7Z3DXPZ2B1":3,"skill-same:01M7ASR6TH7HA1PQ7Z3DXPZ2B1":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ASR6TH7HA1PQ7Z3DXPZ2B1","cube-embed",null,"Set up and debug Cube embedded analytics — embed sessions, embed tokens, embeddable dashboards and embed tenants — using the Cube CLI. Use whenever someone is shipping Cube analytics inside their own product: mint a session for an end user, enable a dashboard for embedding, set up multi-tenant isolation so each customer sees only their data, or debug why an embedded view is empty or unauthorized. Triggers on \"embed this dashboard\", \"embedded analytics\", \"our customers need to see\", \"multi-tenant analytics\", \"the iframe is blank\", \"embed token\", \"sign the embed URL\", \"customer-facing dashboard\". For internal access control use cube-admin; for the dashboards themselves use cube-build-content.","cube-js\u002Fcube-agent-skills","cube-js","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F52467369?v=4","01M7ASPXD7T6SBZM632VQRFBJM","Cube","01M7ASPXDVXSVY911K7DAMGEWQ",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcube-js\u002Fcube-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcube-embed\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cube-embed\ndescription: >-\n  Set up and debug Cube embedded analytics — embed sessions, embed tokens, embeddable dashboards and embed tenants — using the Cube CLI. Use whenever someone is shipping Cube analytics inside their own product: mint a session for an end user, enable a dashboard for embedding, set up multi-tenant isolation so each customer sees only their data, or debug why an embedded view is empty or unauthorized. Triggers on \"embed this dashboard\", \"embedded analytics\", \"our customers need to see\", \"multi-tenant analytics\", \"the iframe is blank\", \"embed token\", \"sign the embed URL\", \"customer-facing dashboard\". For internal access control use cube-admin; for the dashboards themselves use cube-build-content.\nlicense: Apache-2.0\ncompatibility: Needs the Cube CLI, installed and logged in, and network access to Cube Cloud.\n---\n\n# Embed Cube in your product\n\nEmbedding is where analytics leaves your team and reaches your customers, so\nthe isolation model matters more than the mechanics. Most of the work is\ngetting the security context right; the CLI part is short.\n\nCLI-only. The Cube MCP tools do not mint embed sessions or configure\nembedding. Without a terminal and the Cube CLI, explain the model below and\nsay which commands the user needs to run.\n\n## Preflight\n\n```bash\ncommand -v cube >\u002Fdev\u002Fnull || echo \"Cube CLI not installed: curl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fcube-js\u002Fcube\u002Fmaster\u002Finstall-cli.sh | sh\"\ncube whoami || echo \"Not authenticated. Interactive: cube login. Headless: set CUBE_API_URL + CUBE_API_KEY.\"\ncube context list\n```\n\n## The model, before the commands\n\nFour things, and conflating them is the usual source of confusion:\n\n- **Embed tenant** — one of your customers. The isolation boundary.\n- **Embed user** — an end user inside one of those customers.\n- **Embed session \u002F token** — short-lived credentials carrying that user's\n  security context. This is what makes row-level security apply.\n- **Embeddable dashboard** — a dashboard explicitly enabled for embedding.\n  Dashboards are not embeddable by default.\n\nThe security context in the token is what the model's row-level security\nreads. **Isolation is a property of the token you mint, not of the dashboard\nyou embed.** A correct dashboard with a wrong token shows one customer\nanother customer's data — which is the failure mode worth being paranoid\nabout.\n\n## Commands\n\n```bash\ncube embed generate-session --data '\u003Csession>'\ncube embed token --session-id \u003Csession>\n\ncube embed enable-dashboard \u003Cpublic-id>\ncube embed dashboard \u003Cpublic-id>\ncube embed disable-dashboard \u003Cpublic-id>\n\ncube embed tenant groups \u003Ctenant>\ncube embed tenant delete \u003Ctenant>\ncube embed tenant delete-group \u003Ctenant> \u003Cgroup>\n```\n\nSessions and tokens are minted server-side. They must never be generated in\nbrowser code or checked into a repository — anyone holding one has that\nuser's access until it expires.\n\n## Setting up a new embedded dashboard\n\n1. Build and publish the dashboard (`cube-build-content`).\n2. Get the dashboard's public id, then run `cube embed enable-dashboard` —\n   until this runs, embedding it fails.\n3. Confirm the model has row-level security keyed on the attribute your\n   security context carries. Check with `cube-explore-model`; if it does not,\n   stop and fix the model first.\n4. Mint a session for a **test** embed user of one tenant.\n5. Verify that user sees only that tenant's rows. `cube deployments token`\n   carries *your* context, so it cannot test this. Mint a token for each of\n   two tenants' security contexts, query the same measure with each through\n   the `cube-run-query` endpoint, and confirm the numbers differ:\n\n   ```bash\n   cube environments create-token \u003Cdeployment> \u003Cenvironment> --security-context '{\"tenant_id\":\"\u003Ca>\"}'\n   ```\n\n   The token is a credential — use it, never print it.\n\nStep 5 is the one that catches broken isolation, and it is the one people\nskip because step 4 appeared to work.\n\n## Debugging an embedded view\n\n| Symptom | Where to look |\n| --- | --- |\n| Blank iframe, no error | Dashboard not enabled for embedding — run `cube embed dashboard` to check |\n| 401 \u002F 403 in the iframe | Token expired or minted for the wrong tenant |\n| Renders but no rows | Security context has no matching value — the token is valid but scoped to nothing |\n| Shows **too much** data | Row-level security is not applied. Stop and treat this as an incident, not a bug to iterate on |\n| Works for you, not customers | You are testing with an internal account that bypasses the tenant scope |\n\n## Conventions\n\n- Never print a full token in output. Say that one was minted and for which\n  user.\n- Always test with a real embed user, never an admin account. Admin accounts\n  see everything, which makes broken isolation invisible.\n- When something is wrong with isolation, say so directly and stop.\n","# Embed Cube in your product\n\nEmbedding is where analytics leaves your team and reaches your customers, so\nthe isolation model matters more than the mechanics. Most of the work is\ngetting the security context right; the CLI part is short.\n\nCLI-only. The Cube MCP tools do not mint embed sessions or configure\nembedding. Without a terminal and the Cube CLI, explain the model below and\nsay which commands the user needs to run.\n\n## Preflight\n\n```bash\ncommand -v cube >\u002Fdev\u002Fnull || echo \"Cube CLI not installed: curl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fcube-js\u002Fcube\u002Fmaster\u002Finstall-cli.sh | sh\"\ncube whoami || echo \"Not authenticated. Interactive: cube login. Headless: set CUBE_API_URL + CUBE_API_KEY.\"\ncube context list\n```\n\n## The model, before the commands\n\nFour things, and conflating them is the usual source of confusion:\n\n- **Embed tenant** — one of your customers. The isolation boundary.\n- **Embed user** — an end user inside one of those customers.\n- **Embed session \u002F token** — short-lived credentials carrying that user's\n  security context. This is what makes row-level security apply.\n- **Embeddable dashboard** — a dashboard explicitly enabled for embedding.\n  Dashboards are not embeddable by default.\n\nThe security context in the token is what the model's row-level security\nreads. **Isolation is a property of the token you mint, not of the dashboard\nyou embed.** A correct dashboard with a wrong token shows one customer\nanother customer's data — which is the failure mode worth being paranoid\nabout.\n\n## Commands\n\n```bash\ncube embed generate-session --data '\u003Csession>'\ncube embed token --session-id \u003Csession>\n\ncube embed enable-dashboard \u003Cpublic-id>\ncube embed dashboard \u003Cpublic-id>\ncube embed disable-dashboard \u003Cpublic-id>\n\ncube embed tenant groups \u003Ctenant>\ncube embed tenant delete \u003Ctenant>\ncube embed tenant delete-group \u003Ctenant> \u003Cgroup>\n```\n\nSessions and tokens are minted server-side. They must never be generated in\nbrowser code or checked into a repository — anyone holding one has that\nuser's access until it expires.\n\n## Setting up a new embedded dashboard\n\n1. Build and publish the dashboard (`cube-build-content`).\n2. Get the dashboard's public id, then run `cube embed enable-dashboard` —\n   until this runs, embedding it fails.\n3. Confirm the model has row-level security keyed on the attribute your\n   security context carries. Check with `cube-explore-model`; if it does not,\n   stop and fix the model first.\n4. Mint a session for a **test** embed user of one tenant.\n5. Verify that user sees only that tenant's rows. `cube deployments token`\n   carries *your* context, so it cannot test this. Mint a token for each of\n   two tenants' security contexts, query the same measure with each through\n   the `cube-run-query` endpoint, and confirm the numbers differ:\n\n   ```bash\n   cube environments create-token \u003Cdeployment> \u003Cenvironment> --security-context '{\"tenant_id\":\"\u003Ca>\"}'\n   ```\n\n   The token is a credential — use it, never print it.\n\nStep 5 is the one that catches broken isolation, and it is the one people\nskip because step 4 appeared to work.\n\n## Debugging an embedded view\n\n| Symptom | Where to look |\n| --- | --- |\n| Blank iframe, no error | Dashboard not enabled for embedding — run `cube embed dashboard` to check |\n| 401 \u002F 403 in the iframe | Token expired or minted for the wrong tenant |\n| Renders but no rows | Security context has no matching value — the token is valid but scoped to nothing |\n| Shows **too much** data | Row-level security is not applied. Stop and treat this as an incident, not a bug to iterate on |\n| Works for you, not customers | You are testing with an internal account that bypasses the tenant scope |\n\n## Conventions\n\n- Never print a full token in output. Say that one was minted and for which\n  user.\n- Always test with a real embed user, never an admin account. Admin accounts\n  see everything, which makes broken isolation invisible.\n- When something is wrong with isolation, say so directly and stop.\n",{"name":5,"license":15,"description":7,"compatibility":24},"Needs the Cube CLI, installed and logged in, and network access to Cube Cloud.","main","5e5ef13c40f3bfc101d575b568b5c5a3447d6fcb","skills\u002Fcube-embed",0,"https:\u002F\u002Fgithub.com\u002Fcube-js\u002Fcube-agent-skills","https:\u002F\u002Fgithub.com\u002Fcube-js","https:\u002F\u002Fcube.dev","The Semantic Layer for building data apps","2026-10-01 05:18:35",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add cube-js\u002Fcube-agent-skills --skill cube-embed",{"tool":40,"command":41},"bunx","bunx skills add cube-js\u002Fcube-agent-skills --skill cube-embed",{"tool":43,"command":44},"pnpm","pnpm dlx skills add cube-js\u002Fcube-agent-skills --skill cube-embed","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcube-js\u002Fcube-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcube-embed\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7ASRWS98EN8SQEFQFB7RKSA","cube-run-query","Run queries against a Cube deployment's semantic layer and interpret the results — through the Cube MCP tools when they are connected, or the Cube CLI from a 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.","https:\u002F\u002Fgithub.com\u002Fcube-js\u002Fcube-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcube-run-query\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7ASRMCKWK6CMRRTE8XJ9R4W","cube-explore-model","Search and inspect a Cube semantic model — cubes, views, measures, dimensions, joins, and the files they live in — through the Cube MCP tools or 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.","https:\u002F\u002Fgithub.com\u002Fcube-js\u002Fcube-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcube-explore-model\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7ASRDJTX19A2PT8JZ11TNQ4","cube-explore-content","Find and inspect saved content in a Cube workspace — workbooks, dashboards, reports, folders and scheduled notifications — using the Cube CLI, or the Cube MCP tools for content you already have a link to. Use whenever someone wants to know what already exists rather than build something new: locate a dashboard, list reports, see what a report queries, find who a notification goes to, or check what saved content references a model field before renaming it. Triggers on \"what dashboards do we have\", \"find the revenue report\", \"where is that workbook\", \"what's in this folder\", \"who gets this scheduled report\", \"is anything using this field\". To create or edit content use cube-build-content; to inspect the semantic model itself use cube-explore-model.","https:\u002F\u002Fgithub.com\u002Fcube-js\u002Fcube-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcube-explore-content\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7ASR0E40HQ3H7DXY9N795H2","cube-deploy","Manage Cube deployments and their lifecycle — create deployments, deploy a project, check build status, manage environments and environment variables, connect a GitHub repo, and tail logs — using the Cube CLI. Use whenever someone wants to ship, configure or debug a deployment rather than change the model inside one. Triggers on \"deploy this\", \"did the build pass\", \"why did the build fail\", \"set an environment variable\", \"create a deployment\", \"connect our repo\", \"show me the logs\", \"what regions are available\", \"the deployment is down\". To change model files use cube-build-model; for users and access use cube-admin.","https:\u002F\u002Fgithub.com\u002Fcube-js\u002Fcube-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcube-deploy\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7ASQS7SXDV63D81YJFQSDTY","cube-configure-agent","Inspect and tune Cube's in-product AI agent — its rules, certified queries and Agent Skills — by authoring markdown in the semantic model, through the Cube MCP tools or the Cube CLI. Use whenever someone wants the Cube agent to answer better: teach it a business definition, stop it making a recurring mistake, certify a trusted query, capture a repeatable workflow as a skill, or find out why it answered the way it did. Triggers on \"the agent keeps getting X wrong\", \"teach the agent that\", \"make the agent always\", \"add a certified query\", \"create an agent skill\", \"why did the agent say that\", \"what rules does the agent have\". To change the underlying model use cube-build-model; to explore what is queryable use cube-explore-model.","https:\u002F\u002Fgithub.com\u002Fcube-js\u002Fcube-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcube-configure-agent\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7ASQH58PKK3XQK05YA5532H","cube-build-model","Author and change a Cube semantic model — add or edit cubes, views, measures, dimensions, joins and pre-aggregations in YAML — on a dev-mode branch through the Cube MCP tools or the Cube CLI, 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.","https:\u002F\u002Fgithub.com\u002Fcube-js\u002Fcube-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcube-build-model\u002FSKILL.md",[],[]]