メニュー
Map SEO market leaders, winning content themes, keyword coverage, backlinks, and strategic gaps.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | competitive-landscape |
| description | Map SEO market leaders, winning content themes, keyword coverage, backlinks, and strategic gaps. |
Answer: "Who is winning this SEO market, what content is working for them, and where are the openings?"
Use this when the user wants a market-level view across several competitors. For a deep dive on one domain, use competitor-analysis.
projectIdresearch_keywords: discover representative market queries.get_keyword_metrics: validate known query sets with volume, difficulty, intent, and trends.get_serp_results: identify recurring ranking domains across target queries.find_serp_competitors: compare domains competing across supplied keywords; use this before manual SERP counting when a keyword set is available.get_domain_overview: size organic footprint for candidate leaders.get_search_console_performance: when the user's own domain is in the comparison and Search Console is connected, anchor their position with first-party clicks/impressions/CTR rather than third-party estimates.get_ranked_keywords: find exact ranking keywords, URLs, ranks, intents, and SERP result types for leaders.get_backlinks_overview: compare backlink/referring-domain strength where relevant.search_local_businesses, get_local_serp_results, and get_google_business_questions: use for local SEO markets where proximity, Maps rankings, business categories, reviews, or Google Q&A affect who is winning.research_keywords to build 5-10 representative queries.get_keyword_metrics to validate relative demand and difficulty and find_serp_competitors to identify recurring domains at scale.search_local_businesses and get_local_serp_results for the highest-priority location(s) before synthesizing winners. Use get_serp_results as a complement for organic pages, not as the only local evidence.get_serp_results for representative queries when live SERP composition, ranking URLs, or SERP features need inspection. Send at most 10 queries per call.get_domain_overview; default to the top 3-5 domains before expanding.get_ranked_keywords.get_backlinks_overview when backlink authority appears important or the user asks why a domain is winning. Backlinks may be unavailable if the account has not enabled that data; continue with SERP/domain evidence if it fails.Start with the market read:
Then include:
| Domain | Type | Why they matter | Organic footprint | Winning themes | Weakness/gap |
|---|
Add:
Log genuine, recurring repository friction to .agents/PAPERCUTS.md — confusing setup, a flaky repo command or script, a misleading in-repo error, stale generated files, or a non-obvious gotcha that will cost the next contributor time. Also use to review, deduplicate, and resolve existing entries. Gate hard before logging: only friction the repository itself can fix counts. Never log the agent's own sandbox/permission errors, shell-scripting mistakes, transient flakiness, or third-party tool quirks the repo can't change.
Log genuine, recurring repository friction to .agents/PAPERCUTS.md — confusing setup, a flaky repo command or script, a misleading in-repo error, stale generated files, or a non-obvious gotcha that will cost the next contributor time. Also use to review, deduplicate, and resolve existing entries. Gate hard before logging: only friction the repository itself can fix counts. Never log the agent's own sandbox/permission errors, shell-scripting mistakes, transient flakiness, or third-party tool quirks the repo can't change.
Evaluate verified findings from merge-ready, Greptile, pull-request, CI, security, billing, and other code reviews, then promote durable review gaps into the version-controlled .greptile configuration. Use when a review uncovers a recurring or high-risk repository invariant that Greptile does not capture, when Greptile repeatedly produces a false positive, or when asked to audit or update OpenSEO's Greptile rules and context.
Take a branch from "code exists (or is about to)" to "ready for Ben's final review" — multi-axis subagent review with verified findings, fixes, ci:check, checkpoint commits, and an updated PR. Use whenever the user says a feature/fix/branch should be "merge ready", asks to get changes ready for review, or appends this to a build request ("build X and make it merge-ready").
Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.
Take a branch from "code exists (or is about to)" to "ready for Ben's final review" — multi-axis subagent review with verified findings, fixes, ci:check, checkpoint commits, and an updated PR. Use whenever the user says a feature/fix/branch should be "merge ready", asks to get changes ready for review, or appends this to a build request ("build X and make it merge-ready").