code-engine-create

Create Code Engine packages and publish initial payloads via CLI workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code Engine package creation and versioning workflows can be error-prone and manual. This skill automates CLI-based package creation, first-payload publication, and manifest synchronization, reducing friction in code deployment.

Core Features & Use Cases

  • Create new package shells for Code Engine
  • Publish the initial package payload content
  • Infer and normalize function inputs/outputs and update the manifest's packagesMapping after create
  • Use case: when an agent must prepare a versioned container rather than invoking an existing function from app runtime

Quick Start

Use community-domo-cli to create a new Code Engine package and publish its first version with a sample payload.

Frequently Asked Questions about code-engine-create

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

FAQPage Schema
How do I create a Code Engine package and publish its first version from a CLI workflow?

To create a Code Engine package from a CLI workflow, you need to generate a package shell and publish the initial payload content using a deterministic payload contract. This process enforces the required payload shape and applies automatic datatype mapping for the new versioned container.

When should I create a new versioned Code Engine container instead of invoking an existing function?

You need to create a new versioned Code Engine container when your workflow requires a fresh package deployment rather than calling an existing function from app runtime. This is necessary for initial package creation and first payload publication.

How does manifest synchronization work after creating a Code Engine package?

Manifest synchronization updates the packagesMapping after package creation by inferring and normalizing function inputs and outputs. This post-create step ensures the manifest reflects the newly created package and its deterministic payload contract.

What is the best way to automate Code Engine package creation and reduce deployment friction?

Automating Code Engine package creation through CLI workflows enforces deterministic payload contracts and automatic datatype mapping. This approach handles package shell creation, first-payload publication, and manifest synchronization to reduce manual errors.

Does Code Engine package creation enforce specific payload shapes and datatype mapping?

Yes, Code Engine package creation enforces a required payload shape and applies automatic datatype mapping during the CLI workflow. This ensures deterministic payload contracts are maintained when creating packages and publishing initial versions.

Why do my Code Engine manifest updates fail to reflect newly created packages?

Manifest updates fail when post-create synchronization is missing from the CLI workflow. Properly inferring and normalizing function inputs and outputs updates the packagesMapping, ensuring the manifest accurately reflects the new versioned container.