Norce Agent Gateway
/
Norce Backend MCP Servers
/
Skills
/
Check Product Readiness
Last updated

Skill: Check Product Readiness

Runs a structured pre-publication readiness check on one or more SKUs. For each SKU it checks for product issues, missing translations, and how the product renders on the storefront — then produces a prioritised report showing which products are ready and which need attention.

Required MCP server: Product MCP

Who it is for: PIM managers and operators checking products before publication or campaign activation.

The skill

---
name: check-product-readiness
description: Runs a pre-publication readiness check on one or more Norce SKUs — checking for product issues, missing translations, and storefront rendering problems. Returns a prioritised report showing which products are ready and which need attention.
---

You are running a pre-publication readiness check on a set of Norce products.

Application ID: Use the application ID from your session instructions. If no
application ID is available, ask the user which storefront to check against
before proceeding.

Products to check: $ARGUMENTS

For each SKU (PartNo) provided, run the following checks in parallel:

1. **Product issues** — call norce_product_check_product_issues. Note all issues
   (blocking) and warnings (non-blocking) returned.

2. **Translation completeness** — call norce_product_list_missing_translations
   filtered to these SKUs. Note which locales have missing content for each SKU.

3. **Storefront preview** — call norce_product_preview_product with the
   application ID above. Note anything that looks incorrect or incomplete in
   the rendered result.

When all checks are complete, produce a structured report:

---
**Readiness summary**
- SKUs checked: [N]
- Ready for publication: [N]
- Need attention: [N]

**Results by SKU** (lead with the SKUs that have the most issues)

For each SKU:
- PartNo and product name
- Status: ✓ Ready / ✗ Needs attention
- Blocking issues: [list or "None"]
- Warnings: [list or "None"]
- Missing translations: [list locales or "None"]
- Storefront preview: [any problems or "Looks correct"]

**Recommended next steps**
Summarise what needs to be fixed before these products can be published, grouped
by type of fix (content, translations, configuration).
---

If no SKUs are provided in the arguments, ask the user which products to check
before proceeding.

How to install

Save this skill using the filename check-product-readiness and follow the installation instructions for your client.

ClientWhat to do
Claude DesktopCreate SKILL.md inside a check-product-readiness/ folder, zip it, upload via Settings → Skills
Claude CodeSave as .claude/commands/check-product-readiness.md, invoke with /check-product-readiness AB-1042 AB-2201
VS Code / CursorCopy the skill content, replace $ARGUMENTS with your SKU list, paste into chat

What to customise

Before using the skill, update the following in the skill content:

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.

Optional customisations:

  • Pin specific locales — if you always check the same set of languages, add them explicitly: Check translations for these locales: en-GB, sv-SE, de-DE. This prevents the check from covering locales you do not use.
  • Add required parametrics — if certain parametrics are mandatory for publication in your environment, add a step: Check that the following parametric IDs are populated: [IDs]. This catches gaps that the standard issue check does not flag.
  • Adjust the report format — if you want the output in a specific format (for example a table, or ready to paste into a spreadsheet), add that instruction to the report section.

If you work with multiple storefronts, you can maintain separate copies of the skill — one per application ID — or prompt the user to specify which storefront at the start.

Example usage

/check-product-readiness AB-1042 AB-2201 AB-3301

"Check these 10 SKUs before we activate the Summer campaign: [list]"

"Run a readiness check on everything in the Connectors category — start by looking up which SKUs are in that category, then check each one."

The last example combines a product lookup with the readiness check in a single prompt — the AI will use norce_product_lookup_products to find the SKUs first, then run the checks. You do not need to provide the SKU list manually if the AI can derive it from context.

Previous page
Next page