From omni-analytics
Browse, search, and organize Omni Analytics dashboards, workbooks, and folders via the Omni CLI. Supports downloading dashboards as PDF/PNG, managing labels, and paginated listing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/omni-analytics:omni-content-explorerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Find, browse, and organize Omni content — dashboards, workbooks, and folders — through the Omni CLI.
Find, browse, and organize Omni content — dashboards, workbooks, and folders — through the Omni CLI.
# Verify the Omni CLI is installed — if not, ask the user to install it
# See: https://github.com/exploreomni/cli#readme
command -v omni >/dev/null || echo "ERROR: Omni CLI is not installed."
# Show available profiles and select the appropriate one
omni config show
# If multiple profiles exist, ask the user which to use, then switch:
omni config use <profile-name>
omni content --help # Content operations
omni documents --help # Document operations
omni folders --help # Folder operations
Tip: Use
-o jsonto force structured output for programmatic parsing, or-o humanfor readable tables. The default isauto(human in a TTY, JSON when piped).
omni content list does not currently support a --labels filter. To find documents by label, use omni documents list --include labels -o json, paginate with --cursor, then filter records whose labels array contains the target label.Cannot use 'in' operator to search for 'query_id' in .... If omni dashboards download returns an error and no job ID, do not call download-status or claim the export completed. Report the dashboard identifier, the exact API error, and that no downloadable job was created.omni content list
omni content list --include '_count,labels'
# By label: list documents with labels, then filter the JSON results client-side.
# Paginate with --cursor until pageInfo.hasNextPage is false.
omni documents list --include labels -o json
# By scope
omni content list --scope organization
# Sort by popularity or recency
omni content list --sortfield favorites
omni content list --sortfield updatedAt
Responses include pageInfo with cursor-based pagination. Fetch next page:
omni content list --cursor <nextCursor>
omni documents list
# Filter by creator
omni documents list --creatorid <userId>
Each document includes: identifier, name, type, scope, owner, folder, labels, updatedAt, hasDashboard.
Important: Always use the
identifierfield for API calls, notid. Theidfield is null for workbook-type documents and will cause silent failures.
Retrieve query definitions powering a dashboard's tiles:
omni documents get-queries <identifier>
Useful for understanding what a dashboard computes and re-running queries via omni-query.
# List
omni folders list
# Create
omni folders create "Q1 Reports" --scope organization
# List labels
omni labels list
# Find documents with a label
omni documents list --include labels -o json
# Add label to document
omni documents add-label <identifier> <labelName>
# Remove label
omni documents remove-label <identifier> <labelName>
# Favorite
omni documents add-favorite <identifier>
# Unfavorite
omni documents remove-favorite <identifier>
# Start download (async)
omni dashboards download <identifier> --body '{ "format": "pdf" }'
# Poll job status only after the start command returns a job ID
omni dashboards download-status <identifier> <jobId>
Formats: pdf, png
Construct direct links to content:
Dashboard: {OMNI_BASE_URL}/dashboards/{identifier}
Workbook: {OMNI_BASE_URL}/w/{identifier}
The identifier comes from the document's identifier field in API responses. Always provide the user a clickable link after finding content.
When scanning all documents for field references (e.g., for impact analysis), paginate with cursor and call omni documents get-queries <identifier> for each document. Launch multiple query-fetch calls in parallel for efficiency. For field impact analysis, prefer the content-validator approach in omni-model-explorer.
npx claudepluginhub exploreomni/omni-agent-skills --plugin omni-integrationsCreate, update, and manage Omni Analytics documents and dashboards programmatically via the Omni CLI — drafts, tiles, visualizations, filters, controls, and layouts.
Review existing analytics — find all dashboards and reports, check who uses them, whether metrics are defined, and whether they drive decisions. Recommend what to keep, kill, or add. Use when asked "are our dashboards useful", "analytics review", or "metrics audit".