agentleFS
SkillMedevSkillMedev/ecommerce-dtc-ops/skills/comparison-page-builder/SKILL.md

comparison-page-builder

Skill1 starsChanged 39 days agoMITView on GitHub

Builds an honest "X vs Y" or "best alternative to X" comparison page - scannable table plus use-case routing copy - for high-intent commercial searches. Use when someone asks "write a page comparing us to a competitor", "build an X vs Y comparison page", "create an alternative-to page", or wants a competitor comparison table and copy that names a rival and helps the reader choose. Do NOT use for a general marketing landing page - use landing-page-copy instead; for competitor research itself, use competitive-intelligence.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every competitor data point is verifiable and carries a source or date.

    line 29
  2. Distinctive:

    Do not misstate a competitor's features or hide your product's weaknesses - refuse if asked.

    line 36
  3. Distinctive:

    Do not fill the table with vanity specs that do not affect the buying decision.

    line 37
  4. Distinctive:

    Do not force a head-to-head your product loses on the criteria most searchers care about.

    line 38
  5. Distinctive:

    Do not ship undated or unsourced competitor pricing and specs.

    line 39
  6. Distinctive:

    Do not bury the table below the fold under brand storytelling - the searcher came for the comparison.

    line 40
  7. Distinctive:

    Do not let the page rot: a comparison quoting a rival's discontinued plan or old pricing is the false claim that poisons the rest of the …

    line 41
  8. Distinctive:

    Do NOT use when building a single-product landing page, PDP, or generic marketing copy with no named rival, or an internal …

    line 42

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

Comparison Page Builder

Build a comparison page that wins "X vs Y" and "best alternative to X" searches by being genuinely fair, because a shopper who catches one false claim about a rival distrusts every claim about you.

Workflow

  1. Gather inputs: your product, the named competitor(s), the buyer segment you serve best, and the real, verifiable differences. If the requester cannot supply verifiable differences, stop and ask - do not invent them.
  2. Concede at least one real point: name something the competitor genuinely does better. Honest concession is what makes every other claim believable; "we win on everything" reads as marketing and converts worse.
  3. Build the table as the page centerpiece, placed within the first scroll. Pick 6-10 criteria that drive the buying decision (price, key features, support, warranty, ease of use, fit for use case), not vanity specs. One short value, phrase, or checkmark per cell. Attribute and date competitor figures; where a value is unknown, write "varies" or omit the cell - never fabricate a number.
  4. Frame by use case: add "Choose us if…" and "Choose them if…" blocks above or below the table. This routes the right buyer in, the wrong-fit buyer out (fewer refunds, better retention), and captures "X vs Y for [use case]" long-tail intent.
  5. Optimize for the query: use natural "X vs Y" phrasing in the H1, title, and intro; answer the implicit "which is better" question in the first paragraph - a direct 40-60 word answer is the format featured snippets favor; add an FAQ of 4-6 "Is X or Y better for…" questions; link to the relevant product page with descriptive anchor text.
  6. Run the legal/ethics check before shipping: every comparative claim is substantiated, accurate, and dated; no disparagement, no misleading trademark use, no stale pricing. Put a re-verification date on the calendar - competitor pricing and plans should be re-checked at least quarterly, and a table whose sources are more than 6 months old is a liability, not an asset.

Deliverable

Produce a publish-ready comparison page containing:

  1. The comparison table - 6-10 decision-driving criteria, one value per cell, every competitor figure sourced and dated.
  2. The routing copy - a direct first-paragraph answer to "which is better" (40-60 words), plus "Choose us if…" and "Choose them if…" blocks naming distinct buyer segments, including at least one honest concession.
  3. The SEO scaffolding - H1, title tag, and meta description using literal "X vs Y" phrasing; a 4-6 question FAQ; internal links to the relevant product page with descriptive anchors.
  4. A claims register - each comparative claim with its source and verification date, plus the scheduled quarterly re-check date.

Quality bar

  • Every competitor data point is verifiable and carries a source or date; no fabricated specs or prices.
  • At least one genuine competitor advantage is stated plainly.
  • Both "Choose us if…" and "Choose them if…" blocks are present and route distinct buyer segments.
  • The H1, title, and first paragraph all use the literal "X vs Y" phrasing and answer the buyer's question directly.
  • The table sits within the first scroll and no source behind it is older than a quarter without re-verification.

Do NOT

  • Do not misstate a competitor's features or hide your product's weaknesses - refuse if asked; it destroys trust and invites legal exposure.
  • Do not fill the table with vanity specs that do not affect the buying decision.
  • Do not force a head-to-head your product loses on the criteria most searchers care about; recommend a niche-angle page on a use case you genuinely win instead.
  • Do not ship undated or unsourced competitor pricing and specs.
  • Do not bury the table below the fold under brand storytelling - the searcher came for the comparison; make them scroll past marketing and they bounce.
  • Do not let the page rot: a comparison quoting a rival's discontinued plan or old pricing is the false claim that poisons the rest of the page.
  • Do NOT use when building a single-product landing page, PDP, or generic marketing copy with no named rival, or an internal feature-comparison spec - those are not commercial-intent "vs" pages.

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.