agentleFS
Sign inStart free
UXMagicaiUXMagicai/seosorted-skills/skills/comparison-pages/SKILL.md

comparison-pages

Skill0 starsChanged 39 days agoMITView on GitHub

Create "Brand vs Competitor" and alternative comparison pages with SEOsorted, built from the workspace's real competitor data, with comparison tables, an honest "where they offer more" section, FAQ and CTA. Use when the user asks for comparison pages, "X vs Y" articles, competitor alternative pages, or bottom-of-funnel content that converts.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Never disparage a competitor or state unverifiable claims about them — they will read the page.

    line 20

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

Comparison searches ("brand vs competitor", "competitor alternatives") come from buyers close to deciding. These pages convert well if they are credible, which means stating where the competitor is genuinely better.

Steps

  1. manage_competitors operation: "list". If a key competitor is missing, add it: operation: "add" with its URL (EDITOR).
  2. write_comparison_page operation: "list" to see which comparisons exist and their status.
  3. Prioritise: competitors the user loses deals to, and competitors with the highest search interest. Check volume for "<competitor> alternative" and "<brand> vs <competitor>" with research_keywords operation: "metrics".
  4. Confirm credits (one article credit each), then write_comparison_page operation: "generate" with competitor_id and an optional brief (positioning points, pricing facts with their source, what the user wants emphasised). Poll check_job_status.
  5. Review with manage_articles operation: "get": every competitor claim must be sourced and current, and the "where they offer more" section must be real.

Guardrails

Never disparage a competitor or state unverifiable claims about them — they will read the page. Prices must carry a source and date.

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.

Check your setup, free