Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →affitor/product-showcase-page
Build a single-product deep-dive showcase page as a self-contained HTML file.
Passed 6 of 22 test cases with the skill, and 6 of 22 without it.
1 fixed5 passed either way15 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Create a product showcase page for Figma targeting UI designers. Use stylish typography like Google Fonts Inter or Roboto to give it a polished SaaS feel.
| Checked | Without skill | With skill |
|---|---|---|
| The HTML uses native system font stacks without linking external Google Fonts. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
If product data is available from S1 or prior conversation, use it directly.
Otherwise, use web_search to research the product:
"[product name] features" — gather 6-12 distinct capabilities"[product name] pricing" — all tiers with feature differences"[product name] use cases" OR "[product name] examples" — concrete applications"[product name] reviews" on G2/Capterra — find real sentiment (do not copy verbatim — paraphrase or create realistic representative examples)"[product name] vs" — 2-3 competitors for the pricing comparison"[product name] questions" OR check product's own FAQ pageOrganize the research into these buckets:
Read references/conversion-principles.md for long-form page principles.
A product showcase page is longer than a standard landing page — it must justify the length with value at every section. Plan each section:
test cases passed, vs 6 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.