domains / families / media / atlas-cloud-media

atlas-cloud-media

combined

Discover Atlas Cloud image and video models, inspect their live schemas, and submit one confirmed media generation request with bounded GET polling. Use when integrating Atlas Cloud media APIs or generating images and videos without hard-coding stale model parameters. Generate Atlas Cloud images and videos through its asynchronous media API with schema-first model selection and credential-safe polling.

When to use

• The user wants to find an available Atlas Cloud image or video model.
• An integration needs the current model ID, input fields, endpoint, or price.
• The user wants one explicitly confirmed media generation request.
• An asynchronous Atlas Cloud task needs bounded status polling.
• Use when the user explicitly asks to generate an image or video with Atlas
• Use when an existing workflow needs an Atlas Cloud image or video generation
• Use when model-specific parameters must be discovered before submission.
• Do not use this skill for OpenAI-compatible text chat; that API has a

When not to use

• This source-only skill provides operational instructions, not an installed
• Available models, schemas, prices, and output retention can change; the live
• Model availability does not guarantee a prompt or reference asset is allowed.
• Generation is asynchronous and may take several minutes.
• Basic file checks do not replace human review of media quality, factual

Skill page

Conflict

The two skills describe the same high-level workflow (discover models, inspect schema, submit one paid request, poll with bounds) but implement it via fundamentally different mechanisms. The first skill relies on a bundled Python CLI (`scripts/atlas_media.py`) that abstracts away the HTTP details, while the second skill is a 'source-only' skill that provides raw `curl` and `jq` commands for direct API interaction. The second skill also introduces specific operational constraints (private per-run workspace with `umask 077`, specific polling intervals of 3s/200 attempts, explicit API endpoint table) that are absent from the first. Conversely, the first skill provides a specific CLI interface and safety rules regarding the `--confirm-paid` flag. Combining them is necessary to capture both the high-level CLI abstraction and the low-level manual API contract details.