agentleFS
respira-pressrespira-press/agent-skills-wordpress/skills/woo-catalog-perfection/SKILL.md

woo-catalog-perfection

Skill49 starsChanged 8 months agoMITView on GitHub

Use when the user says 'fix my catalog for ai', 'improve my ai readiness score', 'get my catalog to 90', or 'my products keep getting rejected by google'. Runs an ordered fixlist that writes the missing alt text, descriptions, brands, GTINs, and category mappings, snapshotting before each change.

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. Very specific:

    After each batch, woocommerce_validate_feed (google) for the score delta.

    line 65
  2. Distinctive:

    Never fabricate GTINs, specs, materials, dimensions or certifications.

    line 76
  3. Distinctive:

    Every write goes through the add-on's snapshot envelope.

    line 78

≈ “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 Catalog Perfection

Description

Close the loop from "your catalog scores 43" to "your catalog scores 90+", product by product, with every change snapshotted.

AI shopping surfaces reject rows that are missing images, descriptions, brands or identifiers, and rank thin content last. This skill runs the Respira readiness fixlist as a work queue: score the catalog, fetch the ordered list of failing products with the exact tool that fixes each gap, apply the fixes in safe batches, and re-score until the target is reached. It writes real content, not filler: descriptions are drafted from the product's own attributes, categories and existing copy, and anything uncertain is queued for the merchant instead of invented.

Requires the Respira WooCommerce Add-on v3.1+.


Trigger Phrases

This skill activates when the user says any of the following:

  • "fix my catalog for ai"
  • "improve my ai readiness score"
  • "fix products failing the feed checks"
  • "my products keep getting rejected by google"
  • "catalog perfection"
  • "fix missing gtins" / "fix missing brands" / "fix product descriptions"
  • "get my catalog to 90"
  • "clean up my product data"
  • "feed disapprovals woocommerce"

Do NOT trigger for: feed setup and platform registration (that is woo-agent-storefront), pricing changes, or content work outside the catalog.


Execution Workflow

Step 1: Score and scope

respira_get_site_context, then woocommerce_catalog_ai_readiness for the baseline score and woocommerce_readiness_fixlist for the ordered work queue. Report: current score, how many products fail which checks, and the estimated pass count. Agree the target (default 90) and the batch size (default 10 products per pass, so every batch is reviewable).

Step 2: Fix in priority order

The fixlist orders work by impact. Per product, apply only what the fixlist maps, using the tool it names:

  1. Missing GTIN → woocommerce_update_product with global_unique_id when the user can supply real GTINs (ask; never fabricate a GTIN. If none exist, assign brand + SKU so identifier rules pass via brand+MPN).
  2. Missing brand → woocommerce_create_brand / woocommerce_update_product brand assignment. Derive the brand from the product name or ask once for the house brand; apply consistently.
  3. Missing or thin description → woocommerce_update_product. Draft 40-80 words from the product's own attributes, category and existing short description. No invented specs, no superlatives.
  4. Missing image alt text → woocommerce_set_image_alt, descriptive and under 125 characters.
  5. Missing gallery → woocommerce_update_product with gallery_image_ids only from existing media (respira_list_media); never hotlink.
  6. Unmapped categories → woocommerce_set_feed_category_mapping to the closest Google taxonomy node.

Batch writes 10 at a time. Every write is snapshotted by the add-on automatically; state the snapshot coverage in the report.

Step 3: Re-score and loop

After each batch, woocommerce_validate_feed (google) for the score delta. Continue until the target is hit, the fixlist is empty, or the remaining items need merchant input (real GTINs, product photos). Queue those explicitly instead of guessing.

Step 4: Report

Close with: score before → after, products fixed per check type, what was written (with snapshot note: "every change is reversible for 90 days"), and the merchant-input queue (missing photos, GTINs to source). If feeds are enabled, remind that they rebuild automatically within minutes, so the fixes reach Google/ChatGPT on the next platform fetch.


Safety

  • Dry-run first on any bulk operation that supports it; show the preview before applying.
  • Never fabricate GTINs, specs, materials, dimensions or certifications. Uncertain = ask or queue.
  • Batches of 10 with a re-score between batches, so a bad pattern is caught after 10 products, not 500.
  • Every write goes through the add-on's snapshot envelope; mention rollback in the final report.

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.