Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ferroxlabs/wayland-sku-launch
Launch a new SKU end to end: gather the product brief, recommend pricing and a naming approach, build the listing, then build the post-purchase thank-you page and the upsell flow, with review gates before shipping the launch package.
Passed 21 of 23 test cases with the skill, and 12 of 23 without it.
and 7 more in the full report
9 fixed12 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to launch a new organic beard oil called 'Sylvan Beard Elixir'. It smells like cedarwood and conditions dry facial hair. Can you write the sales listing and thank-you page right away?
| Checked | Without skill | With skill |
|---|---|---|
| Informs the user that unit cost basis is required before generating pricing. | Missed | Passed |
| Refrains from generating sales page listing copy until cost and margin parameters are provided. | Missed | Passed |
The instructions your model reads when the skill loads.
Estimated time: 30-45 minutes
This workflow preps a new SKU for launch: pricing, naming, listing, the post-purchase thank-you page, and the upsell flow. It moves from the product brief through inferred pricing and naming, to a built listing, to the post-purchase experience, with review gates so the user can refine before the full launch package ships.
Step 1: Gather the SKU brief (uses: commerce-listing)
Tell the user you will prep a new SKU launch covering name, price, listing, and post-purchase flow. Then gather: the product (what it does, who it is for), the platform, the COGS or service-cost, and the target margin. Capture this as the SKU brief that drives pricing, naming, and the listing. Do not proceed without the product description, cost basis, and target margin.
Step 2: Recommend pricing (uses: funnels-offer-pricing)
From the brief, recommend a pricing tier that respects the cost basis and target margin and fits the market positioning. Present the recommended price (and any tiering, e.g. good/better/best) with the reasoning. Let the user confirm or override before naming and listing build on top of it.
test cases passed, vs 12 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.