skills.rest
noiz354
noiz354COMMUNITY
Explore all skills by this author →
WebsiteGitHub

omni-content-builder

Create and manage Omni Analytics documents and dashboards programmatically via the Omni CLI.

Updated Aug 7, 2026
Search Tags:#data visualization#cli#dashboard#business intelligence#omni analytics#documents api#workbook model
One-click install
npx skills add https://github.com/noiz354/oc-rebirth-rca --skill omni-content-builder-noiz354
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omni-content-builder
Source: https://github.com/noiz354/oc-rebirth-rca/tree/main/planning-zip/omni-agent-skills/skills/omni-content-builder
Command: npx skills add https://github.com/noiz354/oc-rebirth-rca --skill omni-content-builder-noiz354

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building and updating Omni Analytics dashboards by hand through the UI is slow and hard to automate. This Skill lets you create, edit, and publish Omni documents and dashboards programmatically through the Omni CLI's v2 documents API, covering tiles, visualizations, filters, controls, and layouts through a safe draft-to-publish workflow. ## Core Features & Use Cases - Document Lifecycle Management: Create, rename, move, duplicate, delete, and publish Omni documents using the v2 draft flow so the published dashboard is never touched until validation passes. - Dashboard Authoring: Add tiles, charts, KPI views, markdown tiles, dashboard filters, interactive controls, and multi-page grid layouts via the queryPresentations, controls, and containers envelope slices. - Workbook Model Customization: Push dashboard-specific dimensions and measures to a document's workbook model with extension-mode YAML writes, including branch-bound drafts for fields not yet in the shared model. - Use Case: A user asks to build a Q1 revenue dashboard with a monthly trend line chart, a date-range filter, and a state dropdown. The Skill creates the document, authors the tile queries on a topic, wires the controls, lays out the containers tree, validates every query, and publishes the draft. ## Quick Start Ask the AI to build an Omni dashboard showing monthly revenue by state with a date filter, using the omni-content-builder skill.

Frequently Asked Questions about omni-content-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an Omni dashboard programmatically?▼

Use the Omni CLI's documents v2-create command with a JSON body containing queryPresentations, controls, containers, and settings. Tiles are keyed records with a query and visConfig, and edits go through a draft-to-publish flow so changes are validated before going live.

How do I update an existing Omni dashboard without breaking it?▼

Read the current state with documents v2-get, author a patch containing only the changed keys, apply it with v2-patch-draft, validate the draft by running its queries, then publish with v2-publish-draft. The published document stays untouched until the draft is published.

Why does my Omni dashboard tile show No chart available?▼

This usually happens when a tile's inner vis config was round-tripped from a v2-get response, which returns the config flat, while patches only persist it nested under config. Re-author the visConfig with the spec nested under visConfig.visConfig.config and verify by reading the tile back.

Can I add custom fields to a single Omni dashboard?▼

Yes, write dimensions or measures to the document's workbook model using omni models yaml-create with mode set to extension. Get the workbook model ID fresh from documents list-drafts, since it rotates on every draft-to-publish cycle.

Why is only one tile showing after creating a multi-tile dashboard?▼

A multi-tile v2-create only auto-lays-out the first tile; the rest are stored but render nowhere. You must author the full containers layout tree yourself, with a tile stack referencing each tile's key via metadata.attachedQueryKey.

What are the limitations of the Omni v2 documents API?▼

Classic-layout dashboards return 422 from every v2 endpoint and must be upgraded in the Omni UI first. Branch-bound drafts cannot be published or discarded via the CLI, and document operations like list, delete, move, and duplicate have no v2 form.

Related Skills

Explore More Data & Analytics Skills→
exploreomniexploreomni
30

omni-model-explorer

Discover Omni semantic models, topics, and views via the Omni CLI.

Official
Intermediate
api-evangelistapi-evangelist

sharing

Manage sharing permissions for tables, workflows, and agents via the Frontline CLI.

Official
Intermediate
exploreomniexploreomni
30

omni-content-builder

Create and manage Omni Analytics dashboards and documents via the Omni CLI.

Official
Advanced
syncfusionsyncfusion
4

syncfusion-blazor-query-builder

Create rule-based data filtering UIs for Blazor applications.

Official
Advanced