What it does
Pulls the shared attributes (price, size, material, key specs) across a group of related products and lays them out as a comparison table, highlighting the differences rather than repeating identical fields across every column. Flags any product missing an attribute the others have, instead of leaving a blank cell unexplained.
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/product-comparison-table-builder/ (or ~/.claude/skills/product-comparison-table-builder/ for all projects)
GitHub Copilot (VS Code)
.github/skills/product-comparison-table-builder/
OpenAI Codex
.codex/skills/product-comparison-table-builder/
Cursor
.cursor/skills/product-comparison-table-builder/ (or ~/.cursor/skills/product-comparison-table-builder/ globally)
Compatibility
WordPress with WooCommerce active. Needs read access to product attributes and variations for the products being compared.
The complete SKILL.md for this skill:
---
name: product-comparison-table-builder
description: Use when a user wants a comparison table built across two or more related WooCommerce products, for a product page, category page, or buying guide.
---
# Product Comparison Table Builder
## When to use
A set of related products (variants, tiers, or similar items in a category) needs to be laid out side by side so a shopper can see the differences at a glance.
## Procedure
1. Pull each product's title, price, and attributes (size, material, capacity, or whatever fields the category uses consistently).
2. Identify which attributes are shared across all products in the set versus which only apply to some.
3. Build the table with one row per attribute and one column per product, ordering rows so the most decision-relevant attributes (price, then the biggest point of difference) come first.
4. Bold or otherwise flag cells where a product stands out (cheapest, only one with a given feature) so the table helps rather than just lists data.
5. If a product is missing data for an attribute the others have, mark the cell as "not specified" rather than leaving it blank or guessing a value.
6. Keep the table to the attributes that actually help a purchase decision, don't include every field in the product database.
## Guardrails
- Never fill in a missing attribute value with a guess, mark it as unspecified instead.
- Never mark a product as "best" or "recommended" in the table unless the user has defined what that ranking should be based on.