Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计提醒

alternatives-page-generator替代页面生成器

Agent Skill

alternatives-page-generator 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

4,363

周安装

180

GitHub Stars

公开资料未说明

下载量

1,426
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:alternatives-page-generator(替代页面生成器)
来源仓库:https://github.com/kostja94/alternatives-page-generator
安装命令:
openclaw skills install alternatives-page-generator
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install alternatives-page-generator

简介

alternatives-page-generator 自动生成产品或服务替代方案的比较页面,支持博客文章与落地页格式。

  • 输入核心需求关键词,输出包含优缺点对比、价格区间与使用场景的结构化内容。
  • 可指定目标受众(如企业用户、个人消费者)以调整文案语气与技术参数权重。
  • 数据来源依赖公开信息,若涉及竞品商标或专利需谨慎处理表述方式。
  • 生成页面建议添加免责声明,明确说明非官方评测结果仅供参考。

SKILL.md

name
alternatives-page-generator
description
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
metadata
version
1.2.1

Pages: Alternatives / Compare

Guides alternatives and comparison content that target "X alternatives" and "X vs Y" search intent. Purpose: Intercept competitor brand traffic—organic (SEO) and paid (brand keyword ads). High-intent, bottom-of-funnel; users searching alternatives are ready to switch. Content format: Standalone page (/alternatives, /alternatives-to-notion) or blog article (/blog/notion-alternatives). Same structure; blog builds topical authority.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Purpose & Keywords

GoalUse
SEORank for "[Competitor] alternatives," "alternatives to [Competitor]," "[Competitor] vs [You]"
PPCBid on competitor brand + "alternative"/"vs"; send to alternatives landing page
IntentHigh-intent; short sales cycle; users already understand the category

Keyword patterns: alternatives, alternative, vs, comparison, compare, "best [X] alternatives." Include name variants (e.g., "SuccessBox" and "Success Box") in metadata.

Competitor Types

TypeDescriptionExample
DirectObvious rivalsFreshBooks vs QuickBooks
BundlersLarge platforms; users want lighter/cheaperSalesforce, HubSpot → "cheaper Salesforce for SMB"
IndirectSame problem, different solution"Spreadsheet alternative" for accounting software

Target all three for long-tail growth; don't only target the biggest competitor.

Content Format: Page vs Blog Article

FormatPathUse
Standalone page/alternatives, /alternatives-to-[competitor]Dedicated hub; strong for your own product as alternative; preferred for paid ads (competitor brand keyword ads)
Blog article/blog/[product]-alternatives, /blog/best-[x]-alternativesListicle format; common for affiliate, challenger brands; builds topical authority; SEO/organic only

Both formats use the same structure (quick verdict, comparison table, individual reviews, FAQ). For competitor brand keyword ads (Google Ads, etc.): use a dedicated landing page, not a blog. Users searching competitor brands expect direct alternatives; a blog increases bounce; a comparison page matches intent and converts better. Blog is for organic traffic and topical authority.

URL Structure

  • Hub: /alternatives
  • Per-competitor: /alternatives-to-[competitor] or /[competitor]-alternative
  • Short, keyword-rich, crawlable; no keyword stuffing

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, competitors, and differentiators.

Identify:

  1. Format: Standalone page vs. blog article; single hub vs. per-competitor pages
  2. Competitors: Who to include; avoid over-promoting direct rivals
  3. Primary goal: Sign up, trial, demo; position as fair comparison
  4. Tone: Objective, helpful; avoid disparaging competitors

Page / Article Structure

SectionPurpose
Headline"Best [Product Category] Alternatives in [Year]" or "[Product] vs [Competitor]"; plain promise, avoid cute titles
Problem-focused introEmpathy for pain; validate why they're searching; tease the payoff
Quick verdict5–8 lines above the fold: who it's for, top picks, decision shortcut
Pros/cons of originalBuild trust; acknowledge why someone might leave; who should still keep it
Comparison tablePlace early, not hidden; 4–6 columns (best for, price, ease, key limit); HTML table (not image)—required for AEO/GEO; scannable
Alternatives list6–10 picks; each with "best for" label, proof, tradeoff, pricing snapshot
MigrationLink to migration-page if applicable
FAQ"Is X better than Y?"; "Can I migrate from X?"; pricing, trials
CTATry free, start trial, book demo; one CTA above fold, one near end

Best Practices

SEO

  • Intent: Commercial; "alternatives to X," "X vs Y," "best X"
  • Title: "[Product] Alternatives: Top [N] Options Compared | [Your Product]" or "Top [Competitor] Alternatives for [Year]: Better & Cheaper"; under 60 chars
  • Meta: Lead with pain point or question; weave keyword early; end with benefit; max 160 chars
  • Content: 1500+ words for alternatives hub; 800+ for single comparison
  • Internal links: Link to features, pricing, migration, use cases

Fairness & Trust

  • Objective tone: Acknowledge competitor strengths; avoid FUD
  • Transparent criteria: Explain how you compare (features, pricing, use case)
  • Update regularly: Pricing and features change; date the comparison
  • Verifiable claims: Link to pricing pages, docs; cite sources; add "as of [date]" for prices

Conversion

  • Soft sell: Position your product as one option; let value speak
  • Migration CTA: "Switch in minutes" if migration is easy
  • Social proof: Customer quotes from switchers

AEO / GEO (AI Search)

  • HTML tables: Use plain HTML for comparison tables; AI engines parse structured data; avoid images or fancy JS sliders
  • Structured data: Objective entity mappings; bullets over prose for scannability; see entity-seo
  • Third-party validation: G2, niche blogs mentioning you as alternative help AI cite you

Brand Keyword Ads (PPC)

  • Use case: Bid on "[Competitor] alternative," "[Competitor] vs [You]" when allowed by platform
  • Landing page: Use a dedicated alternatives/comparison page, not a blog article. High-intent users expect direct alternatives; blog increases bounce. See google-ads Competitor Brand Keywords.
  • Ad-to-page alignment: H1 mirrors search intent ("X vs [You]"); comparison table; one-line differentiator; strong CTA; see landing-page-generator, paid-ads-strategy

Programmatic SEO (Scale)

  • When: 50+ competitors; can't write manually
  • Data schema: Price, key features, support level; store in API or headless CMS
  • Template: One structure; populate per competitor; verify data quarterly (pricing changes)
  • Name variants: Include "SuccessBox" and "Success Box" in metadata

Measurement

MetricPurpose
Assisted conversionsUser may convert later; attribution
Bounce + pricing clickBounce to pricing = intent signal
GEO share of voiceSearch "[Competitor] alternative" on Perplexity; are you cited?
CTA clicks"Switch Now" button performance

Output Format

  • Competitor list (Direct, Bundlers, Indirect)
  • Keyword list (alternatives, vs, comparison; name variants)
  • Headline and problem-focused intro
  • Comparison structure (table columns, criteria; HTML table)
  • Per-competitor summary (2–3 sentences each)
  • Your product positioning
  • Internal links (migration, features, pricing)
  • SEO metadata (title, meta; under 60/160 chars)
  • PPC (if applicable): ad-to-page alignment

Related Skills

  • article-page-generator: Alternatives as blog listicle; same structure, different path
  • migration-page-generator: Migration guides for switchers; link from alternatives
  • landing-page-generator: When alternatives page is used for paid ads (PPC), apply LP principles; ad-to-page alignment
  • google-ads: Competitor brand keyword campaigns; LP (not blog) for competitor ads; see Competitor Brand Keywords section
  • paid-ads-strategy: When to use paid ads; ad-to-page alignment; channel selection; competitor brand bidding
  • programmatic-seo: Scale alternatives pages across 50+ competitors; template + data
  • features-page-generator: Feature comparison content
  • pricing-page-generator: Pricing comparison
  • customer-stories-page-generator: Switcher testimonials
  • entity-seo: Entity mappings; Organization, Person; GEO citation

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

85.82%
按下载量换算1,224

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills