Skill: Check Pricing Health
Audits the Norce pricing configuration and returns a plain-language report of issues and warnings. Wraps norce_pricing_check_price_list_setup with interpretation — so instead of raw status codes, you get a clear explanation of what is wrong, why it matters, and what to do about it.
Run it against all price lists for a full pre-launch audit, or target a specific price list for a focused check — for example before activating a campaign.
Required MCP servers: Pricing MCP. Config MCP recommended (for application and sales area context).
Who it is for: Pricing managers running routine health checks, pre-launch validation, or investigating unexpected pricing behaviour.
The skill
---
name: check-pricing-health
description: Audits Norce price list configuration and returns a plain-language report of issues, warnings, and recommended fixes. Run before launch or any significant pricing change.
---
You are running a pricing health check on the Norce pricing configuration.
Application ID: Use the application ID from your session instructions. If no
application ID is available, ask the user which storefront to audit before
proceeding.
Target: $ARGUMENTS
Determine the check mode based on the target:
- If a specific price list code or ID is provided, run a full check on that
price list only: call norce_pricing_check_price_list_setup with that price
list specified and full mode enabled.
- If no target is provided, run a full audit across all price lists:
call norce_pricing_check_price_list_setup in full mode.
After receiving the results, interpret them in plain language. Do not just
repeat the raw output — explain what each issue means and what needs to be
done to fix it.
Classify every finding into one of three levels:
🔴 **Critical** — will cause wrong or missing prices in production. Must be
fixed before go-live or before activating a campaign. Examples: missing
primary price list for an application, invalid pricing rule, expired price list
still assigned to a storefront.
🟡 **Warning** — will not immediately break pricing but indicates a
configuration risk. Should be reviewed soon. Examples: price list expiring
within 30 days, population rule referencing a flag with no products assigned,
mixed currencies within a price list hierarchy.
✅ **Passed** — configuration check completed with no issues found.
---
**Pricing health report**
Run: [full audit / specific price list: CODE]
Application: [storefront name]
**Summary**
- Critical issues: [N]
- Warnings: [N]
- Checks passed: [N]
**Critical issues** (fix before go-live)
For each critical issue:
- Price list: [name and code]
- Problem: [plain-language explanation of what is wrong]
- Impact: [what will go wrong for customers or the storefront if not fixed]
- Fix: [specific steps to resolve it]
**Warnings** (review soon)
For each warning:
- Price list: [name and code]
- Problem: [plain-language explanation]
- Recommended action: [what to do and by when]
**Passed checks**
[Brief summary of what was validated and confirmed correct]
**Next steps**
Prioritise the critical issues and suggest a clear order to address them.
---
If there are no critical issues and no warnings, confirm that the pricing
configuration looks healthy and is ready for production use.How to install
Save this skill using the filename check-pricing-health and follow the installation instructions for your client.
| Client | What to do |
|---|---|
| Claude Desktop | Create SKILL.md inside a check-pricing-health/ folder, zip it, upload via Settings → Skills |
| Claude Code | Save as .claude/commands/check-pricing-health.md, invoke with /check-pricing-health or /check-pricing-health SUMMER-2026 |
| VS Code / Cursor | Copy the skill content, replace $ARGUMENTS with a price list code or remove the Target line for a full audit, paste into chat |
What to customise
The application ID is read from your session instructions — no placeholder to fill in. If you want this skill to always target a specific storefront regardless of your default instructions, add Application ID: [the ID] directly after the description block.
This skill works well without additional customisation. The check covers all structural issues automatically. The main reason to customise it is to adjust the report format or to add domain-specific context:
Add a 30-day expiry window reminder. If your team reviews pricing monthly, you can tighten the expiry warning: replace the default 30-day window with a shorter period by adding to the prompt: Flag any price list expiring within 14 days as a critical issue, not a warning.
Add a scheduled routine. This skill pairs well with scheduling — run it every Monday morning and have the report waiting when the week begins. Ask your AI assistant to set it up: Every Monday at 08:00, run a pricing health check and summarise any new issues.
Example usage
/check-pricing-health
"Run a full pricing health audit before we go live next Thursday."
"Something is wrong with the Norwegian price list — run a health check on RETAIL-NO specifically."
"Check the Summer Sale price list and confirm there are no issues before it activates on Friday."
"Every Monday morning, run a pricing health check and send me a report of any new warnings or critical issues."
Related
- Investigate Price — dig into a specific product's price discrepancy
- Pricing manager how-to — full workflow guide for pricing managers
- Pricing MCP tool reference