Agent skill · data analytics · jeremylongshore
ideogram-data-handling
Govern Ideogram prompts, uploads, structured descriptions, generated assets, temporary URLs, metadata, and training datasets through deletion. Use when designing privacy or retention controls. Trigger with "map Ideogram data", "set Ideogram retention", or "audit Ideogram image storage".
Why this skill is useful
Provides domain-specific commands and metadata management patterns for handling Ideogram image assets that the AI wouldn't reliably generate on its own.
What it needs
Requires node installed locally. Requires ideogram account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Ideogram Data Lifecycle Overview Map and enforce the lifecycle of every datum that crosses an Ideogram workflow. Distinguish prompts, JSON descriptions, source media, masks, generated outputs, temporary links, safety decisions, metadata, logs, and custom-training assets because each has different ownership and retention needs. Prerequisites Use case, data owner, tenant, classification, rights basis, region, retention, and deletion SLO. Architecture for upload, API, async state, webhook, polling, download, storage, review, publication, backup, and telemetry. Vendor terms and privacy review appropriate to the workload. Current Contract V4 describe can transform an uploaded image into a structured jsonprompt; its bounding boxes use normalized [0,1000] coordinates in [ymin,xmin,ymax,xmax] order. Output URLs expire. Custom training supports datasets of 10–100 images, optional captions or ZIP upload, model training, and model-status retrieval. Authentication Keep IDEOGRAMAPIKEY outside data stores and send it only as Api-Key from a trusted server. Application authorization must bind every input, generated object, dataset, and trained-model reference to its tenant and purpose. Instructions 1. Inventory each data class, source, purpose, rights basis, vendor transmission, destination, readers, retention, and deletion path. 2. Minimize prompts and metadata, validate image type and size, strip unnecessary metadata, and isolate temporary files. 3. Store async identifiers and safety decisions without copying content into queues, logs, traces, or incident evidence. 4. Download approved output promptly, validate it, store under an opaque tenant-scoped key, and discard the vendor URL. 5. Apply separate governance to describe output, captions, datasets, ZIPs, custom model references, backups, and derived assets. 6. Enforce access, encryption, publication review, lifecycle deletion, legal holds, and tenant export. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ideogram-data-handling--604bcd