Agent skill · Content & Marketing

product-showcase-page

Build a single-product deep-dive showcase page as a self-contained HTML file. Triggers on: "build a product showcase page", "deep dive landing page for [product]", "create a product spotlight page", "product feature page", "single product page", "detailed page about [product]", "build a page showing everything about [product]", "create a long-form product page", "build a sales page for [product]", "product deep dive page", "make a feature breakdown page for [product]".

Affitorgithub.com/AffitorGitHub ↗
claude-codecursorMIT
Install
npx skills add Affitor/affiliate-skills --skill product-showcase-page --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 14 KB
Bundled scripts: none
Version: 1.0.0
Declared author: affitor
Requires: Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent
Path: skills/landing/product-showcase-page/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 586
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Product Showcase Page Build a long-form, single-product showcase page as a self-contained HTML file. Goes deeper than a standard landing page — includes a full hero section, feature breakdown with icons, use case demonstrations, testimonials, a pricing comparison table, FAQ with accordions, and multiple high-intent affiliate CTAs. Designed for pre-sold traffic (readers who came from a review or comparison) and wants to make the final conversion push. ## When to Use - User wants a dedicated page for one product that covers everything a buyer needs to know - User says "showcase page", "product spotlight", "deep-dive page", "feature breakdown page" - User wants a page longer than a standard landing page — for high-ticket products needing more persuasion - User is sending warm traffic (from a blog post or email) and wants to close the sale - User wants a page that can double as a product review in page form ## Workflow ### Step 1: Gather Product Data If `product` data is available from S1 or prior conversation, use it directly. Otherwise, use `web_search` to research the product: 1. **Features**: `"[product name] features"` — gather 6-12 distinct capabilities 2. **Pricing**: `"[produ

What's inside
Steps it walks through
  1. When to Use
  2. Workflow
  3. Step 1: Gather Product Data
  4. Step 2: Plan the Page Architecture
  5. Step 3: Write the Full HTML
  6. Step 4: Format Output
  7. Input Schema
  8. Step 5: Self-Validation
  9. Output Schema
  10. Output Format
  11. Error Handling
  12. Examples
  13. References
  14. Flywheel Connections
Ships with 2 files
  • LICENSE.txt
  • references/conversion-principles.md
More from affiliate-skills
All skills →
About this skill
What does the product-showcase-page skill do?

Build a single-product deep-dive showcase page as a self-contained HTML file. Triggers on: "build a product showcase page", "deep dive landing page for [product]", "create a product spotlight page", "product feature page", "single product page", "detailed page about [product]", "build a page showing everything about [product]", "create a long-form product page", "build a sales page for [product]", "product deep dive page", "make a feature breakdown page for [product]".

How do I install it?

Run `npx skills add Affitor/affiliate-skills --skill product-showcase-page --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Affitor/affiliate-skills, a repository with 586 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going