
Product Showcase
Generate a multi-page marketing site with real screenshots and GIF walkthroughs so prospects understand a complex or agentic web app.
Install
npx skills add https://github.com/jezweb/claude-skills --skill product-showcaseWhat is this skill?
- Three depth levels: quick single page, standard multi-page, thorough per-feature plus comparison and docs-style demo
- Browses the live app to capture real screenshots—not placeholder marketing art
- Builds animated GIF walkthroughs for workflows that static heroes cannot explain
- Targets complex and agentic products where “what it does” needs progressive depth
- Trigger phrases include showcase site, demo site, product page, and marketing site
Adoption & trust: 664 installs on skills.sh; 841 GitHub stars; 1/3 security scanners passed (skills.sh audits).
Recommended Skills
Seo Auditcoreyhaines31/marketingskills
Copywritingcoreyhaines31/marketingskills
Twitter Automationqu-skills/skills
Marketing Psychologycoreyhaines31/marketingskills
Content Strategycoreyhaines31/marketingskills
Programmatic Seocoreyhaines31/marketingskills
Journey fit
Primary fit
Canonical shelf in Launch because the deliverable is outward-facing distribution copy and demo pages, not product code. Distribution fits: the skill browses the running app and ships deployable pages that explain value on the open web.
Common Questions / FAQ
Is Product Showcase safe to install?
skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Product Showcase
# Product Showcase Generator Generate a marketing website that actually teaches people what a web app does. Not just a hero and feature grid — a multi-page site with real screenshots, animated GIF walkthroughs of workflows, feature deep-dives, and progressive depth from "what is this" to "here's exactly how it works." Especially valuable for complex apps, agentic AI tools, and anything where a static screenshot doesn't convey the value. ## Depth Levels | Depth | Output | Duration | |-------|--------|----------| | **quick** | Single page — hero, features, CTA. Same as before. | 15-20 min | | **standard** | Multi-page site — home, features page, how-it-works with screenshots. | 1-2 hours | | **thorough** | Comprehensive site — home, per-feature pages, animated GIF walkthroughs, use cases, comparison page, docs-style demo. | 3-6 hours | Default: **standard** ## Browser Tool Detection Before starting, detect available browser tools: 1. **Chrome MCP** (`mcp__claude-in-chrome__*`) — preferred for authenticated apps 2. **Playwright MCP** (`mcp__plugin_playwright_playwright__*`) — for public apps 3. **playwright-cli** — for scripted flows ## Workflow ### 1. Gather Input | Field | Required | Example | |-------|----------|---------| | App URL | Yes | `https://app.example.com` or `http://localhost:5173` | | App name | Yes | "Acme CRM" | | Tagline | No | "The CRM that gets out of your way" | | Target audience | No | "Small business owners" | | Pricing info | No | Free tier, $29/mo pro | | CTA text + URL | No | "Start Free Trial" → signup page | | Testimonials | No | User provides or skip section | ### 2. Capture Screenshots Use `capture-screenshots` (shipped in `bin/`) to capture the app. This is faster and more consistent than generating Playwright scripts each time. #### Quick capture (all key pages at once): ```bash capture-screenshots http://localhost:5173 \ --pages /,/dashboard,/contacts,/settings \ --output showcase/screenshots \ --prefix screen \ --mobile --dark ``` This produces desktop (1280x720), mobile (375px), and dark mode variants for each page in one run. #### For authenticated apps: ```bash capture-screenshots https://app.example.com \ --pages /,/dashboard,/settings \ --auth user:password \ --output showcase/screenshots \ --mobile --dark ``` #### What to capture: **a. First Impression** — the main page/dashboard becomes the hero image. Note the immediate value proposition. **b. Features** — each major section. Use `--pages` with all nav paths. Capture 6-10 key screens that tell the product story. **c. "How It Works" flow** — the main workflow in sequence. Run `capture-screenshots` multiple times with `--prefix workflow-step` as you navigate through the flow steps. **d. Detail shots** — zoom into specific UI elements. Use `--full-page` for scrollable content. **e. Both modes** — `--dark` flag captures light and dark variants automatically. Use the best-looking mode for the hero. #### Post-capture optimisation: ```bash img-process batch showcase/screenshots --action optimise --max-width 1920 -o showcase/screenshots-opt ``` #### f. Extract the Value Propositions Don't just list features. For each one, answer: **why does the user care?** - BAD: "Contact management page" - GOOD: "See every client, their history, and what needs attention — in one view" - BAD: "Search functionality" -