Lifestyle Scene
- What
- Cost
- Free
- Needs
- Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Place the exact product into a believable lifestyle or in-use scene (kitchen, bathroom, desk, outdoor, gym, bedroom, festive) for listing images, ads and social posts: a product identity lock pasted into every prompt, a scene picked from the built-in scene library, the product as the clear hero at about 35–55% of the frame at the platform sizes (Amazon 1:1 2000×2000, Shopify 4:5, Taobao 1:1, social 4:5 / 9:16), generation via your agent's built-in image tool, an OpenAI-compatible API key, or a one-click online link, then a QA note per asset.
Version:
Install
Copy the install package below, then paste it into Muse📌 Pinned version: commit f4566fdThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites: none for the install itself: no account, no API key, no paid service, and nothing else to install first. For using the skill afterwards, read this first: generation goes through one of three routes, and only one of them is free of keys — (a) your agent's own built-in image tool, if it has one (no key from me); (b) an API key route that needs Python 3 and my own API key in the environment variable GPTIMAGE_API_KEY, billed by the provider I choose (see the sends disclosed in point 2: the default endpoint in the bundled script is https://api.openai.com, and SKILL.md recommends the third-party OpenAI-compatible gateway https://tryallapi.com/v1 — if I set that base URL, my key and my images go to that gateway, not to OpenAI); or (c) a no-key online link route, where the final prompt leaves this machine in a link to a third-party site (also disclosed in point 2). Both bundled scripts use the Python standard library only — there is no extra library to install for this skill. I also provide the product photo myself: the skill asks for at least a front view, and text-only generation is only a concept, not the real product. Install "lifestyle-scene" for me. It places the exact product into a believable lifestyle or in-use scene for listing images, ads and social posts while keeping the product identical: first a product identity lock written from my reference photos and pasted verbatim into every prompt, then a scene picked from its scene library (kitchen, bathroom/beauty, desk/tech, outdoor, fitness, bedroom/home, festive), a prompt built from its template with the product as the clear hero at about 35–55% of the frame, generation through one of the three routes above (default model GPT Image 2.5 Flare, gpt-image-2.5-flare, for new scenes; Sunburst, gpt-image-2.5-sunburst, when a logo, label or small text must survive exactly), at the platform sizes in SKILL.md (Amazon secondary images 1:1 at 2000×2000, Shopify / DTC 4:5 at 1600×2000 or 1:1, Taobao / Tmall 1:1 at 800×800 or more, social / ads 4:5 feed and 9:16 stories), and a 3-line QA note per asset. Repository: https://github.com/xianyu110/ecommerce-image-skills (the skill is the whole skills/lifestyle-scene/ folder at the pinned commit: SKILL.md plus its scripts/ folder, 3 files) Pinned version: install the code at commit f4566fdc812584425728862ad8e08c90883d81ee exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/xianyu110/ecommerce-image-skills into a temporary folder, check out commit f4566fdc812584425728862ad8e08c90883d81ee, and copy the skills/lifestyle-scene/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-19: [FINGERPRINTS] - SKILL.md: SHA-256 f7d778dd1f5f2873682354378dc0d0acdcf67dbf0a26b80fbb692d4bc5945e08 - scripts/generate.py: SHA-256 5339fc5c9c3fd9bb02a1f0dd8643386329ba813c7ebe958a8d28241ed343d1c5 - scripts/online_link.py: SHA-256 72a6a843157d8cfb84f809d4811edefbc1e222dd10807037f0b64524ebb43ad3 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full and read both scripts in scripts/ (generate.py, online_link.py), and tell me in plain words: what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 3 files only: SKILL.md (5,917 bytes) and two Python scripts in scripts/ (generate.py 4,824 bytes, online_link.py 788 bytes). The two scripts in this folder are byte-identical copies of the same-named scripts at the repository root (scripts/): the skill is self-contained in its own folder and needs no file from elsewhere in the repository — not the other 11 skills, not the root scripts/, not the README. SKILL.md only ever calls the scripts sitting next to it (scripts/generate.py, scripts/online_link.py, relative to the skill folder). - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. No script is run during installation, no key is asked for, and there is no telemetry in the folder. - What leaves this machine at use time, disclosed here before it ever happens, by route — the skill picks the first route that works, and using the skill is a separate step that only starts when I ask for lifestyle scene images: (a) built-in image tool: the final scene prompt (with the identity lock pasted in) and my product photo(s) go to whatever image generation tool my agent already has (for example Codex imagegen or ChatGPT images), under that tool's own account and terms. (b) API key route: scripts/generate.py reads GPTIMAGE_API_KEY from the environment (never from a file, never printed), plus the optional GPTIMAGE_BASE_URL (default https://api.openai.com; SKILL.md recommends https://tryallapi.com/v1) and GPTIMAGE_MODEL, and sends an authenticated (Bearer key) request to that base URL — a JSON POST to /v1/images/generations carrying the prompt, model, size and count for text-to-image, or a multipart POST to /v1/images/edits carrying the same fields plus the product reference photo(s) I pass with --image (front, side, logo close-up). If the API answers with an image URL instead of base64 data, the script downloads that URL. Whichever base URL I set receives my key, my prompt and my product photos: if I set the recommended tryallapi.com gateway, that third-party gateway is the recipient, not OpenAI. (c) Online link route: scripts/online_link.py itself makes no network call — it only prints a link — but the link it builds is https://gptimage2.asia/generate?prompt=<my final prompt, URL-encoded>&utm_source=github&utm_medium=skill&utm_campaign=ecommerce-image-skills&utm_content=lifestyle-scene, so opening it sends my final prompt to gptimage2.asia, and SKILL.md tells me to upload my product photo on that site; SKILL.md also names an alternative site for users in mainland China, https://chatgpt-plus.top/list/#/home, where I would paste the prompt myself. Show that link once only, and never open it for me during installation. - The local-only parts at use time: the planning steps (identity lock, scene choice, prompt writing, QA note) stay local, between you and me, and both bundled scripts use the Python standard library only. The identity lock rule from SKILL.md: only facts visible in my photos or confirmed by me — never invent specs, sizes or certifications, and if I gave no photo, ask for one before generating. - Do not install anything else during this install, do not set or ask for GPTIMAGE_API_KEY, do not run either of the two scripts, and do not generate any image: setup of a generation route is my decision, later, when I actually ask for lifestyle scene images. 3. When I say "yes, install", install it as a skill: copy the whole lifestyle-scene folder into the agent's skills directory, in a folder named "lifestyle-scene", keeping all 3 files (SKILL.md at its root and the two scripts in its scripts/ subfolder). A manual clone followed by copying the skills/lifestyle-scene folder into ~/.claude/skills/ is the route described here; any other route is fine only as long as every installed file matches its fingerprint. 4. Verify with no network calls: frontmatter valid (name: lifestyle-scene), all 3 files in place with matching fingerprints. Do not run generate.py or online_link.py to verify. 5. Report what was installed, where, and what I still need to do myself (for example: provide a product photo, front view at minimum, and pick a scene; choose a generation route myself — my agent's built-in image tool if it has one, or set GPTIMAGE_API_KEY and, if I want it, GPTIMAGE_BASE_URL in my environment for the API route, knowing the key, prompt and product photos go to the base URL I set, or use the one-click online link knowing the prompt goes to gptimage2.asia; using the skill is a separate step that only starts when I ask for it, and the use-time sends disclosed above happen only then, on the route that runs). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.