What it does
Compares a product's previous and new price pulled from WooCommerce, calculates the percentage saved, and drafts short copy in multiple formats (email subject and body, a one-line social post, a banner headline) so the announcement can go out across channels without separate rewrites. Flags a price drop that looks like a data entry error instead of writing celebratory copy for it.
Install
This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:
Use it in your AI assistant
Claude Code
.claude/skills/price-drop-announcer/ (or ~/.claude/skills/price-drop-announcer/ for all projects)
GitHub Copilot (VS Code)
.github/skills/price-drop-announcer/
OpenAI Codex
.codex/skills/price-drop-announcer/
Cursor
.cursor/skills/price-drop-announcer/ (or ~/.cursor/skills/price-drop-announcer/ globally)
Compatibility
WordPress with WooCommerce active. Needs read access to a product's regular price and sale price fields.
The complete SKILL.md for this skill:
---
name: price-drop-announcer
description: Use when a user wants announcement copy written for a WooCommerce product whose price just dropped, across email, social, or an on-site banner.
---
# Price Drop Announcer
## When to use
A product's regular price and new, lower price are known and copy is needed to announce the drop to customers.
## Procedure
1. Pull the product's previous price and new price, and calculate the dollar amount and percentage saved.
2. If the drop is larger than about 50%, flag it back to the user as a possible pricing error before writing copy, rather than assuming it's intentional.
3. Draft an email subject line and 2-3 sentence body leading with the savings, not the product features.
4. Draft a one-line social post version and a short on-site banner headline, reusing the same savings figure for consistency.
5. Mention a sale end date only if one has been provided, otherwise leave it out rather than implying urgency that doesn't exist.
6. Keep all figures (price, percentage) exactly matching the source data, don't round in a way that changes the claim.
## Guardrails
- Never round or embellish the percentage saved beyond what the actual price difference supports.
- Never state or imply a sale end date or limited stock unless that information was explicitly provided.