
omni-content-explorer
★ 23by exploreomni · part of exploreomni/omni-agent-skills
Find, browse, and organize content in Omni Analytics — dashboards, workbooks, folders, and labels — using the Omni CLI. Use this skill whenever someone wants…
This is the playbook your agent receives when the skill activates — you don't need to read it to use the skill, but it's here to audit before installing.
by exploreomni
Find, browse, and organize content in Omni Analytics — dashboards, workbooks, folders, and labels — using the Omni CLI. Use this skill whenever someone wants…
npx skills add https://github.com/exploreomni/omni-agent-skills --skill omni-content-explorer
Download ZIPGitHub23
Omni Content Explorer
Find, browse, and organize Omni content — dashboards, workbooks, and folders — through the Omni CLI.
Discovering Commands
omni content --help # Content operations
omni documents --help # Document operations
omni folders --help # Folder operations
Tip: Use -o json to force structured output for programmatic parsing, or -o human for readable tables. The default is auto (human in a TTY, JSON when piped).
Browsing Content
List All Content
omni content list
With Counts and Labels
omni content list --include '_count,labels'
Filter and Sort
# 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
Pagination
Responses include pageInfo with cursor-based pagination. Fetch next page:
omni content list --cursor
Working with Documents
List Documents
omni documents list
# Filter by creator
omni documents list --creatorid
Each document includes: identifier, name, type, scope, owner, folder, labels, updatedAt, hasDashboard.
Important: Always use the identifier field for API calls, not id. The id field is null for workbook-type documents and will cause silent failures.
Get Document Queries
Retrieve query definitions powering a dashboard's tiles:
omni documents get-queries
Useful for understanding what a dashboard computes and re-running queries via omni-query.
Folders
# List
omni folders list
# Create
omni folders create "Q1 Reports" --scope organization
Labels
# 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
# Remove label
omni documents remove-label
Favorites
# Favorite
omni documents add-favorite
# Unfavorite
omni documents remove-favorite
Dashboard Downloads
# Start download (async)
omni dashboards download --body '{ "format": "pdf" }'
# Poll job status only after the start command returns a job ID
omni dashboards download-status
Formats: pdf, png
URL Patterns
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.
Search Patterns
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.
Docs Reference
Related Skills
-
omni-query — run queries behind dashboards you've found
-
omni-content-builder — create or update dashboards
-
omni-embed — embed dashboards you've found in external apps
-
omni-admin — manage permissions on documents and folders
npx skills add https://github.com/exploreomni/omni-agent-skills --skill omni-content-explorerRun this in your project — your agent picks the skill up automatically.
Prerequisites
# 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
# Confirm the active profile is authenticated and inspect your permissions:
omni whoami whoami
Auth: a profile authenticates with an API key or OAuth. If whoami (or any call) returns 401, hand off — ask the user to run ! omni config login <profile> (OAuth 2.1 browser flow; it blocks ~2 min on the browser). Don't run config login yourself in a headless/CI session (no browser → timeout); on a local interactive machine you may . See the omni-api-conventions rule for profile setup (omni config init --auth oauth) and discovering request-body shapes with --schema.
Known Issues & Safe Defaults
-
omni content listdoes not currently support a--labelsfilter. To find documents by label, useomni documents list --include labels -o json, paginate with--cursor, then filter records whoselabelsarray contains the target label. -
Some dashboard exports can fail before a job is created, for example with
Cannot use 'in' operator to search for 'query_id' in .... Ifomni dashboards downloadreturns an error and no job ID, do not calldownload-statusor claim the export completed. Report the dashboard identifier, the exact API error, and that no downloadable job was created.