• Apparel / model-related images (tops/bottoms/dresses/outerwear/shoes & hats, etc.) → Use

  linkfox-aigc-imagegen-cloth

  series.
• Pure image editing operations (background replacement, watermark removal, angle change, etc. with clear creative directions) → Use

  linkfox-aigc-imagegen

  .
• Pure text generation →

  linkfox-aigc-textgen

  .
• Video generation →

  linkfox-aigc-videogen

  .

• Input:

  imageUrls

• Empty Array Guard (Mandatory): If

  imageUrls

  is an empty array / missing / all invalid, stop immediately, do not call downstream with empty images. Prioritize supplementing from context (original image paths uploaded by the user in current/historical rounds); if still unable to supplement, truthfully report an error to the user and request re-upload, prohibit continuing execution with empty

  imageUrls

  .
• Operation: Check each value in

  imageUrls

  one by one (maintain original order): if it is already a public URL (starts with http/https) → directly pass through; if it is a local file path (non http/https) → call

  linkfox-file-upload

  to upload and obtain a public URL for replacement.
• Output:

  imageUrls

  (all are publicly accessible HTTPS URLs)

references/types/<type>.md

White Background Image Static Direct Generation Constraint (WHITE_BG): Use

scripts/build_imagegen_prompt.py --type WHITE_BG

to build the imagegen parameter file. The script will automatically extract the white background image static text from the

text

code block in

references/types/white-bg.md

as the final prompt. The text is long, always let the script read it, do not manually copy or pass via shell variables.

Textgen Chain Call Constraint (Applicable to All Types Except White Background Image): For types that need to call

linkfox-aigc-textgen

, must use this skill's

build_textgen_params.py

auxiliary script to build the textgen parameter file (the script automatically completes template reading, placeholder filling, model/thinkingLevel setting, sensitive word avoidance instruction appending), then execute according to the chain call method in textgen SKILL.md.

Image Set Must Go Through Pipeline Three Phases: Use

scripts/run_collection_pipeline.py

to run plan / dispatch / summary three phases for image set path, agent sends 3 Bash commands in sequence; concurrency is completed by skill layer dispatch using

ThreadPoolExecutor

, agent itself does not run concurrently:

1. --phase plan

   writes

   image-plan.json

   /

   collection-state.json

   , stdout directly outputs markdown table + 1 line of status JSON (including

   specs[]

   /

   run_one_task_script

   /

   state_file

   /

   total

   )
2. After user confirmation, agent only sends 1 dispatch Bash:

   python <root of this skill>/scripts/run_collection_pipeline.py --phase dispatch --state <state_file>

   ; dispatch internally uses

   ThreadPoolExecutor

   to run

   run_one_task.py --index 1..N

   concurrently, each subtask outputs

   task-result-<id>.json

   fragment; dispatch itself does not emit

   Saved full response

   in stdout, only 1 line

   {"status":"dispatch_complete",...}

   at the end for agent internal parsing (this Bash does not render images, it is normal)

3. --phase summary --state <state_file>

   reads fragments → stdout outputs final markdown details (each successful image comes with

   ![label](abs_path)

   inline reference, front-end markdown renderer renders the entire set of images based on this) + 1 line of status JSON; meanwhile, it merges and writes

   collection-asset-manifest.json

Prohibit Agent from manually executing S1 or reading full text of S0~S3; prohibit splitting into N Bash commands to run

run_one_task.py

after user confirmation (old protocol; concurrency is now completed at skill layer, self-concurrency will only result in duplicate images); prohibit stripping

![]()

lines when forwarding summary markdown (the entire set of images relies on these lines for rendering); prohibit attaching

Saved full response: [...]

outside summary (double rendering with markdown

![]()

). The following bash single-step link only applies to single-image direct generation.

Path Iron Rule: This link spans two skill directories (parameter construction scripts belong to this skill, text generation and parameter annotation scripts belong to

linkfox-aigc-textgen

), the current working directory is not fixed, all scripts must be called with absolute paths, do not use bare

scripts/...

relative paths (relative paths will point to wrong directories and cause execution failure). Where

<root of this skill>

= absolute path of the directory where this SKILL.md is located;

<textgen root directory>

is obtained by parsing the absolute path of the directory where its SKILL.md is located via

skill:linkfox-aigc-textgen

.

1. Parameter Construction (this skill):

   python <root of this skill>/scripts/build_textgen_params.py --type <TYPE> ... --out <textgen_params.json>

2. Text Generation (textgen skill):

   PROMPT=$(python <textgen root directory>/scripts/aigc_textgen.py --stdin --content-only < <textgen_params.json>)

   ——

   --content-only

   outputs single-line content captured into variable (line breaks are flattened to

   ⏎

   , downstream automatic restoration mechanism see textgen SKILL.md).
3. Parameter Annotation (step 3, inline with

   jq

   ): Use

   jq

   to inline

   $PROMPT

   into downstream imagegen parameter JSON, then pass to

   linkfox-aigc-imagegen

   for image generation.
   bash

   PROMPT=$(python <textgen root directory>/scripts/aigc_textgen.py --stdin --content-only < <textgen_params.json>)
   PARAMS=$(jq -nc --arg p "$PROMPT" --argjson imgs '<URL JSON array from step 1>' \
     '{prompt:$p, imageUrls:$imgs, provider:"<provider>", outputNum:1, aspectRatio:"<ratio>", resolution:"<resolution>"}')
   # Then pass $PARAMS to image generation according to the calling method in linkfox-aigc-imagegen SKILL.md

Prohibit manually constructing textgen parameter files with Write tool (must use

build_textgen_params.py

), extracting original content with

jq -r

(will reintroduce real line breaks and break splicing), or directly writing Python to call API to bypass this link.

• Input:

  prompt

  from step 2,

  imageUrls

  from step 1,

  ratio

  ,

  resolution

  ,

  provider

• Operation: Read SKILL.md of

  skill:linkfox-aigc-imagegen

  and execute image generation script according to its calling method. Pass parameters:

  • prompt

    : Final prompt produced in step 2

  • imageUrls

    : All image URLs from step 1

  • provider

    : Model specified by input parameters (default

    BANANA_PRO

    )

  • aspectRatio

    : Pass

    ratio

    as is

  • resolution

    : Pass as is

  • outputNum

    :

    1

• Output: Image (local path after

  Saved full response:

  )
• Single-image Direct Generation Delivery (By Type): For single-image direct generation scenario of this skill, follow §3.1 of

  references/runtime/03-deliver.md

  . After imagegen Bash is completed, agent must:
  1. Parse

     Saved full response: ["..."]

     in stdout to get local path (1 image when successful)
  2. Append markdown inline block to the conversation reply body:
     markdown

     - Image 1 · <Chinese name of type>
       ![<Chinese name of type>](<abs_path>)

  3. Chinese Name Mapping: SCENE→Scene Image / CLOSE_UP→Close-up Image / SELLING_POINT→Selling Point Image / WHITE_BG→White Background Image / PREMIUM_APLUS→Premium A+ Image / STANDARD_APLUS→Standard A+ Image / PHONE_APLUS→Mobile A+ Image
  4. Prohibit repeating the protocol text

     Saved full response: [...]

     /

     Saved full response: <json path>

     into conversation reply — it is an internal protocol line between skill ↔ bridge, repeating it will let users see exposed JSON array paths (i.e., "protocol line exposure" fault); only read it to get the path, do not copy the literal
  5. Prohibit manually echoing

     Saved full response:

     literal to let bridge render again — bridge path A's "task output" resource card is automatically triggered by imagegen Bash stdout, agent should not copy manually
  6. Double rendering (markdown inline image + bridge "task output" resource card displayed simultaneously) is expected behavior under current protocol, not a fault
  7. For failure cases (stdout is

     Saved full response: <data path>.json

     single file), truthfully inform according to "Error Handling and Failure Guards" in this SKILL.md, do not append inline image

linkfox-aigc-imagegen

skill returns exit 0 for business failures (non-zero exit is not used), so cannot judge success or failure by command exit code, must parse stdout.

• Success: stdout contains

  Saved full response: ["xxx.png", ...]

  (JSON array path) → Image has been stored in media/, get the path to display.
• Failure: stdout contains

  Saved full response: xxx.json

  (single JSON file path, non-array) → No image product, need to read the JSON to view error details (

  errcode

  /

  errmsg

  /

  error

  ).

errmsg

errorMsg

provider

aspectRatio

resolution

quality

AskUserQuestion

errcode==401

LINKFOX_AGENT_API_KEY

error

Connection failed

• ❌ Prohibit calling any other skill due to image generation failure — this skill has only one image generation path (

  linkfox-aigc-imagegen

  ), handle or report according to the above table when failed, never "try another skill".
• ❌ Prohibit unlimited retries: Except "transient error at most 1 time", do not retry the same type of failure repeatedly.
• ❌ Prohibit treating failed return body as success and continue (display empty image, tell user "generated successfully").

1. Agent layer passed

   resolution

   (value is 2K or 4K): use directly
2. Agent layer did not pass: use

   AskUserQuestion

   to let user select from 2K / 4K

1. No Upload Link: Product images are directly passed in the form of

   imageUrls

   , this skill does not involve local file upload operations (except URL verification in step 1), prohibit probing or calling any upload scripts.
2. Planning Tool Usage Specification: Do not use planning tools for single-image direct generation. Must create task plans for N images before concurrent image generation for image sets (see

   references/runtime/02-confirm.md

   ).
3. Image Set Storage: plan / summary are written to disk by

   run_collection_pipeline.py

   ; prohibit Agent from writing the entire manifest / image-plan from memory via Write.
4. Listing Report Write-back Asset Manifest (Mandatory): Retain

   $DATADIR/collection-asset-manifest.json

   after image set summary is completed. Listing HTML merge only uses

   agent-listing-result-html-skill/scripts/merge-listing-assets.mjs

   . If the manifest still contains local

   media/

   paths, the caller must first use

   linkfox-file-upload

   to replace them with public OSS URLs and update the manifest, then execute merge; this skill does not upload directly, but must not imply that local paths can be directly written into HTML.

• White background image template is static instruction, no category recognition and structure judgment, all categories are uniformly processed as "background removal + retouching + centered enlargement"; edge processing of special-shaped / transparent / reflective products may not meet expectations.
• Scene images/close-up images strongly rely on category and structure judgment of

  linkfox-aigc-textgen

  (

  GEM_3_FLASH

  ), judgment errors will directly affect composition.
• Selling point images/A+ images share dictionary templates, distinguished by

  {layoutInfo}

  ; wrong intent filling will lead to layout mismatch.
• Template text is written in apparel category tone ("fabric texture / version advantage"), adapted by model when used for non-apparel products.
• When multiple reference images are provided, the model judges the subject by itself, which may lead to misjudgment in complex combinations.
• No sensitive word rewriting (scene images/close-up images/white background images): if selling points/scenes contain prohibited content, this link does not intercept, controlled by upstream or manual review. Selling point images/A+ images include sensitive word avoidance in textgen phase.

• API Key Not Configured: Environment variable

  LINKFOX_AGENT_API_KEY

  is not configured, nor is

  LINKFOXAGENT_API_KEY

  .
• Response Returns 401 or 402 Status Code
• Response Indicates Insufficient Credits or Balance: Message contains "insufficient credit balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/need recharge/please recharge", or similar meanings.