PluginBench
Skill
Pass
Audit score 90

ads-photoshoot

agricidaniel/claude-ads

Generate rights-cleared product photography variants for paid ads from authorized source images.

What is ads-photoshoot?

Creates multiple photography style variants of a product for advertising use, starting from an authorized source image and brand profile. Use this when you need studio, lifestyle, ingredient, or contextual product shots for ad campaigns while maintaining legal compliance and brand consistency.

  • Generates distinct photography style variants (studio, lifestyle, contextual use, ingredient story, scale/detail shots)
  • Preserves product geometry, packaging, logos, labels, color, and materials unless explicitly approved for changes
  • Records source hashes, prompt versions, provider/model details, costs, output hashes, and dimensions for compliance
  • Validates product fidelity, visual defects, safe zones, accessibility, and policy compliance
  • Stores assets and manifest atomically with full provenance tracking

How to install ads-photoshoot

npx skills add https://github.com/agricidaniel/claude-ads --skill ads-photoshoot
Prerequisites
  • Authorized/rights-cleared source product image
  • Validated brand profile with product facts
  • Intended ad placements and specifications
  • Provider capability assessment and cost ceiling
Claude Code
Cursor
Windsurf
Cline

How to use ads-photoshoot

  1. 1.Confirm you have rights to the product image and gather the validated brand profile
  2. 2.Collect product facts, intended placements, provider capability, cost ceiling, and output directory
  3. 3.Define the distinct photography styles you need (studio, lifestyle, ingredient, scale, etc.)
  4. 4.Review and approve the generated variants for product fidelity and policy compliance
  5. 5.Store the assets and manifest in your run directory with full provenance records

Use cases

Good for
  • Create multiple ad-ready product photos in different styles from a single authorized source image
  • Generate lifestyle and contextual use shots for e-commerce and social media advertising
  • Produce ingredient or detail shots for product campaigns while maintaining brand consistency
  • Develop studio and floating product images for multi-placement ad campaigns
  • Generate photography variants within a defined cost ceiling and output specifications
Who it's for
  • E-commerce product managers
  • Advertising and marketing teams
  • Brand managers overseeing paid ad campaigns
  • Product photographers and creative directors
  • Compliance and legal teams managing advertising rights

ads-photoshoot FAQ

Can I modify the product appearance in generated photos?

Only if you explicitly approve changes. The skill preserves product geometry, packaging, logos, labels, color, and materials by default.

What compliance checks are performed?

The skill validates product fidelity, visual defects, safe zones, accessibility, and policy compliance before delivery.

Can I use these photos to create before/after claims or endorsements?

No. The skill prohibits creating deceptive before/after evidence, people or endorsements without authorization, or regulated claims from visual implication.

What metadata is recorded with each variant?

Source hashes, prompt version, provider/model used, cost, output hashes, and dimensions are all recorded for compliance and reproducibility.

Is human review required?

Yes, human review is mandatory before using generated variants in paid ads.

Full instructions (SKILL.md)

Source of truth, from agricidaniel/claude-ads.


name: ads-photoshoot description: "Generate rights-cleared paid-ad product photography variants from an authorized source image and validated brand profile. Triggers on: product photo, product photography, virtual photoshoot, photoshoot, enhance product image, studio shot, lifestyle shot, lifestyle product image, floating product image, ingredient shot."

Product Photography Variants

  1. Confirm rights to the product image and collect the validated brand profile, product facts, intended placements, provider capability, cost ceiling, and output root.
  2. Preserve product geometry, packaging, logos, labels, color, and material unless the operator explicitly approves a change.
  3. Define distinct production hypotheses such as studio, contextual use, ingredient story, scale/detail, or lifestyle; do not imply unsupported product outcomes.
  4. Generate approved aspect ratios and record source hashes, prompt version, provider/model, cost, output hashes, and dimensions.
  5. Validate product fidelity, visual defects, safe zones, accessibility, and policy.
  6. Store assets and manifest atomically inside the run directory.

Human review is mandatory. Do not create deceptive before/after evidence, people or endorsements without authorization, or regulated claims from visual implication.