AugmentClaude
Apache-2.0VideoSpecs

Product Analysis

Extract product facts, images, and usage details from URLs or photos for generation.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up β€” so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/analyzing-products-supercmohq/ β€” the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Works for every skill.

    What this command does
    1. Makes a new, empty temporary folder.
    2. Downloads the skill's folder, skills/analyzing-products, from github.com/SupercmoHQ/superCMO-skills (branch main), the GitHub repository it's listed from. You get the version that is there now, not a copy we keep.
    3. Copies that folder to ~/.claude/skills/analyzing-products-supercmohq/.
    4. Deletes the temporary folder.

    Installing runs none of the skill's files; it only downloads and copies them. When you later use the skill, Claude follows its SKILL.md and may run scripts that come with it. Read them first.

    How we check skills, and what we don't Β· Report this skill

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates β€” they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description β€” no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the β€œWhat this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Normalizes a product into generation-ready facts β€” from an e-commerce URL (a clean description plus curated product images) or from a photo alone (category, how it's used, its moving/opening parts, and key visual details). Use when a product URL or photo needs turning into inputs for image/video generation, or when another skill needs product facts before generating.

What this skill does

Product Analysis

Turn a product β€” an e-commerce URL or a bare photo β€” into clean, reusable facts for downstream image/video generation: a tight description, curated product images, and how the product is physically used. It's a building block: other skills call it at the input stage, before any generation.

Workflow

Step 1: Pick the mode and run it

InputReferenceWhat you produce
An e-commerce URL (Amazon, Shopify, AliExpress, any product page)references/url-extract.mdA two-paragraph description + up to 5 downloaded, filtered product images
A product photo only (no URL, no description)references/photo-analysis.mdCategory + how it's used + moving/opening parts + key visual details

Read only the matching reference and follow it end to end. If both a URL and a photo are given, run the URL mode (richer) and keep the photo as one more reference image; if neither is given, there's nothing to analyze β€” ask for one. Don't pause for confirmation β€” a URL (or photo) plus generation intent means extract and proceed.

Step 2: Hand off

Return the result to whoever called you, ready to drop into generation:

  • URL mode β†’ the description and the kept image files (local paths, usable as reference images).
  • Photo mode β†’ the category, how it's used, any moving or opening parts, and the key visual details.

Don't rank the product's market position β€” the calling skill decides that from packaging cues. Your job is the objective facts.

Edge cases

  • The URL can't be extracted (no result, or the extractor isn't set up) β†’ ask for a product photo instead and switch to photo mode.
  • Every image fails the filter (faces, wrong variant, not a product shot) β†’ keep the single cleanest, or hand off the description alone and say plainly that no clean image survived.
  • A supplied photo is too unclear to read (blurry, cropped, ambiguous) β†’ say what you can't determine and ask for a clearer shot rather than guessing the mechanic.
  • Neither a URL nor a photo β†’ ask for one; there is nothing to analyze.

Reference

  • references/url-extract.md β€” the URL pipeline: url_extraction β†’ download the images β†’ filter them with image_analysis β†’ write the description.
  • references/photo-analysis.md β€” the photo pipeline: category, how it's used, moving/opening parts, and the visual details to preserve.

Related skills