Agent skill

Ecommerce Image Workflow

Reference-product ecommerce image workflow for generating a compact set of product-faithful main, feature, and lifestyle images from real product reference photos.

Apache-2.0Auto-check passedSales & Support

Install Ecommerce Image Workflow

skills CLI

$ npx skills add nexu-io/open-design --skill ecommerce-image-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install nexu-io/open-design ecommerce-image-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ecommerce-image-workflow .claude/skills/ecommerce-image-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "ecommerce-image-workflow" agent skill from https://github.com/nexu-io/open-design/tree/main/skills/ecommerce-image-workflow into .claude/skills/ecommerce-image-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecommerce-image-workflow", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/nexu-io/open-design/tree/main/skills/ecommerce-image-workflow

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add nexu-io/open-design --skill ecommerce-image-workflow -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nexu-io/open-design ecommerce-image-workflow --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ecommerce-image-workflow .agents/skills/ecommerce-image-workflow && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ecommerce-image-workflow" agent skill from https://github.com/nexu-io/open-design/tree/main/skills/ecommerce-image-workflow into .agents/skills/ecommerce-image-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecommerce-image-workflow", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nexu-io/open-design --skill ecommerce-image-workflow -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nexu-io/open-design ecommerce-image-workflow --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ecommerce-image-workflow .cursor/skills/ecommerce-image-workflow && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ecommerce-image-workflow" agent skill from https://github.com/nexu-io/open-design/tree/main/skills/ecommerce-image-workflow into .cursor/skills/ecommerce-image-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecommerce-image-workflow", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/nexu-io/open-design.git --path skills/ecommerce-image-workflow

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add nexu-io/open-design --skill ecommerce-image-workflow -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nexu-io/open-design ecommerce-image-workflow --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ecommerce-image-workflow .gemini/skills/ecommerce-image-workflow && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "ecommerce-image-workflow" agent skill from https://github.com/nexu-io/open-design/tree/main/skills/ecommerce-image-workflow into .gemini/skills/ecommerce-image-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecommerce-image-workflow", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install nexu-io/open-design ecommerce-image-workflow

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add nexu-io/open-design --skill ecommerce-image-workflow -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ecommerce-image-workflow .github/skills/ecommerce-image-workflow && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "ecommerce-image-workflow" agent skill from https://github.com/nexu-io/open-design/tree/main/skills/ecommerce-image-workflow into .github/skills/ecommerce-image-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecommerce-image-workflow", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nexu-io/open-design --skill ecommerce-image-workflow -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nexu-io/open-design ecommerce-image-workflow --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ecommerce-image-workflow .opencode/skills/ecommerce-image-workflow && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ecommerce-image-workflow" agent skill from https://github.com/nexu-io/open-design/tree/main/skills/ecommerce-image-workflow into .opencode/skills/ecommerce-image-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecommerce-image-workflow", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: ecommerce-image-workflow
GitHub stars: 100k
Token cost: ~2.4k tokens
SKILL.md length: 815 words
Files: 3 (incl. references)
Skills in repo: 245
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Reference-product ecommerce image workflow for generating a compact set of product-faithful main, feature, and lifestyle images from real product reference photos.

Works in 8 steps: Confirm reference-product mode → Extract product identity anchors → Build a three-slot shot plan → …
Tasks that involve E-commerce operations
SKILL.md covers Resource map, What this skill produces, Input contract and Workflow, plus 1 more section
Calls python3

What it does

Ecommerce Image Workflow is an agent skill from nexu-io/open-design. Reference-product ecommerce image workflow for generating a compact set of product-faithful main, feature, and lifestyle images from real product reference photos. V1 requires uploaded product imagery and intentionally defers brief-only concept generation and platform-specific batch exports.

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/checklist.md`).

It sits in Sales & Support, covering E-commerce operations. The repository describes itself as: 🎨 Best DeepSeek Harness Design Plugin. The open-source Claude Design alternative. 🖥️ Local-first desktop app. 🖼️ Your coding agent becomes the design engine: prototypes… The licence is Apache-2.0.

When your agent uses it

Tasks that involve E-commerce operations

Example prompts

“/ecommerce-image-workflow”

Requirements

Python 3

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Confirm reference-product mode
Extract product identity anchors
Build a three-slot shot plan
Compose prompts with a fidelity lock
Dispatch through the media contract
Write image-manifest.json
Write ecommerce-gallery.html
Hand off

What it can do on your machine

Read from SKILL.md and the folder at commit d9dd6fe. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ecommerce Image Workflow loads about 2.4k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 79 tokens; SKILL.md has 815 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~79
When it runs · the whole SKILL.md, loaded when a task matches: ~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~3.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nexu-io/open-design at commit d9dd6fe, republished under its Apache-2.0 licence (© nexu-io). 815 words, ~2,422 tokens.

Download SKILL.mdSave it as .claude/skills/ecommerce-image-workflow/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: ecommerce-image-workflow
description: Reference-product ecommerce image workflow for generating a compact set of product-faithful main, feature, and lifestyle images from real product reference photos. V1 requires uploaded product imagery and intentionally defers brief-only concept generation and platform-specific batch exports.
en_name: Ecommerce Image Workflow
triggers: ecommerce product images, product image set, product photography workflow, product main image, product feature shot, reference product commerce images…
od.mode: image
od.surface: image
od.category: image-generation
od.scenario: marketing
od.example_prompt: Use the Ecommerce Image Workflow to turn my uploaded product reference photo into a compact ecommerce image set: one main packshot, one feature highlight…

Ecommerce Image Workflow

Create a compact ecommerce image set from real product reference imagery. This V1 skill is intentionally narrow: it supports reference-product mode only. If the user only describes a product and does not provide a product photo, ask for one and stop. Do not create a brief-only concept product in this version.

Resource map

text

ecommerce-image-workflow/
|-- SKILL.md
|-- example.html
`-- references/
    `-- checklist.md

What this skill produces

By default, generate three ecommerce-ready image assets for one product:

Main image - clean product-first packshot on white or soft neutral background.
Feature image - one selling point shown clearly with controlled callout space, without relying on tiny unreadable in-image text.
Lifestyle image - product shown in a plausible use context while keeping the product faithful to the reference.

Also create:

image-manifest.json describing reference inputs, slots, prompts, outputs, aspect ratios, and fidelity notes.
ecommerce-gallery.html as a small preview gallery linking the generated files and summarizing the image roles.

Input contract

Required:

At least one uploaded product reference image in the active project.

Ask only for missing essentials:

Product name or short label if it is not obvious.
Main selling point if the feature image cannot be inferred safely.
Target marketplace or aspect only if the user asks for platform-specific framing.

Do not ask broad discovery questions. Keep the workflow moving.

Workflow

Step 0 - Confirm reference-product mode

Before planning, verify that the current project includes a real product reference image.

If no product image is available, reply:

Please upload at least one product reference image first. This V1 workflow preserves a real product from reference photos; brief-only concept generation is deferred to a later version.

Then stop.

Step 1 - Extract product identity anchors

Inspect the reference image and write a short internal identity lock:

Product category and form factor.
Shape and silhouette.
Primary colors and materials.
Logo, label, pattern, fasteners, ports, straps, handles, or other fixed details.
Scale cues and proportions.
What must not change.

Use these anchors in every generation prompt.

Step 2 - Build a three-slot shot plan

Create a compact shot plan before dispatch:

Slot	Default aspect	Goal
main	1:1	Product-first marketplace image on white or soft neutral background
feature	4:5	One clear selling point with close-up detail or simple callout space
lifestyle	4:5	Realistic use context with the product still visually faithful

If the project metadata provides imageAspect, use it when the user expects a single aspect across the set. Otherwise use the slot defaults above.

Step 3 - Compose prompts with a fidelity lock

Every prompt must include this product fidelity instruction near the top:

text

Preserve the exact product identity from the reference image: shape,
silhouette, color, material, logo/label placement, visible construction
details, and proportions. Do not redesign the product. Do not add, remove,
or relocate product features.

Then add slot-specific instructions:

Main image prompt

Product centered and fully visible.
White, off-white, or very light grey background.
Soft studio lighting with clean shadow.
No props unless the user asked for them.
No in-frame marketing text.

Show full SKILL.md (361 more words)Show less

Feature image prompt

Focus on one user-provided or safely inferred feature.
Use close-up composition, cutaway-style crop, or clean negative space for later designer-added labels.
Keep the product visually balanced in the frame. If no explicit callout structure is being generated, center the product. If label space is needed, offset the product only slightly and make the empty space feel intentional.
Do not invent certifications, performance numbers, materials, or claims.
Avoid tiny rendered text; leave label space instead.

Lifestyle image prompt

Use a realistic environment matched to the product category.
Keep the product the focal point.
Show human interaction only if it helps explain use and does not obscure the product.
Preserve product scale and structure.

Step 4 - Dispatch through the media contract

Use the unified OpenDesign media dispatcher. Do not call provider APIs or custom model commands directly.

For each slot, run the standard generate/wait loop:

bash

# POSIX bash. Do not call provider APIs directly.
out=$("$OD_NODE_BIN" "$OD_BIN" media generate \
  --project "$OD_PROJECT_ID" \
  --surface image \
  --model "<imageModel from metadata>" \
  --aspect "<slot aspect or imageAspect from metadata>" \
  --image "<project-relative product reference image>" \
  --output "<product-slug>-<slot>.png" \
  --prompt "<full slot prompt>")
ec=$?
if [ "$ec" -ne 0 ]; then echo "$out" >&2; exit "$ec"; fi

last=$(printf '%s\n' "$out" | tail -1)
task_id=$(printf '%s\n' "$last" |
  python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('taskId',''))" 2>/dev/null)
since=$(printf '%s\n' "$last" |
  python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('nextSince',0))" 2>/dev/null)
since="${since:-0}"

while [ -n "$task_id" ]; do
  out=$("$OD_NODE_BIN" "$OD_BIN" media wait "$task_id" --since "$since")
  ec=$?
  last=$(printf '%s\n' "$out" | tail -1)
  since=$(printf '%s\n' "$last" |
    python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('nextSince',0))" 2>/dev/null)
  since="${since:-0}"
  if [ "$ec" -eq 0 ]; then
    task_id=""
  elif [ "$ec" -ne 2 ]; then
    echo "$out" >&2
    exit "$ec"
  fi
done

printf '%s\n' "$last"

The final line must be JSON with {"file": {"name": "...", ...}}. Record each final returned filename in image-manifest.json.

If the active image model or provider cannot use --image, stop and tell the user that this workflow needs a reference-capable image generation path for product fidelity.

Step 5 - Write `image-manifest.json`

After generation, create a project file named image-manifest.json:

json

{
  "workflow": "ecommerce-image-workflow",
  "mode": "reference-product",
  "productName": "Example product",
  "referenceImages": ["reference-product.png"],
  "fidelityNotes": [
    "Preserve product identity, color, material, construction, and proportions.",
    "Do not treat these outputs as platform-compliance proof without human review."
  ],
  "slots": [
    {
      "id": "main",
      "role": "marketplace packshot",
      "aspect": "1:1",
      "output": "example-product-main.png",
      "promptSummary": "Centered product-first packshot on a clean neutral background."
    },
    {
      "id": "feature",
      "role": "single feature highlight",
      "aspect": "4:5",
      "output": "example-product-feature.png",
      "promptSummary": "Close-up or negative-space composition for one verified selling point."
    },
    {
      "id": "lifestyle",
      "role": "usage context",
      "aspect": "4:5",
      "output": "example-product-lifestyle.png",
      "promptSummary": "Realistic scene with the product as the focal point."
    }
  ]
}

Keep the manifest honest. If a detail is unknown, write null or a short note instead of inventing claims.

Step 6 - Write `ecommerce-gallery.html`

Create a simple single-file HTML gallery that:

Shows the reference image first.
Shows the three generated slots with their role names.
Lists product-fidelity notes.
Links to image-manifest.json.
Uses system fonts and local project files only; no CDN imports.

Step 7 - Hand off

Reply with:

The generated filenames.
A one-sentence summary of the fidelity lock used.
A reminder that marketplace-specific compliance, final text overlays, and claim/legal review remain human review steps.

Do not emit an <artifact> tag.

Hard rules

V1 requires real product reference imagery. No brief-only concept products.
One product per run.
Default to exactly three slots: main, feature, lifestyle.
Preserve the product; do not redesign it.
Do not invent claims, certifications, measurements, ingredients, or performance data.
Use "$OD_NODE_BIN" "$OD_BIN" media generate; do not call provider APIs directly.
Always create image-manifest.json after generation.
Run references/checklist.md before handoff.

Files

SKILL.md and 2 other files (references) in skills/ecommerce-image-workflow of nexu-io/open-design.

SKILL.md
example.html
references/checklist.md

Open the folder on GitHubat commit d9dd6fe

Compare with similar skills

Ecommerce Image Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ecommerce Image Workflow compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Ecommerce Image Workflow this skillnexu-io/open-design	100k	—	~2.4k	Automated safety check: Pass	Apache-2.0	today
Amazon Buy Box Monitorbrowser-act/skills	6.1k	1 repos	~1.6k	Automated safety check: Pass	MIT	1 mo ago
Tourmind Bookingtourmind-com/Tourmind-Booking-Skills	1.7k	—	~13k	Automated safety check: Pass	MIT	yesterday
Ecommerce Image Suitewzj177/ecommerce-image-suite	446	—	~10k	Automated safety check: Pass	Apache-2.0	1 mo ago
Zach Feature Demand Validatorzach22-1999/amazon-skills	208	1 repos	~2.3k	Automated safety check: Notes	MIT	1 mo ago
Caramel CouponsDevinoSolutions/caramel	141	—	~1.1k	Automated safety check: Pass	AGPL-3.0	today

Similar skills

Amazon Buy Box Monitor
browser-act/skills
Pulls Amazon product details, competing seller prices and seller ratings for a given ASIN through the BrowserAct API, without browser automation.
6.1k GitHub starsUsed in 1 repo~1.6k tokens
Sales & SupportAuto-check passed
Tourmind Booking
tourmind-com/Tourmind-Booking-Skills
MUST USE for any hotel or accommodation intent in any language, including hotel search, hotel recommendations, nearby accommodation, hostels, guesthouses, resorts, where-to-stay questions, room…
1.7k GitHub stars~13k tokensUpdated yesterday
Sales & SupportAuto-check passed
Ecommerce Image Suite
wzj177/ecommerce-image-suite
电商套图生成助手。用户明确提出需要生成电商套图、商品主图、卖点图、场景图、模特图等图片内容时触发. An agent skill from wzj177/ecommerce-image-suite.
446 GitHub stars~10k tokensUpdated 1 mo ago
Sales & SupportAuto-check passed
Zach Feature Demand Validator
zach22-1999/amazon-skills
功能需求真伪验证器。用三维数据（Review/关键词/社区）验证微创新是否真实需求. An agent skill from zach22-1999/amazon-skills.
208 GitHub starsUsed in 1 repo~2.3k tokens
Sales & SupportAuto-check: notes
Caramel Coupons
DevinoSolutions/caramel
Look up live coupon / promo codes for any online store through Caramel's public API (grabcaramel.com) — use whenever the user is about to buy something online, asks for a discount or promo code, or…
141 GitHub stars~1.1k tokensUpdated today
Sales & SupportAuto-check passed
Zach Sif Cvr Threshold Analyzer
zach22-1999/amazon-skills
基于领星 ASIN 360 或同类日业务报表，以及用户自己 SIF MCP 导出的日级关键词自然排名 JSON，回测 CVR 与核心词/稳定词自然排名波动的关系，并输出观察线、危险线、广告 CVR 确认线。
208 GitHub starsUsed in 1 repo~982 tokens
Sales & SupportAuto-check: notes

More from nexu-io/open-design

All 245 skills in this repo

Humanize PPT
nexu-io/open-design
Turns raw notes into a talk-ready slide outline with per-page image, diagram or video decisions, then checks the rendered deck against that outline.
100k GitHub stars~4k tokensUpdated today
Auto-check passed
Last 30 Days Trend Research
nexu-io/open-design
Produces a cited Markdown briefing on recent community sentiment and social reaction to a topic, labeling every source it could not actually check.
100k GitHub stars~1.3k tokensUpdated today
Auto-check passed
OpenDesign Contribution Flow
nexu-io/open-design
Helps newcomers contribute to OpenDesign: ship a skill or design system, translate docs, fix docs or report a bug, ending in a pull request or issue.
100k GitHub stars~3.5k tokensUpdated today
Auto-check: notes
Chat Motion Overlay Generator
nexu-io/open-design
Turns a chat transcript or screenshot into a configurable animated chat clip, rendered as a Remotion bundle with optional transparency.
100k GitHub stars~1.1k tokensUpdated today
Auto-check passed
Flowai Live Dashboard Template
nexu-io/open-design
Team-management dashboard skill in the FlowAI aesthetic — three tabs (Team Members, Team Details, Activity Log), KPI stat row, member table, role distribution bar chart, online presence and activity…
100k GitHub stars~865 tokensUpdated today
Auto-check passed
Hatch Pet
nexu-io/open-design
Create, repair, validate, preview, and package Codex-compatible animated pet spritesheets from character art, screenshots, generated images, or visual references.
100k GitHub stars~6k tokensUpdated today
Auto-check passed

Questions about Ecommerce Image Workflow

What does Ecommerce Image Workflow do?

Reference-product ecommerce image workflow for generating a compact set of product-faithful main, feature, and lifestyle images from real product reference photos. Ecommerce Image Workflow is an agent skill from nexu-io/open-design. Reference-product ecommerce image workflow for generating a compact set of product-faithful main, feature, and lifestyle images from real product reference photos.

When should I use Ecommerce Image Workflow?

Ecommerce Image Workflow fits situations like: tasks that involve E-commerce operations.

How do I install Ecommerce Image Workflow in Claude Code?

Run `npx skills add nexu-io/open-design --skill ecommerce-image-workflow -a claude-code`. Or copy the skill folder (skills/ecommerce-image-workflow in nexu-io/open-design) into .claude/skills/ecommerce-image-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Ecommerce Image Workflow in Codex?

Run `npx skills add nexu-io/open-design --skill ecommerce-image-workflow -a codex`. Or copy the skill folder (skills/ecommerce-image-workflow in nexu-io/open-design) into .agents/skills/ecommerce-image-workflow in your project. Codex loads it when a task matches its description.

Can I use Ecommerce Image Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nexu-io/open-design --skill ecommerce-image-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ecommerce-image-workflow, .gemini/skills/ecommerce-image-workflow, .github/skills/ecommerce-image-workflow and .opencode/skills/ecommerce-image-workflow in your project.

What does Ecommerce Image Workflow need to run?

Going by SKILL.md and its folder, Ecommerce Image Workflow needs the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Ecommerce Image Workflow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ecommerce Image Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ecommerce Image Workflow use?

Ecommerce Image Workflow is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ecommerce Image Workflow use?

About 2.4k tokens (SKILL.md is roughly 9.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 797 tokens, read only when the agent opens those files.

What are the alternatives to Ecommerce Image Workflow?

Skills that share tags, products or a category with Ecommerce Image Workflow: Amazon Buy Box Monitor (browser-act/skills, 6.1k stars), Tourmind Booking (tourmind-com/Tourmind-Booking-Skills, 1.7k stars), Ecommerce Image Suite (wzj177/ecommerce-image-suite, 446 stars) and Zach Feature Demand Validator (zach22-1999/amazon-skills, 208 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ecommerce Image Workflow?

nexu-io (a GitHub organization) maintains it in nexu-io/open-design, which has 100,100 GitHub stars. The repository holds 245 skills in this directory. The repository was last updated on October 9, 2026.

Source: nexu-io/open-design on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Ecommerce Image Workflow

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Ecommerce Image Workflow

Resource map

What this skill produces

Input contract

Workflow

Step 0 - Confirm reference-product mode

Step 1 - Extract product identity anchors

Step 2 - Build a three-slot shot plan

Step 3 - Compose prompts with a fidelity lock

Main image prompt

Feature image prompt

Lifestyle image prompt

Step 4 - Dispatch through the media contract

Step 5 - Write image-manifest.json

Step 6 - Write ecommerce-gallery.html

Step 7 - Hand off

Hard rules

Files

Compare with similar skills

Similar skills

More from nexu-io/open-design

Related

Questions about Ecommerce Image Workflow

Step 5 - Write `image-manifest.json`

Step 6 - Write `ecommerce-gallery.html`