agentleFS
scayverscayver/marketing-skills/skills/competitors/SKILL.md

competitors

Skill8 starsChanged 5 months agoMITView on GitHub

Use this skill when writing competitor comparison or alternative pages for a website. Trigger phrases include: "write a competitor comparison page," "create an alternatives page," "write a [Product] vs [Competitor] page," "build a best [Competitor] alternatives page," "create a '[Your Product] vs [Competitor]' page," "write a competitor vs competitor page," "create a comparison landing page," or "write SEO content comparing us to competitors." This skill covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Distinct from competitor-profiling, which researches and documents a competitor for internal use.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 16

    Distinctive

    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:

    Write in a way that sounds like a knowledgeable human wrote it.

    line 12
  2. Distinctive:

    Use short sentences. One idea per sentence.

    line 13
  3. Distinctive:

    Use active voice. Never passive constructions.

    line 14
  4. Distinctive:

    Use bullet points only when they genuinely improve readability.

    line 16
  5. Distinctive:

    No hashtags, emojis, or asterisks.

    line 19
  6. Distinctive:

    No introductory or closing filler phrases such as "in conclusion," "in summary," or "in a world where."

    line 20
  7. Distinctive:

    No warnings, notes, or disclaimers.

    line 21
  8. Distinctive:

    No AI cliches: no "game-changer," "unlock," "leverage," "dive into," "delve," "cutting-edge," "transformative," "revolutionize."

    line 22
  9. Distinctive:

    No excessive adjectives or adverbs.

    line 23
  10. Distinctive:

    No broad generalizations. Every claim tied to specific context.

    line 24
  11. Distinctive:

    Use specific examples, data, and scenarios.

    line 25
  12. Distinctive:

    Update the year in the title and the content annually.

    line 145
  13. Distinctive:

    Consider [Your Product] if...: Introduce your product as the alternative for specific situations the reader might be in.

    line 217
  14. Distinctive:

    Update each page when:

    line 244
  15. Distinctive:

    Search volumes for the primary keyword change significantly

    line 249
  16. Distinctive:

    If the user has not provided enough information about their product's differentiators, ask before writing.

    line 274

“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “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

Competitors Skill

Mandatory Content Standards

  • Match the output length to the task. For full audits, strategies, plans, or multi-part deliverables, write 1,500 to 10,000 words. For quick tasks, single assets, snippets, or narrow revisions, keep the output concise and provide only the useful variations, rationale, and next steps.
  • Write in a way that sounds like a knowledgeable human wrote it. No robotic or templated phrasing.
  • Use short sentences. One idea per sentence. One focus per paragraph.
  • Use active voice. Never passive constructions.
  • Address the reader directly using "you" and "your."
  • Use bullet points only when they genuinely improve readability.
  • Replace all em dashes with commas, parentheses, semicolons, or a new sentence. No hidden Unicode characters.
  • End every sentence with a period.
  • No hashtags, emojis, or asterisks.
  • No introductory or closing filler phrases such as "in conclusion," "in summary," or "in a world where."
  • No warnings, notes, or disclaimers. Stick to requested output.
  • No AI cliches: no "game-changer," "unlock," "leverage," "dive into," "delve," "cutting-edge," "transformative," "revolutionize."
  • No excessive adjectives or adverbs. Let specifics do the work.
  • No broad generalizations. Every claim tied to specific context.
  • Use specific examples, data, and scenarios.
  • Pose at least one thought-provoking question per skill.
  • Mobile-friendly: short paragraphs, clear headers, scannable.
  • Practical and actionable. Every section connects to a next step.

What This Skill Does

This skill writes competitor comparison and alternative pages. These are SEO-driven pages designed to capture people who are actively evaluating tools in a category. They also serve as sales enablement assets for closing deals where a specific competitor is in the consideration set.

The four formats this skill covers:

Format 1: Singular alternative ("[Product] alternative"). A page targeting someone looking for one specific alternative to a specific tool. Example: "A Notion alternative for engineering teams."

Format 2: Plural alternatives ("[Product] alternatives"). A page targeting people searching for multiple options. Example: "The 7 best Asana alternatives in 2025."

Format 3: You vs competitor ("[Your Product] vs [Competitor]"). A direct comparison between your product and one competitor. Example: "Linear vs Jira: what's the difference?"

Format 4: Competitor vs competitor. A neutral-seeming page comparing two competitors, neither of which is your product, designed to capture high-intent comparison traffic. Example: "Notion vs Confluence: a side-by-side comparison."


Why These Pages Work

Someone searching "best [Competitor] alternatives" is not casually browsing. They have already decided they want to switch from a tool. They are actively researching options. That is some of the highest buyer intent in search.

The same applies to "[Product A] vs [Product B]" searches. People typing those queries are in active evaluation mode. They want to make a decision. A page that answers their comparison question clearly and honestly, while positioning your product well, captures that intent at the moment it is highest.

Here is the question that shapes everything else on these pages: what does the person searching this term actually want to know? Not what you want to tell them. What information would make their decision easier?

That answer should drive every section of the page.


What to Gather Before Writing

For any competitor comparison or alternative page, gather:

  • Your product name, core use case, and ideal customer
  • The competitor or competitors being compared
  • Honest differentiators (where your product is genuinely better, where it is not)
  • Customer quotes or reviews that reflect why people switch to you
  • The target keyword(s) and their search volume if known
  • Whether the goal is primarily SEO, sales enablement, or both
  • Any similar pages that exist (on your site or a competitor's) that you want to learn from or beat

Format 1: Singular Alternative Page

Target Query Pattern

"[CompetitorProduct] alternative for [use case or persona]" "[CompetitorProduct] alternative"

Who This Page Serves

Someone who has decided they do not want to use a specific product but has not yet decided what to use instead. They are looking for one credible option that solves the problem the competitor was not solving for them.

Page Structure

Opening paragraph: Acknowledge why someone might be looking for an alternative. This is not about attacking the competitor. It is about naming the specific friction people experience that leads them to search. Use language from actual reviews of the competitor.

Why people switch section: Two to four specific reasons people leave the competitor, grounded in observable evidence (review quotes, known product limitations). Write these as reader pain points, not competitor attacks. "If you've found yourself frustrated by X" is more effective and more credible than "[Competitor] is bad at X."

Who [Your Product] is for: Be specific about who your product serves best. Do not claim to be better for everyone. Name the use case, the company size, the role, or the workflow where you win clearly.

Head-to-head comparison: A table or structured section comparing the two products on the dimensions that matter most to buyers in this category. The dimensions you choose shape the narrative. Choose dimensions where your product competes well, but do not exclude dimensions where the competitor is stronger. Readers trust balanced comparisons more than one-sided ones.

Social proof: Two to three quotes from customers who switched from this competitor. The quotes should explain what changed and why it mattered.

Honest trade-offs: A short section that names when the competitor might be the better choice. This sounds counterintuitive, but it is the element that makes the page feel trustworthy. A comparison page that acknowledges no trade-offs reads like a press release and gets ignored.

CTA: A specific next step. Usually a trial, a demo request, or a side-by-side feature comparison tool.

Length

800 to 1,500 words for a singular alternative page is typical. Enough to be thorough, not enough to lose the reader.


Format 2: Plural Alternatives Page

Target Query Pattern

"Best [CompetitorProduct] alternatives" "[CompetitorProduct] alternatives in [Year]" "Top [CompetitorProduct] alternatives"

Who This Page Serves

Someone who has decided to leave a specific product but wants to see the full landscape before committing. They are doing comparative research and want a trusted curator.

Page Structure

Opening: Briefly explain the context. Why do people look for alternatives to this product? What are the most common reasons? Keep it to two or three sentences.

Criteria for ranking: Briefly explain how you evaluated the alternatives. What factors did you use? (Ease of use, pricing, specific features, support quality, etc.) This makes the list feel curated rather than arbitrary.

The alternatives: List five to eight alternatives. For each one, write:

  • One sentence on what the product is
  • Two or three sentences on who it is best for and why
  • A note on pricing structure
  • One strength and one limitation (the limitation is what makes you credible)
  • Where it fits in the comparison (best for small teams, best for enterprise, best free option, etc.)

Your product in the list: Include your own product in the list. Place it strategically, not always first. If you put yourself first, readers assume bias. Third or fourth position with the strongest write-up is often more effective. Write about yourself with the same structure and tone as the others. Do not make your entry three times longer or more effusive than the others.

Summary section: A short paragraph helping the reader decide. Something like "If you're a small team that needs X, look at [Option A]. If you're a larger organization that needs Y, look at [Option B]. If [specific situation], [Your Product] is designed for exactly that."

CTA: A trial or comparison page link. At this stage in the funnel, readers have not chosen you yet. Make it easy to explore further.

Length

1,500 to 3,000 words is typical. Each alternative needs enough depth to be useful. Thin write-ups feel like you copied the list from somewhere else.

SEO Note

Update the year in the title and the content annually. "Best [Product] alternatives in 2025" will outrank "Best [Product] alternatives in 2023" for the same query, and fresh content signals relevance to search engines.


Format 3: You vs Competitor Page

Target Query Pattern

"[Your Product] vs [Competitor]" "[Competitor] vs [Your Product]" "[Your Product] or [Competitor]"

Who This Page Serves

Someone who has narrowed their evaluation to two specific tools. They want to know the decisive differences. They are close to a decision.

Page Structure

Opening: Name the comparison directly. Acknowledge that both products solve similar problems but for different people. One or two sentences maximum.

At a glance comparison: A table covering six to ten dimensions. Choose dimensions that matter to buyers in your category. Common dimensions: pricing, ease of setup, integrations, customer support model, key features, best suited for, free trial availability. Fill in both columns honestly.

Who [Competitor] is best for: Write two to four sentences on the specific person or use case where the competitor wins. This is not a concession. It is an act of positioning. By naming who the competitor is best for, you implicitly define who they are not best for, which leads naturally to your next section.

Who [Your Product] is best for: Write two to four sentences on the specific person or use case where you win. Connect this directly to the frustrations or gaps you named in the competitor's section.

Detailed comparison by dimension: Go deeper on three to five dimensions where the comparison is most nuanced. A table row can only say so much. For the dimensions that matter most to your buyer, write a paragraph explaining the difference and why it matters.

What customers who switched say: Two to four quotes from customers who evaluated both and chose you. The quotes should explain the decision, not just endorse your product.

FAQ section: Answer the five to seven questions people actually ask when comparing these two products. ("Is [Product] more expensive than [Competitor]?" "Can I migrate my data from [Competitor]?" "Which is better for [specific use case]?") FAQs improve SEO performance and address real buyer concerns.

CTA: A trial or demo request with a message that acknowledges they are comparing options.

Tone

Stay factual. Do not mock or belittle the competitor. Write the competitor section the same way you would want someone to write about you if they were making an honest comparison. Readers respect objectivity and distrust anything that reads like propaganda.

Length

1,200 to 2,500 words is typical for a direct comparison page. The comparison table plus three to four written sections plus FAQ is usually the right volume.


Format 4: Competitor vs Competitor Page

Target Query Pattern

"[Competitor A] vs [Competitor B]"

Who This Page Serves

Someone early in their research who has not yet heard of your product. They are comparing two options that do not include you. A page that answers their question credibly, then introduces your product as a third option, can capture this early-stage intent.

Why This Format Works

When someone searches "[Tool A] vs [Tool B]," they are probably not satisfied with either tool yet. They are exploring. A page that answers the question they searched for, earns their trust through objectivity, and then introduces your product as an alternative worth considering captures attention at the right moment.

The key is that the first 70 to 80 percent of the page must genuinely serve the reader's original question. If the page feels like a setup to sell them something, it will not rank and it will not convert.

Page Structure

Opening: Acknowledge what both tools are and what they share in common. Two to three sentences.

At a glance table: A side-by-side comparison of both tools on relevant dimensions. Same structure as Format 3.

Where [Competitor A] wins: Two to three genuine strengths. Specific and honest.

Where [Competitor B] wins: Same structure for the second competitor.

Common frustrations with both: A short section where you name the gaps that neither competitor addresses well. This is the bridge to introducing your product. The frustrations should be real and grounded in review data.

Consider [Your Product] if...: Introduce your product as the alternative for specific situations the reader might be in. This section should be shorter than the competitor sections. It is a recommendation, not a pitch.

CTA: A simple way to learn more or start a trial.

Tone

Neutral and informative throughout the main comparison. Your product introduction should feel like a helpful recommendation, not a bait-and-switch. If readers feel tricked, they leave. If they feel helped, they click.

Length

1,000 to 2,000 words. The comparison itself should be thorough. Your product section should be brief but specific.


Keyword Strategy for Comparison Pages

Each page targets a specific keyword or cluster. The keyword drives the URL structure, the title tag, the H1, and the content focus.

URL patterns:

  • yourproduct.com/alternatives/competitor-name
  • yourproduct.com/compare/yourproduct-vs-competitor
  • yourproduct.com/blog/best-competitor-alternatives (if the page lives in the blog)

Internal linking: Each comparison or alternative page should link to related pages. The "[Competitor] alternative" page should link to your product's relevant feature page. The "vs" page should link to your pricing page and your customer case studies.

The canonical URL for each page should be the page itself, not a category page that aggregates comparisons.

Update each page when:

  • Either product releases a significant feature change
  • Pricing changes
  • The competitor raises funding or changes direction
  • Search volumes for the primary keyword change significantly

What Not to Do on Comparison Pages

Making claims you cannot support: "We are the best in the market" needs proof. "We are faster to set up than [Competitor], based on our average time-to-value of 4 hours vs the industry average of 14" is a claim.

Writing the competitor section as an attack: It reads as insecure and makes readers trust you less. Present both products fairly. Let the reader draw their own conclusion.

Hiding trade-offs: Every product has trade-offs. Pages that pretend otherwise damage credibility with readers who do even basic research.

Targeting queries with no volume: Before building comparison pages, verify that people are actually searching for the comparison. Building a page for "[Your Product] vs [Tool Nobody Searches For]" is a low-return investment.


Output Format

For any comparison page, deliver:

  • A suggested title and meta description (optimized for the target keyword)
  • The full page content organized by section with clear headings
  • A comparison table formatted for easy editing
  • A brief note on the primary keyword being targeted and why the structure serves it

If the user has not provided enough information about their product's differentiators, ask before writing. A comparison page that is vague about why your product wins does not serve anyone.

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.