photos

Marketplace Photos

Review every photo in a target directory and produce a ranked photo order for a marketplace listing, with explicit skips.

When to use

Trigger automatically when:

• The user names a directory of product photos and asks for a recommended order
• The /marketplace:listing orchestrator delegates photo review
• The user is preparing a Facebook Marketplace or eBay listing and has photographed an item

Required inputs

• Photo directory — Path to a folder containing image files. Default to ./Photos/ relative to the current item directory if not specified.
• Item name — Used to filter photos when the directory contains multiple items (filenames typically prefix the item, e.g., Strider-12-SportBalanceBike-01.jpeg).

If the directory is ambiguous and not derivable from context (e.g. the folder holds several items and the filename prefix doesn't disambiguate), ask which item — don't pick one. Surface it with options rather than guessing (see ${CLAUDE_PLUGIN_ROOT}/references/handling-ambiguity.md).

Process

1. Enumerate photos

List the directory and filter to images for the target item (typically by filename prefix). Sort by filename so numbering is stable.

Cap the set you actually read. The final listing wants only 5–8 photos, so reading 20+ full images is wasted context. If there are more than ~12 matching images, read the first ~12 in filename order — that's plenty to pick a hero, cover the main angles, and spot condition/duplication. Note in the output if you capped (e.g. "reviewed 12 of 20; the rest were additional angles").

If the directory doesn't exist or contains no matching images, stop here — don't invent filenames or a photo order. Emit a Block 1 that states no photos were provided plus a short shot list to capture before posting (hero 3/4, side profile, included extras, honest wear shots), and a Block 2 stating condition can't be assessed from photos. This is a normal outcome for items photographed later, not an error.