publish

Automate Domo app build, packaging, and publishing with dist artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build and publish Domo apps end-to-end with automated dist packaging, first-publish ID handling, and validation checks to prevent failed deployments.

Core Features & Use Cases

  • End-to-end app build and publish workflow with dist output
  • First-publish ID management ensures updates overwrite the existing app rather than creating duplicates
  • Validation and remediation steps for manifest, thumbnail, and dataset configuration to prevent failed publishes

Quick Start

Install dependencies, build the project for production, authenticate with Domo, and publish from the dist folder.

Frequently Asked Questions about publish

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

FAQPage Schema
How do I automate building and publishing Domo apps from the command line?

You can automate Domo app deployment by building production artifacts into a dist folder and using the Domo CLI to authenticate and publish. This workflow handles packaging end-to-end to prevent failed releases.

Why does publishing my Domo app create a duplicate instead of overwriting the existing version?

Publishing creates duplicates when first-publish ID management is missing. Automated deployment workflows handle ID matching to ensure updates overwrite the existing app rather than creating new entries.

What prerequisites do I need to publish Domo apps locally?

Publishing Domo apps locally requires Node.js, npm, and the Domo CLI installed for authentication and publishing. You also need a prepared dist folder containing your app's production artifacts.

How do I validate my Domo app manifest and thumbnail before publishing?

Validating a Domo app before publishing involves checking the manifest, thumbnail, and dataset configuration. Automated deployment workflows include validation and remediation steps to prevent failed deployments.

What's the best way to manage dist artifacts for reliable Domo app deployment?

Managing dist artifacts for Domo deployment requires building the project for production, validating configurations, and publishing from the dist folder. Automating this workflow ensures reliable end-to-end releases.