Give me a sales report for my WooCommerce store covering [last 30 days / 2026-07-01 to 2026-07-31 / all time]. Read the orders directly and do not change anything on the store.  Report: total revenue, number of orders, and a breakdown by status (processing, completed, on-hold, refunded, cancelled). Then list the top [5] products by revenue with quantity sold for each.  If there are more orders than fit in one response, keep paging until every order is counted. Finish with the total order count and total revenue on their own line so I can check them against WooCommerce.

I want to update prices in my WooCommerce store. Scope: [all products / the "Category name" category / products with SKU starting "ABC"]. Change: [increase by 10% / decrease by 5 EUR / round to the nearest .99].  Do this in two phases. Phase 1: read the matching products and show me a table with product name, SKU, current price, and proposed new price. Include variations for variable products. Do not write anything yet. Wait for my approval.  Phase 2, only after I say go: apply the changes, then show me the same table with the actual saved prices so I can confirm nothing drifted. Keep sale prices untouched unless I say otherwise.

I am going to give you a supplier CSV with columns [SKU, stock, price]. Match each row to a WooCommerce product or variation by SKU.  Before changing anything: show me a diff table with SKU, product name, current stock → new stock, current price → new price. List separately any SKUs in the file that do not exist in the store, and any store products that are not in the file (leave those untouched). Save a rollback list of the current values for every product you are about to change and show it to me.  Wait for my approval. After I approve, apply the updates and confirm the count of products changed.  [Paste the CSV here or attach it.]

Find WooCommerce products in [the "Category name" category / the whole store] where the long description is empty or under [50] words. Show me the list with product name and current description length first. Do not write anything yet.  For each product, draft a description in this format: one-sentence hook, a short paragraph on who it is for and what problem it solves, then 3 to 5 bullet points of specifications or benefits pulled from the product's existing attributes, short description, and title. Tone: [friendly and plain / technical and precise]. Do not invent specifications that are not in the product data.  Work in batches of [5]. Show me each batch for approval before saving it. Keep the short description unchanged.

Create [50] single-use WooCommerce coupon codes for a campaign called [Campaign name].  Rules: [15% off / 10 EUR off] the cart, minimum spend [40 EUR], one use per code, one use per customer, exclude sale items, expires on [2026-09-30]. Code format: [SUMMER-] followed by 6 random uppercase letters and numbers.  First show me a summary of the settings and three example codes. Wait for my approval. Then create the coupons and give me the full list of codes as a plain list I can paste into a spreadsheet, with the number created on its own line.

Create a new LifterLMS course called [Course title] as a draft. Do not publish it.  Structure it from this outline: [paste outline, or write "build a sensible outline for a beginner course on TOPIC with about 4 sections of 3 to 4 lessons each"].  For each section create the lessons in order. Put a short placeholder paragraph in each lesson describing what it will cover, so I can fill in the content later. Set every lesson to free preview off.  When done, show me the full section and lesson tree with the course edit link, and confirm the course status is draft.

Enroll the following people in the LifterLMS course [Course title]. For anyone who does not already have an account, create one with the Student role and send the standard new-user email. For anyone who already has an account, just enroll them.  Before doing anything, check each email against existing users and show me a table: name, email, account exists yes/no, already enrolled yes/no. Wait for my approval.  After I approve, run the enrollments and report how many accounts were created and how many enrollments were added, each on its own line.  [Paste list as: Full Name, [email protected] — one per line]

Give me a progress report for the LifterLMS course [Course title]. Read-only, do not change anything.  Show a table of every enrolled student: name, email, enrollment date, percent complete, last activity date, and completed yes/no. Sort by percent complete, lowest first.  Then summarize: total enrolled, number completed, number with zero progress, and number with no activity in the last [30] days. Put those four counts on their own lines.

On the page [Page title or URL], which is built with [Elementor / Divi], make these changes: [rewrite the hero heading to "…" / change the button color in the pricing section to #FF5A1F / add a three-column testimonials section below the features section].  First inspect the page and tell me its current structure (sections and their headings) so we agree on which section you are editing. Do not change anything yet.  After I confirm, make the edits through the builder's own save method so the page stays editable in [Elementor / Divi]. Do not edit the raw post content. When done, give me the preview link and list exactly what changed.

Give me a full inventory of this WordPress site. Read-only, change nothing.  Cover: WordPress and PHP version, active theme and whether it has a child theme, every installed plugin with version, active/inactive, and whether an update is available; all users with the Administrator role and their last login if available; total posts, pages, products, and media; permalink structure; whether search engines are blocked; and any custom code snippets or must-use plugins.  End with a short list of anything that looks risky or out of date, in priority order.

Check this site for available plugin, theme, and WordPress core updates. Show me the list with current version → new version and, where you can find it, the changelog headline. Do not update anything yet.  After I approve the list, update them one at a time. After each one: confirm the update succeeded, load the homepage and one interior page, and tell me whether they return normally. If anything breaks, stop immediately, tell me which update caused it, and do not continue.  Do core last. At the end, give me a summary of what was updated and what was skipped.

Run a security audit on this site. Phase 1 is read-only.  Check: WordPress core and plugin files against official checksums and list any modified or unexpected files; every Administrator account, flagging any I did not list here as known: [name1, name2]; whether XML-RPC is enabled; whether file editing is enabled in wp-admin; whether the site exposes the WordPress version publicly; and any plugins that are inactive but still installed.  Give me the findings grouped by severity. Then propose fixes, marking each one as safe (reversible, no visible change) or needs review. Do not apply anything until I approve, and never delete a user account; demote instead and tell me.