Source profileQuality 94/100

event4u-app/agent-config/src/skills/image-generation/SKILL.md

image-generation

Generate an image from a brief — provider-agnostic blueprint then provider-specific translation, with ref-image/seed reuse for consistency. Use when generating/creating an image.

Source repository stars
7
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Generate an image end-to-end: capture the brief, route to the right provider, author a provider-specific prompt, reuse seeds for consistency, invoke the adapter, and apply governance. All adapters are scaffold-tier (dry-run) until promoted to stable.

Best for

  • User asks to generate, create, or produce an image from a brief.
  • End-to-end image production (routing + prompting + adapter invocation + governance).
  • When a consistent series of images needs seed/ref-image reuse across renders.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/event4u-app/agent-config --skill "src/skills/image-generation"
Safe inspection promptEditorial

Inspect the Agent Skill "image-generation" from https://github.com/event4u-app/agent-config/blob/0adf49a8ae84b0ff6e2de8759eea43257e020eff/src/skills/image-generation/SKILL.md at commit 0adf49a8ae84b0ff6e2de8759eea43257e020eff. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Procedure

    1. Capture the brief — extract: subject, output format (raster/vector/banner/icon), style intent, any existing ref images or seed values for consistency. 2. Route the provider via image-provider-routing — match job shape (text-in-image → Ideogram, photoreal → Flux, vector → Recr…

    Capture the brief — extract: subject, output format (raster/vector/banner/icon),Route the provider via image-provider-routing —Author the prompt via prompt-engineering-image —
  2. 02

    When to use

    User asks to generate, create, or produce an image from a brief.

    User asks to generate, create, or produce an image from a brief.End-to-end image production (routing + prompting + adapter invocation + governance).When a consistent series of images needs seed/ref-image reuse across renders.
  3. 03

    Output format

    1. Blueprint — provider choice + routing rationale + prompt string ready to copy. 2. Provider + prompt — adapter file reference, key params (aspect ratio, style, negative prompts), and any seed/ref-image value carried forward. 3. Artifact path / dry-run note — the path returned…

    Blueprint — provider choice + routing rationale + prompt string ready to copy.Provider + prompt — adapter file reference, key params (aspect ratio, style,Artifact path / dry-run note — the path returned by the adapter, or an explicit
  4. 04

    Gotcha

    Good example: Brief for a product-shot series → route to Flux (photoreal), author noun-phrase prompt, carry seed: 42 across all five renders, invoke adapter, note "experimental — dry-run plan only."

    Scaffold-tier adapters produce plans, not pixels — all four adapters (ideogram.sh,Seed reuse is the consistency lever — re-describing the subject more precisely- Scaffold-tier adapters produce plans, not pixels — all four adapters (ideogram.sh, flux.sh, recraft.sh, gemini-image.sh) are scaffold-tier (dry-run only). This skill produces the blueprint + dry-run confirmation; actu…
  5. 05

    Do NOT

    Do NOT claim a rendered asset is produced while adapters are scaffold-tier — surface

    Do NOT claim a rendered asset is produced while adapters are scaffold-tier — surfaceDo NOT skip image-likeness-and-rights when the brief names a real person, a brandDo NOT bypass image-provider-routing — selecting the wrong provider for the job

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score94/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars7SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
event4u-app/agent-config
Skill path
src/skills/image-generation/SKILL.md
Commit
0adf49a8ae84b0ff6e2de8759eea43257e020eff
License
MIT
Collected
2026-07-28
Default branch
main
View the original SKILL.md

image-generation

Generate an image end-to-end: capture the brief, route to the right provider, author a provider-specific prompt, reuse seeds for consistency, invoke the adapter, and apply governance. All adapters are scaffold-tier (dry-run) until promoted to stable.

When to use

  • User asks to generate, create, or produce an image from a brief.
  • End-to-end image production (routing + prompting + adapter invocation + governance).
  • When a consistent series of images needs seed/ref-image reuse across renders.

Procedure

  1. Capture the brief — extract: subject, output format (raster/vector/banner/icon), style intent, any existing ref images or seed values for consistency.
  2. Route the provider via image-provider-routing — match job shape (text-in-image → Ideogram, photoreal → Flux, vector → Recraft, general → Gemini/GPT Image 2).
  3. Author the prompt via prompt-engineering-image — apply provider-specific grammar (text-literal first for Ideogram, noun-phrase for Flux, style: param for Recraft, natural language for Gemini/GPT).
  4. Reuse ref-image / seed for consistency — if the brief is part of a series, carry the seed value or ref-image path forward. Seed reuse is the primary consistency lever; re-describing the subject each time is not.
  5. Invoke the adapter (dry-run today) — run node_modules/@event4u/agent-config/src/scripts/ai-image/adapters/<provider>.sh with the assembled params. Validate the returned artifact path or dry-run confirmation. All adapters are experimental (scaffold-tier); no live generation occurs until a maintainer promotes the adapter via provider-lifecycle-discipline.
  6. Apply governance — run the rights check (image-likeness-and-rights) when the brief names a real person, brand mark, or living artist's style. Attach the AI-disclosure footer per media-governance-routing before delivering the output.

Output format

  1. Blueprint — provider choice + routing rationale + prompt string ready to copy.
  2. Provider + prompt — adapter file reference, key params (aspect ratio, style, negative prompts), and any seed/ref-image value carried forward.
  3. Artifact path / dry-run note — the path returned by the adapter, or an explicit note: "adapter is experimental (scaffold-tier) — dry-run plan only; no rendered asset until promotion per provider-lifecycle-discipline."

Gotcha

  • Scaffold-tier adapters produce plans, not pixels — all four adapters (ideogram.sh, flux.sh, recraft.sh, gemini-image.sh) are scaffold-tier (dry-run only). This skill produces the blueprint + dry-run confirmation; actual renders require a maintainer to capture a smoke trace and promote the adapter to stable. Claiming a rendered asset exists when no adapter is stable misleads the caller.
  • Seed reuse is the consistency lever — re-describing the subject more precisely in each prompt does not lock character or style; carrying the seed value or ref-image path forward does. Drop the seed and character drift is inevitable across a series.

Good example: Brief for a product-shot series → route to Flux (photoreal), author noun-phrase prompt, carry seed: 42 across all five renders, invoke adapter, note "experimental — dry-run plan only."

Bad example: Invoking the adapter and telling the user "here is your rendered image" while all adapters are still scaffold-tier.

Do NOT

  • Do NOT claim a rendered asset is produced while adapters are scaffold-tier — surface the dry-run caveat explicitly every time.
  • Do NOT skip image-likeness-and-rights when the brief names a real person, a brand mark, or a named living artist's style.
  • Do NOT bypass image-provider-routing — selecting the wrong provider for the job shape (e.g. Flux for a text-in-image logo) produces garbled output.
  • Do NOT ignore seed/ref-image values when consistency across a series is required — seed reuse is the only reliable consistency mechanism.

See also

Alternatives

Compare before choosing

Computed 72359

sonichi/sutando

image-generation

Generate and edit images using Gemini Flash Image, and generate videos using Veo. Supports text-to-image, image editing, text-to-video, and image-to-video.

Computed 9438,313

wshobson/agents

brand-landingpage

Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established visual direction. Skip when they have a design mockup, need a dashboard or app UI, are working at component level, building a multi-page app, or restyling with known design tokens —

Computed 947

event4u-app/agent-config

prompt-engineering-image

Translate an image brief into provider-specific prompt grammar per model. Use when writing or refining an image-generation prompt for Ideogram, Flux, Gemini, GPT Image 2, or Recraft.

Computed 91234,327

affaan-m/ECC

videodb

See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize (codec, fps, resolution, aspect ratio), perform timeline edits (subtitles, text/image overlays, branding, audio overlays, dubbing, translation), generate media assets (image, audio, v