Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/ideogram-data-handling

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/ideogram-data-handling

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈78 tokens for metadata: the name and description. ≈998 when used: this file. ≈623 more on demand in 1 file.

Description uses 3.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈312 characters, or 3.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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 json_prompt; its bounding boxes use normalized [0,1000] coordinates in [y_min,x_min,y_max,x_max] 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 IDEOGRAM_API_KEY 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. Test deletion across primary storage, metadata, queue, cache, backup policy, and custom-training records.

Tool Discipline

Use Read, Glob, and Grep to inspect schemas, stores, policies, and fixtures. Use Write and Edit for approved lifecycle controls or documentation. Do not open, copy, upload, publish, or delete customer media without authority.

Approval Boundaries

Require data-owner approval for sensitive inputs, training, new purposes, longer retention, external publication, cross-region movement, backup exceptions, and destructive deletion. Rights uncertainty is a stop condition.

Error Handling

  • Never treat an expiring URL as durable storage or an authorization token.
  • Quarantine tenant-mismatched, malformed, oversized, or unexpectedly content-bearing records.
  • Preserve legal holds while reporting why normal deletion could not complete.

Output

Return the data map, classifications, rights and purpose decisions, stores, access paths, retention and deletion controls, tests, gaps, owners, and rollback. Exclude actual prompts, images, URLs, or credentials.

Examples

  • Retain an opaque generation ID and safety result for audit while deleting the source upload and vendor URL metadata.
  • Govern a training dataset, captions, trained-model reference, and derived outputs as linked but separately deletable records.

Validation

Trace one synthetic record through every system, verify least privilege and content-free telemetry, execute deletion, and confirm all governed locations. Reconcile any retained backup or legal-hold exception.

Resources

  • Current first-party evidence map — use the dated endpoint, webhook, billing, team, and training links as the contract index for this workflow.
  • Recheck the endpoint-specific page and current OpenAPI description before relying on an enum, limit, beta feature, or lifecycle claim.
  • Record live observations as environment-specific evidence, not as universal vendor guarantees.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides instructions for governing Ideogram data lifecycles, focusing on privacy, retention, and security best practices. It references official Ideogram documentation and does not contain any malicious code, obfuscation, or data exfiltration patterns.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Edits files
Modelinherit
argument-hint
<data-class> <use-case> <retention-policy>
version
1.11.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "ideogram",
  "data-governance"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; customer-derived media requires explicit authority

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/ideogram-data-handling