Claude Skills for Ecommerce: What They Are, How They Run, and Which 80 Are Worth Saving

A pre-built context file that turns Claude into a specialist for one ecommerce job: media buying, reporting, inventory. It packages the workflows, metric definitions and guardrails, and connects to your live store data through Polar’s MCP server. You run it, Claude proposes, you publish.

No. A skill is a file of instructions, not a script. You load it into Claude, connect Polar with an OAuth login, and ask in plain English. The only thing you need to be able to do is describe the decision you want made.

Yes, and most teams do. The thresholds, the guardrails and the output format are all editable text. Change the ROAS floor, add a rule about which SKUs are never discounted, or ask for the output as a Slack message instead of a table. Your version stays yours.

They run, but they answer on whatever data you hand them. Without a governed model the same skill can return three different numbers for the same question, because nothing fixes what net revenue or blended ROAS means. Polar is what makes the answer repeatable.

A plugin gives the model an action to call. A skill gives it the business context to decide with: your metric definitions, your thresholds, your approval rules, and the order in which to work. One extends what the model can touch, the other extends what it understands about your store.

Yes. The directory grows as teams publish the workflows they run every week, and existing skills are versioned when a definition or a guardrail changes.