data-api

Route Domo dataset reads through the dataset-query module.

19|13|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/stahura/domo-ai-vibe-rules --skill data-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-api
Source: https://github.com/stahura/domo-ai-vibe-rules/tree/main/skills/custom-apps/data-api
Command: npx skills add https://github.com/stahura/domo-ai-vibe-rules --skill data-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline Domo data access by providing a high-level entry point that routes detailed query work to the dataset-query module, reducing boilerplate and coupling.

Core Features & Use Cases

  • High-level data access surface for Domo datasets that delegates to dataset-query for reads.
  • Toolkit-first integration across apps to standardize dataset querying and improve consistency.
  • Example: Use the data-api skill to fetch aggregated metrics from a dataset via the dataset-query backend.

Quick Start

Create a simple data access flow by invoking the data-api to route a dataset read through dataset-query.

Frequently Asked Questions about data-api

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

FAQPage Schema
How do I access Domo datasets without writing direct SQL queries?

You can access Domo datasets through a high-level data-api surface that routes reads to the dataset-query module, encouraging structured, query-first workflows over direct SQL to reduce boilerplate and standardize data retrieval across apps.

What is the best way to standardize Domo dataset querying across multiple apps?

Use a toolkit-first data access surface to standardize Domo dataset querying across apps. It delegates reads to a dedicated dataset-query backend, ensuring consistency and reliability while reducing boilerplate code and coupling in your integration workflows.

Do I need manifest wiring to fetch aggregated metrics from a Domo dataset?

Fetching aggregated metrics requires manifest wiring via datasetsMapping. You must also define a name and description in SKILL.md to properly configure the data-api surface before routing reads through the dataset-query backend.

Why does the data-api route query work to a separate dataset-query module?

Routing query work to the dataset-query module provides a high-level entry point that reduces boilerplate and coupling. This delegation ensures consistent and reliable toolkit-first data access across your applications.

Can I use direct SQL for Domo dataset reads instead of a query-first approach?

While direct SQL may be possible, the data-api surface mandates structured, query-first access by delegating reads to the dataset-query module. This approach ensures consistency and reliability across toolkit-first data access workflows.

What are the limitations of using a high-level data access surface for Domo datasets?

The high-level data-api surface requires manifest wiring via datasetsMapping and a name and description in SKILL.md, adding configuration overhead while delegating detailed query execution to the dataset-query module rather than allowing direct SQL.