link-prospecting
Skill56 starsChanged 38 days agoMITView on GitHub
Find link-building and digital-PR opportunities via the OpenGSC MCP: mine competitor backlink mentions (Link Monitor), spot multi-linker domains, and check the site's own backlink health.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- foverse/seoversetheir own version, first seen Nov 8, 2026
- winsley-jeune/harborrank-skillstheir own version, first seen Oct 27, 2026
- jwuthri-cloud/Tracely-aitheir own version, first seen Oct 20, 2026
- petera2c/simple-tabletheir own version, first seen Oct 8, 2026
- VladSez/easy-invoice-pdftheir own version, first seen Oct 8, 2026
- every-app/open-seotheir own version, first seen Oct 8, 2026
Used with
Projects with it also use local-seo and seo-report.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
huiferSkilllocal-seo
本地 SEO 分析和优化专家。自动检测项目是否需要本地 SEO,分析 NAP(Name, Address, Phone)一致性、本地关键词优化、Google Business Profile (GBP) 优化和本地结构化数据生成。提供本地商家搜索引擎排名优化建议,包括 NAP 标准化、本地关键词策略、GBP 完整性检查、评论策略、地图嵌入和本地 SEO 审计。
Also in 5 projects that use this
01claudingSkillseo-report
SEO reporting and analytics dashboard generation. Creates weekly digests, monthly performance reports, quarterly strategy reviews, and real-time dashboard templates. Use when user says "SEO report", "weekly digest", "monthly report", "dashboard", "SEO metrics", "performance summary".
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- every-app/open-seo★ 27ksame name
- Jwuthri/Tracely-ai★ 1.3ksame name
- VladSez/easy-invoice-pdf★ 1.1ksame name
- jwuthri-cloud/Tracely-ai★ 979same name
- petera2c/simple-table★ 233same name
- foverse/seoverse★ 4same name
- kid7st/agenticseo★ 2same name
- ventra-rocket/EchoSEO★ 2same name
- winsley-jeune/harborrank-skills★ 2same name
- ictlondon/kraftskills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- aeo-visibility-reviewSkill
- drops-researchSkill
- gsc-performance-reviewSkill
- keyword-researchSkill
- page-optimizationSkill
- seo-productionSkill
- site-triageSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Call get_link_mentions. If it returns a "no data yet" note, stop and tell the user to add brands and run a pull under SEO Tools → Link …
- Very specific: line 27
If the user's site is known, call get_backlinks and list dead (alive: false) links as reclamation targets — the cheapest wins in link …
- Distinctive: line 38
Do not fabricate DR values or mentions.
- Distinctive: line 39
Never suggest paid links or PBNs.
- Distinctive: line 47
Call it before any other tool.
- Distinctive: line 52
Before any PAID tool, check the research log: if the same research ran within the last 30 days, reuse that result and say so instead of …
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
OpenGSC Link Prospecting
Goal
Produce a concrete outreach shortlist: which domains to contact, why they're likely to link, and what content to pitch — grounded in the fresh competitor backlinks the user's Link Monitor has already pulled from Ahrefs.
Required inputs
- Optional: a specific watched brand to focus on, and the user's own site for the backlink-health check.
OpenGSC MCP tools
get_link_mentions: fresh quality backlinks earned by the watched competitor brands +multiLinkerDomains(domains linking to 2+ brands — the highest-probability outreach targets). This is the core tool.get_backlinks: the user's OWN curated backlink inventory with liveness/indexed status — use to spot dead links worth reclaiming.list_sites: resolve the user's site if backlink health is in scope.
Workflow
- Call
get_link_mentions. If it returns a "no data yet" note, stop and tell the user to add brands and run a pull under SEO Tools → Link Monitor. - Prioritize
multiLinkerDomains: a domain that linked to two competitors but not the user is the warmest lead. - From
mentions, infer WHAT earns links in this niche: content types (studies, comparisons, tools), anchor patterns, and the context titles suggest. - If the user's site is known, call
get_backlinksand list dead (alive: false) links as reclamation targets — the cheapest wins in link building. - Build the outreach shortlist with a specific pitch angle per domain.
Output format
- Top 5 outreach targets: domain, DR (from data), which brands it linked, suggested pitch.
- Content/PR ideas the mention data supports (with example source titles as evidence).
- Reclamation list (dead backlinks), if any.
Guardrails
- Do not fabricate DR values or mentions; every claim must trace to a returned row.
- Never suggest paid links or PBNs; keep recommendations white-hat outreach/content.
Site context — read first, free
get_site_context is this skill's step zero. It returns the site's shared memory — business
overview, current goal, positioning, writing preferences, the competitor list, key pages and
the research log — and grounds every decision below in what the operator already told us.
- Call it before any other tool. If it errors or comes back empty, continue without it; never block the workflow on missing context.
- This skill especially needs:
positioning,competitors. If a needed section is empty, do a minimal inline fill — ask the user (or infer from the site and confirm), write it back withupdate_site_context, then continue. Never front-load a full interview. - Before any PAID tool, check the research log: if the same research ran within the last 30 days, reuse that result and say so instead of re-buying it.
- On finish, write back what is durable — new or corrected key pages, competitors the work
revealed, positioning facts the user stated — and append a research-log entry if the
session spent paid units (
appendResearchLog).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

