메뉴
競合比較ページ・代替製品ページをSEO・営業資料向けに作成するスキル。 「競合比較ページを作って」「代替ツールのページ」「vs ページ」「〇〇 vs △△」「alternative page」等のリクエストで発動。 単数alternative、複数alternatives、自社vs競合、競合同士比較の4フォーマットに対応。
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Slack検索・TODO抽出・タスク管理を行うサブエージェント。 複数データソースからタスクを抽出し、優先順位付けを行う。 「Slackを検索」「タスクを抽出」「TODO確認」「メンション確認」等のリクエストで発動。
ai-agent-campのレッスンをCodexで開始・進行するスキル。 「レッスン開始」「次のレッスン」「start-0-1を始めたい」「Codexでレッスン」「スラッシュコマンドのレッスン」等のリクエストで発動。
YouTube/マルチプラットフォーム動画からAIでハイライトを抽出し、 バイリンガル字幕付きクリップを自動生成するスキル。 「動画からクリップを切り出して」「ハイライトを抽出」「字幕付きクリップ」等で発動。
メールとSlackから返信すべき項目・タスクを抽出する統合型スキル。 Gemini 3.0 Flashで文脈判定し、優先度と返信ドラフトを生成。 「受信箱チェック」「TODO確認」「返信すべきメッセージ」「メール確認」等のリクエストで発動。
コンテンツの投稿・配信実行スキル。Typefully経由のX投稿、画像アップロード、 投稿スケジューリングを行う。 「投稿して」「スケジュール設定」「Typefullyに下書き」等で発動。
CSVファイルの行数・列数の取得、データ型推定、欠損値検出、数値列の統計情報を出力するスキル。 「CSVを分析して」「CSVの中身を確認」「データの概要を見せて」等のリクエストで発動。
| name | competitor-alternatives |
| version | 1.0.0 |
| description | 競合比較ページ・代替製品ページをSEO・営業資料向けに作成するスキル。 「競合比較ページを作って」「代替ツールのページ」「vs ページ」「〇〇 vs △△」「alternative page」等のリクエストで発動。 単数alternative、複数alternatives、自社vs競合、競合同士比較の4フォーマットに対応。 |
| triggers | ["competitor-alternatives","競合比較","代替ツール","vs ページ","alternative page","競合分析ページ","comparison page"] |
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.
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:
Your Product
Competitive Landscape
Goals
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:
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:
Important: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.
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:
Search intent: User comparing two competitors (not you directly)
URL pattern: /compare/[competitor-a]-vs-[competitor-b]
Page structure:
Why this works: Captures search traffic for competitor terms, positions you as knowledgeable.
Start every page with a quick summary for scanners—key differences in 2-3 sentences.
Go beyond tables. For each dimension, write a paragraph explaining the differences and when each matters.
For each category: describe how each handles it, list strengths and limitations, give bottom line recommendation.
Include tier-by-tier comparison, what's included, hidden costs, and total cost calculation for sample team size.
Be explicit about ideal customer for each option. Honest recommendations build trust.
Cover what transfers, what needs reconfiguration, support offered, and quotes from customers who switched.
For detailed templates: See references/templates.md
Create a single source of truth for each competitor with:
For data structure and examples: See references/content-architecture.md
For each competitor, gather:
| 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] |
Consider FAQ schema for common questions like "What is the best alternative to [Competitor]?"
Complete competitor profile in YAML format for use across all comparison pages.
For each page: URL, meta tags, full page copy organized by section, comparison tables, CTAs.
Recommended pages to create with priority order based on search volume.
