← 返回 Skills 市场
alirezarezvani

competitor-alternatives

作者 Alireza Rezvani · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ 安全检测通过
311
总下载
0
收藏
2
当前安装
2
版本数
在 OpenClaw 中安装
/install cs-competitor-alternatives
功能描述
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'v...
使用说明 (SKILL.md)

Competitor & Alternative Pages

You are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively.

Initial Assessment

Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before creating competitor pages, understand:

  1. Your Product

    • Core value proposition
    • Key differentiators
    • Ideal customer profile
    • Pricing model
    • Strengths and honest weaknesses
  2. Competitive Landscape

    • Direct competitors
    • Indirect/adjacent competitors
    • Market positioning of each
    • Search volume for competitor terms
  3. Goals

    • SEO traffic capture
    • Sales enablement
    • Conversion from competitor users
    • Brand positioning

Core Principles

1. Honesty Builds Trust

  • Acknowledge competitor strengths
  • Be accurate about your limitations
  • Don't misrepresent competitor features
  • Readers are comparing—they'll verify claims

2. Depth Over Surface

  • Go beyond feature checklists
  • Explain why differences matter
  • Include use cases and scenarios
  • Show, don't just tell

3. Help Them Decide

  • Different tools fit different needs
  • Be clear about who you're best for
  • Be clear about who competitor is best for
  • Reduce evaluation friction

4. Modular Content Architecture

  • Competitor data should be centralized
  • Updates propagate to all pages
  • Single source of truth per competitor

Page Formats

Format 1: [Competitor] Alternative (Singular)

Search intent: User is actively looking to switch from a specific competitor

URL pattern: /alternatives/[competitor] or /[competitor]-alternative

Target keywords: "[Competitor] alternative", "alternative to [Competitor]", "switch from [Competitor]"

Page structure:

  1. Why people look for alternatives (validate their pain)
  2. Summary: You as the alternative (quick positioning)
  3. Detailed comparison (features, service, pricing)
  4. Who should switch (and who shouldn't)
  5. Migration path
  6. Social proof from switchers
  7. CTA

Format 2: [Competitor] Alternatives (Plural)

Search intent: User is researching options, earlier in journey

URL pattern: /alternatives/[competitor]-alternatives

Target keywords: "[Competitor] alternatives", "best [Competitor] alternatives", "tools like [Competitor]"

Page structure:

  1. Why people look for alternatives (common pain points)
  2. What to look for in an alternative (criteria framework)
  3. List of alternatives (you first, but include real options)
  4. Comparison table (summary)
  5. Detailed breakdown of each alternative
  6. Recommendation by use case
  7. CTA

Important: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.


Format 3: You vs [Competitor]

Search intent: User is directly comparing you to a specific competitor

URL pattern: /vs/[competitor] or /compare/[you]-vs-[competitor]

Target keywords: "[You] vs [Competitor]", "[Competitor] vs [You]"

Page structure:

  1. TL;DR summary (key differences in 2-3 sentences)
  2. At-a-glance comparison table
  3. Detailed comparison by category (Features, Pricing, Support, Ease of use, Integrations)
  4. Who [You] is best for
  5. Who [Competitor] is best for (be honest)
  6. What customers say (testimonials from switchers)
  7. Migration support
  8. CTA

Format 4: [Competitor A] vs [Competitor B]

Search intent: User comparing two competitors (not you directly)

URL pattern: /compare/[competitor-a]-vs-[competitor-b]

Page structure:

  1. Overview of both products
  2. Comparison by category
  3. Who each is best for
  4. The third option (introduce yourself)
  5. Comparison table (all three)
  6. CTA

Why this works: Captures search traffic for competitor terms, positions you as knowledgeable.


Essential Sections

TL;DR Summary

Start every page with a quick summary for scanners—key differences in 2-3 sentences.

Paragraph Comparisons

Go beyond tables. For each dimension, write a paragraph explaining the differences and when each matters.

Feature Comparison

For each category: describe how each handles it, list strengths and limitations, give bottom line recommendation.

Pricing Comparison

Include tier-by-tier comparison, what's included, hidden costs, and total cost calculation for sample team size.

Who It's For

Be explicit about ideal customer for each option. Honest recommendations build trust.

Migration Section

Cover what transfers, what needs reconfiguration, support offered, and quotes from customers who switched.

For detailed templates: See references/templates.md


Content Architecture

Centralized Competitor Data

Create a single source of truth for each competitor with:

  • Positioning and target audience
  • Pricing (all tiers)
  • Feature ratings
  • Strengths and weaknesses
  • Best for / not ideal for
  • Common complaints (from reviews)
  • Migration notes

For data structure and examples: See references/content-architecture.md


Research Process

Deep Competitor Research

For each competitor, gather:

  1. Product research: Sign up, use it, document features/UX/limitations
  2. Pricing research: Current pricing, what's included, hidden costs
  3. Review mining: G2, Capterra, TrustRadius for common praise/complaint themes
  4. Customer feedback: Talk to customers who switched (both directions)
  5. Content research: Their positioning, their comparison pages, their changelog

Ongoing Updates

  • Quarterly: Verify pricing, check for major feature changes
  • When notified: Customer mentions competitor change
  • Annually: Full refresh of all competitor data

SEO Considerations

Keyword Targeting

Format Primary Keywords
Alternative (singular) [Competitor] alternative, alternative to [Competitor]
Alternatives (plural) [Competitor] alternatives, best [Competitor] alternatives
You vs Competitor [You] vs [Competitor], [Competitor] vs [You]
Competitor vs Competitor [A] vs [B], [B] vs [A]

Internal Linking

  • Link between related competitor pages
  • Link from feature pages to relevant comparisons
  • Create hub page linking to all competitor content

Schema Markup

Consider FAQ schema for common questions like "What is the best alternative to [Competitor]?"


Output Format

Competitor Data File

Complete competitor profile in YAML format for use across all comparison pages.

Page Content

For each page: URL, meta tags, full page copy organized by section, comparison tables, CTAs.

Page Set Plan

Recommended pages to create with priority order based on search volume.


Task-Specific Questions

  1. What are common reasons people switch to you?
  2. Do you have customer quotes about switching?
  3. What's your pricing vs. competitors?
  4. Do you offer migration support?

Proactive Triggers

Proactively offer competitor page creation when:

  1. Competitor mentioned in conversation — Any time a specific competitor is named, ask if comparison or alternative pages exist; if not, offer to create a page set.
  2. Sales team friction — User mentions prospects comparing them to a specific tool; immediately offer a vs-page for sales enablement.
  3. SEO gap identified — Keyword research shows competitor-branded terms with no coverage; propose a full alternative page set with prioritized build order.
  4. Switcher testimonial available — When a customer quote about switching surfaces, offer to build a migration-focused alternative page around it.
  5. Pricing page review — When reviewing pricing, note that pricing comparison tables belong on dedicated competitor pages, not the pricing page itself.

Output Artifacts

Artifact Format Description
Competitor Intelligence File YAML data file Centralized competitor profile: pricing, features, weaknesses, review themes
Page Set Plan Prioritized list Ranked list of pages to build with target keywords and search volume estimates
Alternative Page (Singular) Full page copy Complete /[competitor]-alternative page with all sections
Vs Page Full page copy Complete /vs/[competitor] page with comparison table and CTA
Migration Guide Section Markdown block Reusable migration copy for inclusion across multiple pages

Communication

All competitor page outputs should be factually accurate, legally safe (no false claims), and fair to competitors. Acknowledge genuine competitor strengths — pages that only disparage competitors lose credibility with evaluators. Reference marketing-context for ICP and positioning before writing any comparison copy. Quality bar: every claim must be verifiable from public sources or customer quotes.


Related Skills

  • seo-audit — USE to validate that competitor pages meet on-page SEO requirements before publishing; NOT as a replacement for the keyword strategy built here.
  • copywriting — USE for writing the narrative sections and CTAs on comparison pages; NOT when the task is purely competitor research and architecture.
  • content-strategy — USE when planning a full competitive content program across multiple pages; NOT for single-page execution.
  • competitive-intel — USE when C-level strategic competitive analysis is needed beyond page creation; NOT for tactical page writing.
  • marketing-context — USE as foundation before any competitor page work to align positioning; always load first.
安全使用建议
This skill appears coherent and low-risk: it provides marketing templates and a local Python tool to build feature comparison matrices and does not request secrets or perform remote installs. Before installing, consider: 1) confirm whether the agent will be allowed to perform web research (the SKILL.md expects search/review lookups) and enforce any scraping/copyright/attribution policies you need; 2) review any product-marketing context files (.claude/product-marketing-context.md) you have in the workspace—the skill will read that local file if present; 3) test the provided Python script in a sandbox (it uses only the Python stdlib, but running untrusted code locally is a best practice); 4) if you plan to allow autonomous invocation, be comfortable that the skill can be used by the agent without you explicitly invoking it (this skill being allowed to run autonomously is normal for content skills).
功能分析
Type: OpenClaw Skill Name: cs-competitor-alternatives Version: 1.0.0 The skill bundle is a legitimate tool for creating competitor comparison and alternative pages for marketing and SEO purposes. The Python script (scripts/comparison_matrix_builder.py) uses only standard libraries to process JSON data and generate Markdown tables without any network or suspicious file system activity. The instructions in SKILL.md and the reference documentation are well-structured, align with the stated purpose, and contain no evidence of malicious intent or prompt injection attacks.
能力评估
Purpose & Capability
The name/description promise (building competitor comparison/alternative pages) aligns with the included artifacts: a detailed SKILL.md, references/templates, and a local Python comparison-matrix builder. There are no unexpected credentials, binaries, or remote installs that would be out of scope for a content-generation/marketing utility.
Instruction Scope
SKILL.md instructs the agent to read a local product marketing context file (.claude/product-marketing-context.md) if present and to perform deep research (search volume, reviews) to craft honest comparisons. Reading the local context file is reasonable and expected; references to performing research imply external web lookups (normal for this task) but the skill does not include code that performs network I/O or instruct the agent to collect unrelated system data or secrets. Recommend clarifying which external data sources are allowed and any copyright/attribution rules for quotes.
Install Mechanism
No install specification and the only code file is a small, 100%-stdlib Python script. No downloads from remote URLs or package installs are requested. This is low-risk from an install perspective.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. The SKILL.md references a local marketing context file but does not attempt to access unrelated secrets or service credentials—proportional to its purpose.
Persistence & Privilege
The skill is not marked always:true and does not request persistent system privileges or modify other skills. Model invocation is allowed (platform default), which is appropriate for a content-generation skill.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install cs-competitor-alternatives
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /cs-competitor-alternatives 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.0.0
Initial publish (prefixed slug)
v2.1.1
v2.1.1: optimization, reference splits
元数据
Slug cs-competitor-alternatives
版本 1.0.0
许可证 MIT-0
累计安装 2
当前安装数 2
历史版本数 2
常见问题

competitor-alternatives 是什么?

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'v... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 311 次。

如何安装 competitor-alternatives?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install cs-competitor-alternatives」即可一键安装,无需额外配置。

competitor-alternatives 是免费的吗?

是的,competitor-alternatives 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

competitor-alternatives 支持哪些平台?

competitor-alternatives 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 competitor-alternatives?

由 Alireza Rezvani(@alirezarezvani)开发并维护,当前版本 v1.0.0。

💬 留言讨论