AB image-scene-generator
Generates professional e-commerce product scene prompts (Midjourney/DALL-E/Stable Diffusion) with physics-based lighting, material-accurate rendering, and lifestyle compositions. Use when the user mentions product photography, scene rendering, Midjourney prompts, product mockup, lifestyle shot, flat lay, product visual, hero image, social media product content, AI-generated product image, product on background, studio shot, or wants to create realistic product visuals for their store—even if they do not say "Midjourney" or "scene" explicitly. Also trigger when users provide a product image or description and ask for "better photos," "more angles," or "lifestyle images."
As a process B 72/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
How to improve
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 72/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 4 branches
- 100Tools and files. No external tools needed
- 100Steps. 94 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3084 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- medium 3 test cases, all positive: not one "should refuse" or "should ask first"
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 678: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 94 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (1 of 2)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 99.