agentleFS
petera2cpetera2c/simple-table/.agents/skills/link-prospecting/SKILL.md

link-prospecting

Skill233 starsChanged 3 months agoMITView on GitHub

Find link prospects, discover contact paths, and draft outreach from SERPs and backlink signals.

10 other projects use a version of this, 6 of them edited.

Adopted by

Most recently taken up by

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.
  • huiferSkill

    local-seo

    本地 SEO 分析和优化专家。自动检测项目是否需要本地 SEO,分析 NAP(Name, Address, Phone)一致性、本地关键词优化、Google Business Profile (GBP) 优化和本地结构化数据生成。提供本地商家搜索引擎排名优化建议,包括 NAP 标准化、本地关键词策略、GBP 完整性检查、评论策略、地图嵌入和本地 SEO 审计。

    Also in 5 projects that use this

  • 01claudingSkill

    seo-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

The file

We split this skill into the rules it gives an agent

10 rules. 6 are common, 0 are distinctive, and 4 are very specific to this project.

  • 6

    Common

    Most of the 7 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    After OpenSEO identifies good prospects, use available non-OpenSEO browsing or search tools for public contact discovery.

    line 31
  2. Common:

    Only record contact details that were actually found.

    line 44
  3. Very specific:

    Use get_serp_results in batches for the most relevant patterns.

    line 60
  4. Very specific:

    Call get_serp_results for those queries.

    line 66
  5. Very specific:

    If competitors are provided, call get_backlinks_overview for the strongest competitor domains or pages first.

    line 67
  6. Common:

    Keep topical relevance and editorial pages.

    line 70
  7. Common:

    Do not invent email addresses, social handles, or contact names.

    line 103
  8. Very specific:

    Do not say OpenSEO found contact details unless an OpenSEO tool returned them.

    line 104
  9. Common:

    If contact details are not available after a reasonable search, recommend specific discovery steps such as checking the author page, …

    line 105
  10. Common:

    Avoid spammy mass outreach.

    line 106

“Common” is measured: kept by at least 6 in 10 of the 7 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OpenSEO Link Prospecting

Goal

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.

Required inputs

  • projectId
  • User domain or target URL
  • Linkable asset, page, product, study, tool, or topic
  • Optional competitors
  • Optional market/location/language

OpenSEO MCP tools

  • get_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.

Contact discovery tools

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:

  • Author byline pages
  • Contact pages
  • Editorial guidelines
  • About/team pages
  • LinkedIn, X, Bluesky, or other professional profiles
  • Newsletter or publication masthead pages
  • Public email addresses in page HTML or visible page text
  • Structured data such as Person, Organization, sameAs, or email

Only record contact details that were actually found. Include the source URL for any email, profile, or contact form.

Prospecting query patterns

Build queries from the asset/topic:

  • <topic> resources
  • best <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.

Workflow

  1. Clarify the linkable asset and the reason someone would reference it.
  2. Build 5-10 prospecting queries by default.
  3. Call get_serp_results for those queries.
  4. If competitors are provided, call get_backlinks_overview for the strongest competitor domains or pages first. Continue without backlink evidence if it is unavailable.
  5. For local SEO, use 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.
  6. Filter prospects:
    • Keep topical relevance and editorial pages.
    • Prioritize articles, directories, resource pages, comparisons, statistics pages, templates, and curated lists.
    • Deprioritize homepages, login pages, thin affiliate pages, spam, unrelated forums, and direct competitors unless a comparison angle is valid.
  7. For each good prospect, define the outreach angle:
    • Broken/missing resource
    • Better current data
    • Useful tool/template
    • Alternative or comparison inclusion
    • Expert quote or supporting reference
  8. For the strongest prospects, visit or search the prospect site to find the best contact path.
  9. Draft outreach messages. If contact details were found, include the source. If not, list the next best contact-discovery path.

Output format

Start with:

  • Best outreach angle
  • Highest-priority prospect type
  • Any data limitations

Then include:

Prospect URLSite/domainSourceRelevanceSuggested angleContact pathPriority

Then provide 2-3 reusable outreach drafts:

  • Resource/list inclusion
  • Article update/reference suggestion
  • Competitor alternative/comparison angle

Guardrails

  • Do not invent email addresses, social handles, or contact names.
  • Do not say OpenSEO found contact details unless an OpenSEO tool returned them. Attribute contact discovery to the web/search/browser source used.
  • If contact details are not available after a reasonable search, recommend specific discovery steps such as checking the author page, contact page, LinkedIn, X, or a reputable contact-enrichment tool.
  • Avoid spammy mass outreach. Personalize by page and reason.
  • Flag prospects that are direct competitors or likely paid placements.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.