agentleFS
jstanxjstanx/aeo-toolkit/skills/comparison-content/SKILL.md

comparison-content

Skill2 starsChanged 5 months agoMITView on GitHub

Create the comparison content answer engines lean on for buying decisions — "best X for Y" lists, alternatives pages, and head-to-head "X vs Y" comparisons, built to be cited and to get the brand fairly represented. Works for any business, B2B or B2C, product or service. Use when the request is to write a comparison or alternatives or "best of" page, get into AI recommendations for a category, win versus-queries, or earn citations on decision-stage prompts. Pairs with digital-pr (third-party lists) and community-and-reviews.

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:

    Read aeo-foundation.md for the category, the competitor/alternative set, the differentiators, and the decision-stage prompts.

    line 33
  2. Distinctive:

    Use real criteria buyers care about.

    line 43
  3. Distinctive:

    Keep it current — comparison facts (pricing, features) date fast (see

    line 48

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

This skill creates the comparison content that decides commercial AI answers: "best X for Y" roundups, "alternatives to" pages, and "X vs Y" head-to-heads. When a buyer asks an assistant to recommend or compare options, engines pull heavily from this format — listicles and comparison pages are among the most-cited content types for decision-stage prompts. The goal is twofold: create genuinely useful comparisons you can be cited for, and ensure the brand is fairly represented in others'. It works for any business, B2B or B2C.

When to use this skill

  • Writing a "best X for [use case]" or "alternatives to [competitor]" page.
  • Creating head-to-head "X vs Y" comparisons.
  • Targeting decision-stage prompts where engines recommend options.
  • Improving how the brand shows up in third-party comparisons.

Before you start

Read aeo-foundation.md for the category, the competitor/alternative set, the differentiators, and the decision-stage prompts. If it is missing, point to the aeo-foundation skill.

Two plays

1. Own comparisons (your site). Publish genuinely useful, honest comparisons. Engines (and Google's 2026-era quality stance) deprioritize transparently self-serving "we win everything" pages, so credibility is the strategy:

  • Use real criteria buyers care about; present them in a scannable table.
  • Be fair about where alternatives are stronger; balanced comparisons get trusted and cited, biased ones get discounted.
  • Make each option's row/section self-contained and answer-first (see answer-engineering), so an engine can lift a single comparison cleanly.
  • Keep it current — comparison facts (pricing, features) date fast (see content-freshness).

2. Earn placement (third-party). Most decision-stage citations come from independent comparisons — analyst pieces, review-site roundups, "alternatives" articles, and community threads. Getting the brand accurately included there is high-leverage:

  • Identify the third-party lists engines already cite for your prompts (from competitor-ai-analysis).
  • Pursue inclusion and accuracy through digital-pr and community-and-reviews.
  • Supply reviewers and publishers with correct, current facts so the brand is represented well.

Workflow

  1. Target the prompts. Pick the decision-stage prompts ("best X for Y", "X vs Y", "alternatives to Z") worth winning.
  2. Choose the play. Own page, earned placement, or both.
  3. Build the criteria. Define the comparison dimensions buyers actually weigh; gather accurate data for every option.
  4. Draft fair, structured comparisons. Tables for the at-a-glance view; self-contained, answer-first sections per option; honest trade-offs.
  5. Add evidence. Specific specs, pricing, and sourced claims (see evidence-and-citations).
  6. Pursue third-party inclusion for the independent lists engines cite.
  7. Maintain. Schedule refreshes; comparison content decays quickly.

Output format

  • The comparison page(s): intro answer block, criteria table, per-option sections, honest verdict/fit guidance.
  • A target list of third-party comparisons to earn placement in, with the current gap.
  • Fact sheets to supply reviewers/publishers for accurate representation.
  • (assumption) tags on any competitor facts to verify.

Common pitfalls

  • Transparently biased "we win every row" pages — distrusted and discounted.
  • Comparisons with no table or structure, so nothing extracts cleanly.
  • Stale pricing/feature facts that make the page wrong.
  • Ignoring the third-party lists that actually drive decision-stage citations.

Related Skills

  • competitor-ai-analysis — finds the comparisons and "vs" prompts to target.
  • answer-engineering / evidence-and-citations — structure and substance.
  • digital-pr — earns placement in independent comparison content.
  • community-and-reviews — review-platform and community comparison presence.

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.