relay-imagegen

Generate images via relay endpoints with saved prompts and metadata sidecars.

30|1|Updated May 27, 2026
One-click install
npx skills add https://github.com/AwakeFantasy/relay-imagegen --skill relay-imagegen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: relay-imagegen
Source: https://github.com/AwakeFantasy/relay-imagegen/tree/main
Command: npx skills add https://github.com/AwakeFantasy/relay-imagegen --skill relay-imagegen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Generate or edit images through a local OpenAI-compatible relay or proxy endpoint, with saved prompt files and non-secret run metadata. Use when you want to avoid persistent OPENAI_API_KEY environment variables and reuse current Codex/ccswitch configurations.

Core Features & Use Cases

  • Save prompts under prompts/*.txt for reuse and consistency.
  • Write non-secret .meta.json sidecars with run metadata and prompt snapshots.
  • Support multiple configuration sources (Codex, ccswitch, or private JSON) for flexible workflows.

Quick Start

Generate an image through a relay-based OpenAI-compatible endpoint using prompts from prompts/*.txt and save a non-secret run metadata sidecar in generated/.

Frequently Asked Questions about relay-imagegen

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

FAQPage Schema
How do I generate images through a local relay endpoint while saving prompt files?

Image generation through a local relay endpoint saves prompts under prompts/*.txt and writes a non-secret .meta.json sidecar with run metadata next to each generated image. It reads Codex or ccswitch settings, injects API keys only into the child process, and validates output dimensions automatically.

Can I avoid persistent OPENAI_API_KEY environment variables when using relay-based image generation?

Yes, relay-based image generation avoids persistent OPENAI_API_KEY environment variables by injecting API keys only into the child process. It reads existing Codex, ccswitch configurations, or private JSON configs to authenticate, ensuring keys are not left exposed in your environment.

Does this image generation workflow support ccswitch configurations and Codex settings?

This image generation workflow supports multiple configuration sources including Codex, ccswitch, and private JSON configs. It reads these settings to determine relay endpoints and API keys, enabling flexible workflows without needing separate manual setup for each run.

What is the best way to reuse prompts for repeatable relay image generation?

The best way to reuse prompts for relay image generation is saving them under prompts/*.txt files. This centralizes prompts for consistency and reuse, allowing the workflow to read them directly and write a non-secret run metadata sidecar capturing prompt snapshots for each generated image.

How do I save non-secret run metadata sidecars next to generated images?

To save non-secret run metadata sidecars, the workflow automatically writes a .meta.json file next to each generated image in the generated/ directory. This sidecar captures run metadata and prompt snapshots without exposing secret API keys, ensuring safe version tracking.

What are the limitations of using private JSON configs for relay image generation?

Limitations of using private JSON configs for relay image generation include requiring valid relay endpoints and correct output dimensions. The workflow validates output dimensions and relies on private JSON configs or Codex settings, meaning misconfigured endpoints will cause generation failures.