structured-asset-pipeline

Generates multi-unit image and audio assets from YAML specs via contract-first backend adapters.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill structured-asset-pipeline-avatar-arts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: structured-asset-pipeline
Source: https://github.com/AvaTar-ArTs/.Agent-skills/tree/main/skills/creative/structured-asset-pipeline
Command: npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill structured-asset-pipeline-avatar-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve? Batch generation of images and audio often fails silently: files land in wrong directories, prompts are lost when context resets, and existing assets get overwritten. This Skill enforces a reproducible pipeline where every asset is specified on disk first, generated through a validated adapter, verified on the filesystem, and listed in a completion report. ## Core Features & Use Cases - Contract-first adapters: Six backend adapters (OpenAI Images, Replicate, fal.ai, ComfyUI, ElevenLabs, Suno unofficial) share one CLI contract with --spec, --out, --dry-run, JSON stdout results, and standardized exit codes. - Reproducible unit specs: Every generation unit is written as a YAML spec before any API call, enabling partial workflows like analyze-only, specs-only, generate-only, and regenerate-N with automatic timestamped backups. - Safety guardrails: Mandatory confirmation gate before spending money, absolute-path enforcement, secret redaction on intake (sk-, r8_, Bearer tokens, cookies), and refusal to overwrite existing non-empty outputs. - Use Case: Turn a short story into a 4-panel comic series: the pipeline analyzes the content, writes four image specs with embedded character descriptions, dry-runs the adapters to check API keys, then generates and verifies each PNG on disk. ## Quick Start Ask the agent to turn your story or brief into a series of image or audio assets using the structured asset pipeline, and confirm the backend and scope at the confirmation gate before generation begins.

Frequently Asked Questions about structured-asset-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I batch generate images from a story or brief?

Provide your content and the pipeline analyzes it, writes one YAML spec per image unit, then asks you to confirm backend and scope before generating. Each adapter call writes to an absolute output path and verifies the file is non-empty before moving on.

Which image and audio generation backends are supported?

Image backends are OpenAI Images (gpt-image-1, dall-e-3), Replicate, fal.ai, and local ComfyUI. Audio backends are ElevenLabs TTS and an unofficial Suno proxy adapter. Each backend is an independent adapter script following the same CLI contract.

Can I regenerate a single failed unit without redoing everything?

Yes, the regenerate-N partial workflow targets specific units by id or number. The existing output is renamed with a timestamped backup suffix before the adapter reruns, and the report is updated with the new status.

Does the pipeline work without API keys configured?

Dry-run mode works without credentials and validates specs, paths, and required env vars, exiting 2 with the missing variable names. Live generation requires the backend's key, such as OPENAI_API_KEY, REPLICATE_API_TOKEN, FAL_KEY, or ELEVENLABS_API_KEY.

Why does the pipeline require absolute paths for outputs?

Relative paths caused a real incident where generated pages silently landed in the wrong directory after the working directory drifted between batches. All adapters reject relative --out paths with exit code 1 to prevent this class of failure.

When should I not use this generation pipeline?

Skip it for a single one-off image with no reproducibility need, since a lone asset does not justify a manifest and spec files. It is designed for batches, series, and workflows you may partially redo later.