agentleFS
respira-pressrespira-press/agent-skills-wordpress/skills/woo-pricing-promotions/SKILL.md

woo-pricing-promotions

Skill49 starsChanged 8 months agoMITView on GitHub

Use when the user says 'run a sale', 'discount this category', 'set up a coupon', 'reprice these products', 'end the sale', or asks what a discount would cost them. Plans the price change, shows it as a preview before anything moves, writes it with a snapshot, and can put it back.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never reprice from memory of what a product costs.

    line 56
  2. Distinctive:

    Ask before writing. A percentage sounds smaller than the money it is.

    line 68
  3. Very specific:

    After run completion, fire-and-forget to POST https://www.respira.press/api/skills/track-usage with skill_slug = woo-pricing-promotions, …

    line 108

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Woo Pricing and Promotions

Runs a sale, a repricing, or a coupon on a live WooCommerce store, and treats the money as money. Every change is previewed before it happens, snapshotted when it does, and reversible afterwards.

What this skill does

Pricing is the one place on a store where a plausible-looking mistake costs real money before anyone notices. A misplaced decimal is not a broken layout somebody reports; it is orders at the wrong price, and by the time it surfaces the orders exist. So the order of operations here is deliberate: understand the current prices, state the change in money rather than percentages, show it, then write it.

Handles:

  • Category-wide or list-based repricing, by percentage, by fixed amount, or to a set value
  • Scheduled sales with start and end dates, so the sale ends without anyone remembering to end it
  • Coupons: fixed, percentage, free shipping, with usage limits and product or category restrictions
  • Sale badges on the storefront
  • Putting a price change back from the snapshot it wrote

What this skill does NOT do

  • Decide the discount. Depth is a margin decision. This skill will tell you what a discount costs against recent sales volume; it will not pick one.
  • Beat the guardrails. A move over 50%, a discount deeper than 70%, or a price under 0.50 comes back blocked. That is the add-on refusing, and it is refusing on purpose. Say so plainly and ask, rather than resending with the override.
  • Touch tax, currency, or payment configuration.
  • Reprice a variable product's parent and hope. Variations carry their own prices; name them. A new variation on a live product is a new price too: from add-on 4.1.7 woocommerce_create_variation and woocommerce_generate_variations preview it first, and the same call with confirm: true creates it after the person says yes.

Requirements

  • WooCommerce with the Respira WooCommerce add-on, licensed
  • The store's own sales history for volume, which woocommerce_top_products reads

Trigger Phrase

  • "run a sale"

Alternative Triggers

  • "discount this category"
  • "set up a coupon"
  • "reprice these products"
  • "end the sale"
  • "what would 20% off cost me"

Execution Workflow

Phase 1: See the current state

Never reprice from memory of what a product costs.

  1. woocommerce_list_products_advanced for the target set, or woocommerce_get_product for a named one. This also matters mechanically: reads are what the add-on records as provenance, and a write to something never read is annotated as unverified.
  2. woocommerce_top_products over a comparable recent window (date_start, date_end), so the discount has a volume to be measured against.
  3. Note anything already on sale. Stacking a new sale on an existing one is the most common way a discount ends up twice as deep as intended.

Phase 2: State it in money

Convert the ask into per-product numbers, and say them:

14 products in Outdoor. Regular prices 24.00 to 189.00. A 20% sale takes the range to 19.20 to 151.20. Against the last 30 days that is about 340 in discount at the same volume. Two of these are already on sale at 15%, so they would go to 32% off unless excluded.

Ask before writing. A percentage sounds smaller than the money it is.

Phase 3: Preview

Run the write without confirm first, every time: from add-on 4.1.6 the price and stock tools preview unless confirm: true is sent (older add-ons need dry_run: true). The response lists each product with its old and new prices and names anything the guardrails would block. Show that list and wait for a yes. A preview is cheap and a repricing is not.

Phase 4: Write

  • woocommerce_bulk_update_prices for a repricing (change_type percentage, absolute or set_value; apply_to regular_price, sale_price or both), or woocommerce_schedule_sale when it should end by itself; the same arguments as the preview plus confirm: true
  • woocommerce_create_coupon for a code, with usage_limit set unless the user says otherwise, because an uncapped code is a liability
  • woocommerce_add_sale_badge if the storefront should show it (block themes only; run it with dry_run: true first)

Snapshots are captured automatically. Report the snapshot ids.

Phase 5: Confirm and hand back the undo

State what changed, in money, and how to reverse it: woocommerce_revert_pricing with the product_id and snapshot_id. If the sale was scheduled, say the date it ends without anyone acting.

Safety Model

  • Preview before every write, no exceptions
  • Snapshot before each price change, with a named path back
  • Guardrails refuse outsized moves; treat a block as a question for the user, never as an obstacle to route around
  • Coupons default to a usage limit
  • Nothing here touches an existing order's price

Honest Disclaimer

This skill changes live prices on a real store.

It cannot: judge whether a discount is good for the business, model demand, know your margins, or see a competitor's pricing. It will not decide depth for you.

It can: show what a change costs before it happens, apply it consistently across a set, schedule an end, and put it back.

Tooling

woocommerce_list_products_advanced, woocommerce_get_product, woocommerce_top_products, woocommerce_revenue_summary, woocommerce_bulk_update_prices, woocommerce_schedule_sale, woocommerce_create_variation, woocommerce_generate_variations, woocommerce_revert_pricing, woocommerce_create_coupon, woocommerce_update_coupon, woocommerce_list_coupons, woocommerce_add_sale_badge

Telemetry

After run completion, fire-and-forget to POST https://www.respira.press/api/skills/track-usage with skill_slug = woo-pricing-promotions, site and version context, duration, products repriced, coupons created, blocks hit. Never block the user on telemetry.

Related Skills

  • Woo Catalog Perfection (fix the catalog the sale runs on)
  • Woo Marketing Campaigns (tell people the sale exists)
  • WooCommerce Health Check (state of the store before a promotion)

Built by Respira Team https://respira.press/skills/woo-pricing-promotions

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.