跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
营销与销售

competitor-alternatives

When the user wants to create public competitor comparison or alternative pages for SEO and evaluators. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For battle cards and other internal sales material, see sales-enablement.

mia-ppp · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add mia-ppp/PMM-Skills --skill competitor-alternatives

技能说明


name: competitor-alternatives description: "When the user wants to create public competitor comparison or alternative pages for SEO and evaluators. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For battle cards and other internal sales material, see sales-enablement." metadata: version: 1.1.0

Competitor & Alternative Pages

Use the company SSOT when present: follow ../_shared/ssot-consumption.md and the project manifest to load only relevant approved context. Preserve covered strategic meaning while keeping this skill’s existing scope and frameworks.

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.

Before Starting

Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Only ask for what it does not cover.

Load the shared reference: read ../_shared/evidence-gaps.md (relative to this skill's folder). Label every claim, finding, and number Sourced, Assumed, or Gap.

Scope: this skill writes public pages that prospects and searchers read. If the user wants a battle card or other internal sales material, say in one line that sales-enablement covers it and hand off. Do not ask which they want.

Useful inputs (ask only if missing and it would change the page):

  1. Your product: value proposition, differentiators, best-fit customer, pricing, honest weaknesses.
  2. The competitor: who they are, how they position, what switchers complain about.
  3. Goal: SEO capture, converting competitor users, or supporting sales conversations.

If an accepted market-entry brief or canonical SSOT already establishes the target segment, use that segment. Do not select a different ICP inside the page workflow. Flag conflicts with canonical SSOT for review through ssot-context-loop.

Assess decision-specific readiness using ../_shared/context-establishment.md. If no accepted target exists, route market selection to market-entry-brief or context establishment to product-marketing-context. Do not score/select an ICP inside page production. An explicit exploratory audience may support a bounded page draft, preserving its assumption, risk, scope and validation trigger. Read competitor-profiling artifacts before requesting targeted verification. Hold only unsupported consequential claims/choices; continue independent page structure or supported sections. Missing evidence uses Gap placeholders with provable fallbacks, not uncited public knowledge or assumed capabilities. End with the consequential gaps/owners and separate approval dependencies.

Never invent stats, customer quotes, or competitor weaknesses. Proof you do not have is a [Gap: ...] placeholder. A page with open Gaps is labeled "Draft, not publish-ready" at the top. A page that is mostly placeholders is not a draft.


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
  • competitor-profiling owns reusable research; page data is a derived view

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 ho
阅读完整来源 ↗