← ClaudeAtlas

lucidalisted

Generating and editing images and video with Lucida — choosing a provider, iterating on a render, and the outcomes that differ from what was asked for. Use when creating image or video assets through the lucida MCP server or CLI, or when a render came back wrong and the next attempt needs to be different rather than repeated.
Artificial-Humanity/Lucida · ★ 0 · AI & Automation · score 72
Install: claude install-skill Artificial-Humanity/Lucida
# Lucida Lucida generates and edits images, and generates video, as an MCP server (`generate_image`, `image_providers`, `start_video`, `check_video`, `video_providers`, `list_operations`) or a CLI (`lucida generate|edit|video|check|ops|history|models|config`). Both images and video have a choice of provider, and `--provider`/`provider` selects one in either case. **This file deliberately contains no capability facts.** Which provider takes a seed, a mask, a negative prompt, a quality tier or a given aspect ratio changes as providers ship and Lucida adds them — so those live in one place that is always current: - MCP: call `image_providers`, or `video_providers` for the video lanes. - CLI: run `lucida models --provider <name>` — it answers for both kinds. Anything here that contradicts those is out of date; believe the probe. ## The one rule that changes how you work **Nothing is silently dropped.** A parameter the chosen provider cannot honour comes back as an error naming a provider that *can*, not a render that quietly ignored you. This is unusual and it is worth relying on: - Do not defensively strip parameters you are unsure about. Ask for what you want; if it cannot be honoured you get told, before anything is spent. - Do not treat such an error as failure. It is a routing hint — the message names the provider to switch to. - Do not pre-filter by consulting a table you remember. Let the call fail and read the answer, or probe first if you are about to spend