// Update Domo Code Engine packages through CLI-driven versioned lifecycle workflows with compatibility checks, datatype contract safeguards, and manifest mapping drift synchronization. Use when an agent must update package code or create a new package version and keep app mappings aligned.
Step-by-step orchestrator for building Domo App Studio apps with native KPI cards via community-domo-cli. Sequences app creation, pages, theme, hero metrics, native charts, filter cards, layout assembly, and navigation. CLI-first — no raw API calls.
Domo KPI card CRUD via community-domo-cli — body schema, column mapping, beast modes, chart type index with on-demand reference files, and gotchas.
**Generating sample data for Domo** -- invoke when a user needs to create realistic sample datasets and upload them to a Domo instance. Primary signals: requests for sample data, demo data, test data, fake data for Domo; mentions of Salesforce, Google Analytics, QuickBooks, NetSuite, Google Ads, Facebook Ads, HubSpot, Marketo, or Health Portal sample data; questions about the datagen CLI or domo_data_generator. Covers: generating datasets, uploading to Domo, creating datasets in Domo, rolling dates, entity pools, connector icons, catalog management, and adding new dataset definitions. Skip for: real connector setup, production data pipelines, data transformations (Magic ETL), or Domo App Platform.
Create AppDB collections via CLI-first workflows where collection creation also provisions the required datastore, then returns collection identifiers for manifest wiring and document-write follow-up. Use when an agent must initialize new AppDB storage for a Domo app, not just list/get collections or create documents.
Create Domo Code Engine packages from CLI workflows with deterministic payload contracts, automatic function parameter datatype mapping, and manifest packagesMapping follow-up guidance. Use when an agent must create a new package/versioned package container rather than only invoke an existing function from app runtime code.
General instructions for using the community-domo-cli in this repository, including install/auth setup, endpoint testing, and troubleshooting.
| name | code-engine-update |
| description | Update Domo Code Engine packages through CLI-driven versioned lifecycle workflows with compatibility checks, datatype contract safeguards, and manifest mapping drift synchronization. Use when an agent must update package code or create a new package version and keep app mappings aligned. |
Use this skill for package update/version workflows and safe contract evolution.
This skill covers:
For app-runtime invocation code, use ~/.agents/skills/code-engine/SKILL.md.
Prefer community-domo-cli:
community-domo-cli --instance <instance> code-engine update-version <package_id> <version> --body-file payload.json
Fallback endpoint pattern:
POST /api/codeengine/v2/packages
with id and version set in body for versioned update behavior.
Hard rule: never call any Code Engine release endpoint unless the user explicitly says "release".
Preferred create/update model:
POST /api/codeengine/v2/packagesPOST /api/codeengine/v2/packages with id and version (for example 1.0.1) in the request body, including code/manifest payload.PUT /api/codeengine/v2/packages/{id}/versions/{version}Execution notes:
PUT for subsequent changes to that specific version.Always emit resulting packageId and version for downstream manifest sync.
Before update publish:
When breaking change is intentional, require explicit migration note in generated output.
After update:
manifest.json packagesMapping against returned package id/versionpackageId, version, and parameter/output contracts when drift detectedpackagesMapping drift checked and synchronized