Agent skill · software engineering · jeremylongshore
ideogram-multi-env-setup
Isolate Ideogram development, staging, and production across keys, budgets, webhook routes, storage, data, and promotion evidence. Use when designing or auditing environment separation. Trigger with "separate Ideogram environments", "configure Ideogram staging", or "audit Ideogram promotion".
Why this skill is useful
Adds a comprehensive multi-environment setup script for Ideogram that includes configuration management and secret handling not found in public documentation.
What it needs
Requires aws, gcloud installed locally. Requires github account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Ideogram Environment Isolation Overview Prevent development and staging activity from consuming production authority or contaminating production media. Separate keys, application identities, budgets, routes, queues, state, storage, telemetry, and cleanup while recognizing that keys in the same Ideogram team share credits. Prerequisites Environment inventory, Ideogram team model, billing owner, and promotion owner. Secret, queue, webhook, storage, observability, data, and retention maps. A synthetic test-data policy and production-access exception process. Current Contract Ideogram supports multiple revocable keys, but keys within one team share credit and billing. Team roles are Owner, Admin, and Member. Environment separation therefore needs application-owned budgets and controls even when separate vendor keys use one shared team. Authentication Create distinct secret references per environment and inject each server-side as Api-Key to https://api.ideogram.ai. Never copy a production key into developer machines, pull-request jobs, staging configuration, or shared examples. Instructions 1. Inventory each environment's key reference, team, role owner, budget, route, queue, webhook URL, storage prefix, telemetry, and data class. 2. Assign distinct keys where supported and document the shared-credit boundary of any common Ideogram team. 3. Enforce application-side environment and tenant budgets, concurrency, and destination allowlists. 4. Use environment-specific webhook hosts and bind every delivery to a known generation, tenant, and environment. 5. Isolate object stores or prefixes, signing keys, retention jobs, and publication targets. 6. Promote immutable code and schema evidence, not prompts, images, URLs, credentials, or in-flight state. 7. Test wrong-key, wrong-webhook, wrong-bucket, and cross-environment access denial plus independent rollback. Tool Discipline Use Read, Glob, and Grep to inspect configuration and infrastructure. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ideogram-multi-env-setup