Trust Signals
thedaviddias/Front-End-Checklist
A skill your agent uses when applies especially to e-commerce checkouts, contact/lead forms, pricing pages, and YMYL (Your Money or Your Life) content.
A skill your agent uses when producing product photography with Scenario from a real product photo: e-commerce packshots on white, transparent, or brand backgrounds, lifestyle scenes placing the…
Install Scenario Product Shots
$ npx skills add scenario-labs/skills --skill scenario-product-shots -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install scenario-labs/skills scenario-product-shots --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/scenario-product-shots .claude/skills/scenario-product-shots && rm -rf skills-srcUse ~/.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/
Install the "scenario-product-shots" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-product-shots into .claude/skills/scenario-product-shots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-product-shots", 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 install https://github.com/scenario-labs/skills/tree/main/skills/scenario-product-shotsType 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.
$ npx skills add scenario-labs/skills --skill scenario-product-shots -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install scenario-labs/skills scenario-product-shots --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/scenario-product-shots .agents/skills/scenario-product-shots && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "scenario-product-shots" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-product-shots into .agents/skills/scenario-product-shots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-product-shots", 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.
$ npx skills add scenario-labs/skills --skill scenario-product-shots -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install scenario-labs/skills scenario-product-shots --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/scenario-product-shots .cursor/skills/scenario-product-shots && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "scenario-product-shots" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-product-shots into .cursor/skills/scenario-product-shots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-product-shots", 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 https://github.com/scenario-labs/skills.git --path skills/scenario-product-shots--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add scenario-labs/skills --skill scenario-product-shots -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install scenario-labs/skills scenario-product-shots --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/scenario-product-shots .gemini/skills/scenario-product-shots && rm -rf skills-srcUse ~/.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/
Install the "scenario-product-shots" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-product-shots into .gemini/skills/scenario-product-shots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-product-shots", 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.
$ gh skill install scenario-labs/skills scenario-product-shotsInstalls 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).
$ npx skills add scenario-labs/skills --skill scenario-product-shots -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/scenario-product-shots .github/skills/scenario-product-shots && rm -rf skills-srcUse ~/.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/
Install the "scenario-product-shots" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-product-shots into .github/skills/scenario-product-shots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-product-shots", 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.
$ npx skills add scenario-labs/skills --skill scenario-product-shots -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install scenario-labs/skills scenario-product-shots --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/scenario-product-shots .opencode/skills/scenario-product-shots && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "scenario-product-shots" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-product-shots into .opencode/skills/scenario-product-shots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-product-shots", 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
scenario-product-shots- GitHub stars
- 946
- Token cost
- ~1.8k tokens
- SKILL.md length
- 803 words
- Files
- 1
- Skills in repo
- 146
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when producing product photography with Scenario from a real product photo: e-commerce packshots on white, transparent, or brand backgrounds, lifestyle scenes placing the…
- Works in 6 steps: upload_asset the studio photo, then… → Build the checklist once with… → Packshot: recommend with the packshot… → …
- Producing product photography with Scenario from a real product photo: e-commerce packshots on white
- SKILL.md covers Overview, Quick reference, The preserve-first prompt and Worked example: one can, a…, plus 1 more section
- Calls npx
What it does
Scenario Product Shots is an agent skill from scenario-labs/skills. Use when producing product photography with Scenario from a real product photo: e-commerce packshots on white, transparent, or brand backgrounds, lifestyle scenes placing the product in an environment, hero shots for a landing page or marketplace listing, angle and colorway sets, relighting or shadow fixes, or any shot where the label, logo, and shape must stay exact. Keywords: product photo, packshot, e-commerce, lifestyle shot, compositing, relight, label fidelity, catalog.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering E-commerce operations and Landing pages. The repository describes itself as: Get production-ready images, video, audio, and 3D from any AI agent: skills that pick the right model, price before spending, and keep characters and brands consistent through… The licence is MIT.
When your agent uses it
- Producing product photography with Scenario from a real product photo: e-commerce packshots on white
- Brand backgrounds
- Lifestyle scenes placing the product in an environment
- Hero shots for a landing page
Example prompts
- “/scenario-product-shots”
Requirements
- Node.js
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- upload_asset the studio photo, then upload_asset_complete: asset_can.
- Build the checklist once with asset_analyze (write lane, contract in scenario-asset-analysis); the inventory lands as a text asset, so…
- Packshot: recommend with the packshot need in the user's own words, model_schema_get the pick, then run it with asset_can in its image…
- Scenes: recommend with capability="img2img"; on next_step.type="ask_user", present the options (unattended, the task instructions name the…
- jobs_wait, then gate all four outputs in one asset_analyze call, the saved checklist passed via text_inputs and an instruction to read the…
- Upscale the keepers, asset_download with format="png", file the set in a collection.
What it can do on your machine
Read from SKILL.md and the folder at commit f6f8ab7. 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:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
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
Scenario Product Shots loads about 1.8k tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 803 words of instructions outside code blocks.
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 scenario-labs/skills at commit f6f8ab7, republished under its MIT licence (© scenario-labs). 803 words, ~1,802 tokens.
Download SKILL.mdSave it as
.claude/skills/scenario-product-shots/SKILL.md (or your agent's skills folder).- name
- scenario-product-shots
- description
- Use when producing product photography with Scenario from a real product photo: e-commerce packshots on white, transparent, or brand backgrounds, lifestyle scenes placing the product in an environment, hero shots for a landing page or marketplace listing, angle and colorway sets, relighting or shadow fixes, or any shot where the label, logo, and shape must stay exact. Keywords: product photo, packshot, e-commerce, lifestyle shot, compositing, relight, label fidelity, catalog.
- license
- MIT
Scenario Product Shots
Overview
The product is never generated. A text-prompted bottle ships a wrong label to a landing page; every credible shot starts from an uploaded photo of the real product, and fidelity is a gated check, not a hope. Two lanes cover most work: deterministic packshot tools (cutout, background, shadow, relight) and generative scene placement with an instruction-editing model. Connection and the core loop: see the scenario skill. Edit-model contracts: scenario-image. Deterministic tools: scenario-image-editing. Reading assets back: scenario-asset-analysis. Animating an approved still into an ad: scenario-video-ads. If a sibling skill named here is missing from your available skills, ask the user to install it (npx skills add scenario-labs/skills --skill <name>); unattended, proceed from tool schemas and flag the gap.
Quick reference
| Need | Route |
|---|---|
| The source | upload_asset the best photo available: sharp, evenly lit, whole product in frame (search "uncrop" finds tools that rebuild a clipped edge) |
| Fidelity checklist | asset_analyze the upload once, instructing an inventory of label text, geometry, materials, and colors; every later check reuses it |
| Packshot | recommend with the packshot need in the user's own words (a cutout-and-stage tool with solid, transparent, or custom backgrounds, margins, and shadows was the authoring-time hit), or background removal plus your own compose |
| Lifestyle scene | recommend with capability="img2img", product photo as reference, preserve-first prompt, one scene per run |
| Relight | search "relighting" (the authoring-time hit adjusts light, exposure, and mood, with a brand-color lock) |
| Upscale keepers | recommend with the user's own words; product-tuned upscalers existed at authoring time |
| Gate | asset_analyze the outputs against the checklist: up to 10 ids in images, the saved checklist in text_inputs, the letter-by-letter brief in instruction |
The preserve-first prompt
Scene prompts subordinate the world to the product: "The exact can from the reference image, proportions and colors unchanged, the label reads 'SUMMIT COLD BREW', no other text, standing on a wet slate counter, morning side light, shallow depth of field." Name the placement, the surface, the light. What goes unstated drifts: "label unchanged" alone leaves the type to whatever the model resolves from the reference, so the preserve clause quotes the checklist's label copy (existing on-pack text only) and the gate reads it back letter by letter rather than trusting the render.
Shadows and reflections carry the realism: a cutout pasted without them floats. Prefer a stage tool that rebuilds shadows, or name one in the edit prompt ("soft contact shadow falling right").
Show full SKILL.md (406 more words)Show less
Worked example: one can, a packshot plus three scenes
upload_assetthe studio photo, thenupload_asset_complete:asset_can.- Build the checklist once with
asset_analyze(write lane, contract inscenario-asset-analysis); the inventory lands as a text asset, soasset_downloadit and keep the text. - Packshot:
recommendwith the packshot need in the user's own words,model_schema_getthe pick, then run it withasset_canin its image field, the background set to the brand hex, and margins per the marketplace's current spec (confirm specs with the user; unattended, take them from the task instructions, else keep the tool's defaults). - Scenes:
recommendwithcapability="img2img"; onnext_step.type="ask_user", present the options (unattended, the task instructions name the pick, elseproceed:specialty.model_idfirst, skipping a specialty whosecaveatsorwhen_general_bettername the task at hand, then the toprankedentry, never one flaggedrequires_plan_upgrade).model_schema_getthe pick, then three runs, each the preserve-first prompt with one scene clause andasset_canwired as the schema says (an array only underarray: true). jobs_wait, then gate all four outputs in oneasset_analyzecall, the saved checklist passed viatext_inputsand an instruction to read the label back letter by letter. A drifted label fails the shot: re-run fromasset_canwith the preserve clause tightened (the quoted copy spelled letter by letter, "no other text" kept), never from the drifted output. Text the gate cannot resolve at output resolution is unverified, not passed: upscale and re-gate, or flag it in the delivery note.- Upscale the keepers,
asset_downloadwithformat="png", file the set in a collection.
Common mistakes
- Generating the product from a text description because the photo seems easy to describe: the one unfixable error, since no edit restores a label that never existed.
- Compositing from a screenshot of a crop: fidelity caps at the source; ask for the original file, and when nobody can supply one, proceed with the best source at hand and flag the ceiling in the delivery note.
- Skipping the gate because it "looks fine": label drift hides at thumbnail size; the checklist compare reads letter by letter.
- Prompting prices, claims, or promo copy into the image: overlay them with
scenario-text-overlay; regulations and locales change faster than plates. - Removing the background and losing the real shadow with it: restage with a shadow-building tool or prompt a new one.
- One run with a batch count for "the same scene, four angles": per-angle clauses need one run each (
scenario-image).
© scenario-labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/scenario-product-shots of scenario-labs/skills.
Open the folder on GitHubat commit f6f8ab7
Compare with similar skills
Scenario Product Shots 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Scenario Product Shots this skillscenario-labs/skills | 946 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Trust Signalsthedaviddias/Front-End-Checklist | 74k | — | ~619 | Automated safety check: Pass | MIT | |
| Ecommerce Landing Pagenexscope-ai/eCommerce-Skills | 1.1k | — | ~617 | Automated safety check: Pass | MIT | |
| UI UX Pro Maxsaoudi-h/solar-icons | 190 | 18 repos | ~11k | Automated safety check: Notes | Custom licence | |
| Pricing StrategyOpenClaudia/openclaudia-skills | 713 | — | ~1.8k | Automated safety check: Pass | MIT | |
| 12 Landing Page Brief Globalminhnv0807/ai-business-skills | 609 | — | ~3.9k | Automated safety check: Pass | MIT |
Similar skills
Ecommerce Landing Page
nexscope-ai/eCommerce-Skills
Audit and optimize e-commerce landing pages for conversion. An agent skill from nexscope-ai/eCommerce-Skills.
UI UX Pro Max
saoudi-h/solar-icons
UI/UX design intelligence for web and mobile. An agent skill from saoudi-h/solar-icons.
Pricing Strategy
OpenClaudia/openclaudia-skills
Optimize pricing pages, pricing models, and pricing strategy.
12 Landing Page Brief Global
minhnv0807/ai-business-skills
A skill your agent uses when a NEW landing page, sales page, or single-product page has to be built — seven-section structure, one page one goal one CTA, copy per block, mobile-first rules…
Suede Pricing
JasonColapietro/suede-creator-skills
Suede-owned pricing and packaging discipline. An agent skill from JasonColapietro/suede-creator-skills.
More from scenario-labs/skills
All 146 skills in this repoScenario Blender Grease Pencil
scenario-labs/skills
A skill your agent uses when drawing or animating with Grease Pencil in Blender 5.x from Python: 2D or 2.5D illustration, frame-by-frame animation, a cutout or part-based 2D character, strokes with…
Scenario Blender Hair
scenario-labs/skills
A skill your agent uses when grooming hair or fur in Blender with hair curves, such as a character hairstyle, animal fur, procedural fur in geometry nodes, or hair cards and mesh hair for games.
Scenario Blender Lighting Rendering
scenario-labs/skills
A skill your agent uses when lighting, rendering or compositing in Blender: light a character, product or hero shot, interior at dusk or night, three-point or motivated lighting, sun and sky, HDRI…
Scenario Chatgpt Pet Create
scenario-labs/skills
A skill your agent uses when creating a ChatGPT pet or Codex pet with Scenario: hatching an animated companion from a text idea, a character, mascot or brand cue, or reference photos and art; making…
Scenario Godot Animation
scenario-labs/skills
A skill your agent uses when animating characters or scenes in Godot 4.7: AnimationPlayer clips and RESET, AnimationTree state machines and blend spaces built in code, Mixamo or glTF import, loop…
Scenario Godot Audio
scenario-labs/skills
A skill your agent uses when adding or fixing sound in Godot 4.7: audio buses and effects, volume sliders, 'too many sounds', combat audio with hundreds of enemies, sounds clipping or distorting, 3D…
Related
Questions about Scenario Product Shots
What does Scenario Product Shots do?
A skill your agent uses when producing product photography with Scenario from a real product photo: e-commerce packshots on white, transparent, or brand backgrounds, lifestyle scenes placing the…. Scenario Product Shots is an agent skill from scenario-labs/skills. Use when producing product photography with Scenario from a real product photo: e-commerce packshots on white, transparent, or brand backgrounds, lifestyle scenes placing the product in an environment, hero shots for a landing page or marketplace listing, angle and colorway sets, relighting or shadow fixes, or any shot where the label, logo, and shape must stay exact.
When should I use Scenario Product Shots?
Scenario Product Shots fits situations like: producing product photography with Scenario from a real product photo: e-commerce packshots on white; brand backgrounds; lifestyle scenes placing the product in an environment; hero shots for a landing page.
How do I install Scenario Product Shots in Claude Code?
Run `npx skills add scenario-labs/skills --skill scenario-product-shots -a claude-code`. Or copy the skill folder (skills/scenario-product-shots in scenario-labs/skills) into .claude/skills/scenario-product-shots in your project. Claude Code loads it when a task matches its description.
How do I install Scenario Product Shots in Codex?
Run `npx skills add scenario-labs/skills --skill scenario-product-shots -a codex`. Or copy the skill folder (skills/scenario-product-shots in scenario-labs/skills) into .agents/skills/scenario-product-shots in your project. Codex loads it when a task matches its description.
Can I use Scenario Product Shots 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 scenario-labs/skills --skill scenario-product-shots -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scenario-product-shots, .gemini/skills/scenario-product-shots, .github/skills/scenario-product-shots and .opencode/skills/scenario-product-shots in your project.
What does Scenario Product Shots need to run?
Going by SKILL.md and its folder, Scenario Product Shots needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
Does Scenario Product Shots access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Scenario Product Shots 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 Scenario Product Shots use?
Scenario Product Shots is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Scenario Product Shots use?
About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Scenario Product Shots?
Skills that share tags, products or a category with Scenario Product Shots: Trust Signals (thedaviddias/Front-End-Checklist, 74k stars), Ecommerce Landing Page (nexscope-ai/eCommerce-Skills, 1.1k stars), UI UX Pro Max (saoudi-h/solar-icons, 190 stars) and Pricing Strategy (OpenClaudia/openclaudia-skills, 713 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Scenario Product Shots?
scenario-labs (a GitHub organization) maintains it in scenario-labs/skills, which has 946 GitHub stars. The repository holds 146 skills in this directory. The repository was last updated on October 10, 2026.
Source: scenario-labs/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.