ワンクリックで
link-prospecting
Find link prospects, discover contact paths, and draft outreach from SERPs and backlink signals.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Find link prospects, discover contact paths, and draft outreach from SERPs and backlink signals.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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").
| name | link-prospecting |
| description | Find link prospects, discover contact paths, and draft outreach from SERPs and backlink signals. |
Find realistic pages, sites, and authors that might reference the user's page, product, study, guide, or tool. Use OpenSEO for prospect discovery, then use available web/search/browser tools for contact discovery.
projectIdget_serp_results: find ranking articles, listicles, resource pages, comparisons, and topical publishers.get_backlinks_overview: inspect competitor domain or page backlink/referring-domain patterns.get_domain_overview: qualify important prospect domains.get_ranked_keywords: understand what a prospect or competitor ranks for when topical fit matters.search_local_businesses and get_local_serp_results: use for local SEO link prospecting when nearby businesses, local competitors, or Maps/category signals can reveal partnership targets.research_keywords: expand prospecting queries.After OpenSEO identifies good prospects, use available non-OpenSEO browsing or search tools for public contact discovery. Depending on the client, this may be web search, page fetches, browser automation, or a search API.
Look for:
Person, Organization, sameAs, or emailOnly record contact details that were actually found. Include the source URL for any email, profile, or contact form.
Build queries from the asset/topic:
<topic> resourcesbest <category> tools<competitor> alternatives<topic> statistics<topic> guide<topic> examples<topic> templates<topic> software<topic> for <audience>Use get_serp_results in batches for the most relevant patterns. Send at most 10 queries per call.
get_serp_results for those queries.get_backlinks_overview for the strongest competitor domains or pages first. Continue without backlink evidence if it is unavailable.search_local_businesses and get_local_serp_results around priority locations to identify nearby competitors, categories, and local SERP evidence before searching for local chambers, associations, campus resources, community pages, and directories.Start with:
Then include:
| Prospect URL | Site/domain | Source | Relevance | Suggested angle | Contact path | Priority |
|---|
Then provide 2-3 reusable outreach drafts: