⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

v1.0.0

backlink-outreach

jasper0122@jasper0122⭐ 8 stars· last commit 2mo ago· 0 open issues

Find, evaluate, pitch and track natural backlink and content partnerships. Prospects come from the GEO citation data rather than a generic blog search: the targets are the pages an AI already cites when answering your category questions. Research runs on the Monid tool layer (web search and scrape, authority metrics, company enrichment, email validation). Triggers "backlink", "link building", "outreach email", "who is citing us", "find link partners", "guest placement", "backlink-outreach". Research and drafting are always allowed; SENDING, PUBLISHING and PROMISING a link are never done without an explicit instruction.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐ 8 on GitHubGitHub ↗

New / niche

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

agent-seo-kit

Four Claude Code skills that run a search pipeline end to end: measure where you stand, measure whether AI answers name you, pick the target, write it, and go get the links. Every network call goes through Monid, so there is one key and one balance instead of four vendor contracts.

competitor keywords ──→ seo-intake ──┐
                                     ├──→ content-library.json ──→ content-thicken ──→ article
answer engine probes ──→ geo-monitor ┘        │
                     │                        └──→ placement for a partner
                     └──→ ranked cited hosts ──→ backlink-outreach ──→ outreach + links

The four

SkillWhat it does
seo-intakePulls the organic keyword set for your domain and each competitor, computes the gap locally, and routes every keyword to the one action that can help it: write-new, striking, build-depth, defend, or noise.
geo-monitorMeasures whether AI answer engines mention, recommend and cite you. Puts a fixed registry of real user questions to an answer engine, detects the three signals plus competitors, and turns "a rival is named and we are not" into a tracked queue. Optionally cross checks citation counts across eight assistants.
content-thickenThe writing driver. Takes one target from the fused library, pulls the real questions it must answer, drafts a long-form guide against a template contract, validates deterministically, and stops at preview.
backlink-outreachProspects come from the citation data rather than a generic blog search, so every target is a page that already shapes an answer you lose. Ten steps from research to verified placement, with a tracker that enforces its own state rules. An authority floor set to your own Domain Rating gates every prospect before it is scored, and paid placements are refused at any DR.

Why the data layer is Monid

The pipeline needs a keyword tool, an answer engine, a Reddit search, a page scraper, company enrichment and email validation. Bought separately that is five signups, five minimums and five invoices, most of which sit idle between runs.

Monid is a tool layer for agents: one key and one balance reach all of them, discovered and inspected for free, billed per call. Nothing here holds an API key of its own.

Enable it once:

npm install -g @monid-ai/cli@latest
monid setup
monid keys add -k <key from https://app.monid.ai/access/api-keys> -l main

Install the official monid skill too, so your agent can discover and price endpoints itself:

set up https://monid.ai/SKILL.md

The SEO reports need an entitlement, and it is free

Ahrefs and Semrush are entitlements on a Monid workspace, not open endpoints. A fresh workspace can see them in monid discover and still be refused at run time with a permission error.

Getting it turned on is free. Ask at [email protected], or join the WeChat group at the bottom of this README and ask there.

Everything else in the kit (the answer engine, Reddit, page scraping, enrichment, email validation) works on a normal workspace with no extra step.

Install

git clone https://github.com/Jasper0122/agent-seo-kit.git
cd agent-seo-kit
cp seo.config.example.json seo.config.json   # then fill it in
cp -r skills/* ~/.claude/skills/             # Claude Code picks them up by directory name

No dependencies. Node 20 or newer.

Three fields in seo.config.json decide whether the output is useful:

  • site.domain, the domain you are optimising.
  • site.brandTerms, your brand and its common misspellings. Left out, brand navigation dominates every average and the pipeline writes articles for people who already found you.
  • competitors, hand picked. Automatic discovery does not work for a young domain: it returns a directory site and a social network at near zero relevance.

Run it

# search side
node scripts/pull-organic.mjs --dry-run    # quote the cost, spend nothing
node scripts/pull-organic.mjs
node scripts/classify.mjs                  # free

# answer side
cp data/geo-registry.example.json data/geo-registry.json   # then write your own questions
node scripts/run-geo.mjs --dry-run
node scripts/run-geo.mjs
node scripts/geo-dictionary.mjs --min 2    # harvest who was named, DRAFT only
node scripts/redetect.mjs                  # free, after you confirm the draft
node scripts/geo-opportunities.mjs
node scripts/geo-ledger.mjs

# fuse, then write
node scripts/build-content-library.mjs
node scripts/questions-for.mjs "<your target keyword>"

# links
node scripts/prospects-from-geo.mjs --min 2
node scripts/tracker.mjs list

# optional breadth check across eight assistants
node scripts/ai-visibility.mjs --dry-run

What it costs

Every paid script quotes itself with --dry-run first and prints what it actually spent afterwards. The dials:

ScriptBillsThe dial
pull-organicper keyword rowlimits.rowsPerDomain. Ahrefs is about 36x the Semrush rate per row, and Semrush allows far deeper pulls. Switch with one field.
run-geoper questionregistry size, and --limit
questions-forper Reddit post--max
ai-visibilityper domainhow many competitors you include
prospects-from-geo --authorityper hosthow many prospects you score
everything elsefreeit only reads what was already bought

limits.maxSpendPerRunUsd is a hard stop on the keyword pull, and it refuses rather than warns.

The ideas worth stealing, even if you never run this

  • Every topic traces to evidence of real demand. A keyword tool, a real thread, first party research. Never a model's suggestion. The moment a topic is invented, every number downstream is decoration.
  • The wrong action on the right keyword does nothing. A title rewrite helps a page already being shown. Spend one at position 40 and nothing happens.
  • Losing in an AI answer is invisible. No click, no referrer, no log line. The only way to know is to ask the questions yourself and store the answers.
  • Never average the cohorts. Brand questions name the brand by construction. Mixed with generic questions they produce a healthy number that describes nothing.
  • The recommendation detector is a heuristic and it has been wrong. Read the evidence before reporting a rate. Mentions and citations are deterministic; endorsement is not.
  • A throttled row and a genuine absence look identical once written down. Errors are recorded as errors and excluded from every denominator.
  • A changed parser starts a new baseline. Re-read stored answers for free rather than comparing two runs with two detectors.
  • sent needs a message id. A finished draft is not a send, and an agent that records one as the other will tell you next week that nobody replied.

What is deliberately not in here

  • No business data. Everything the pipeline reads and writes lives in data/, which is gitignored except for the example registry.
  • No credentials. One Monid key, stored by the Monid CLI, on your machine.
  • No opinions about your product. content-thicken reads a PRODUCT.md you write once. There is a template in its references/.

Join the group

An SEO and GEO discussion group, in Chinese. Also where to ask for the free Ahrefs or Semrush entitlement if email is slower than you want.

If the code has expired, mail [email protected] and you will get a current one.

中文说明 · MIT licensed.

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • skills/backlink-outreach/SKILL.md7.8 KBupstream ↗
    ---
    name: backlink-outreach
    description: Find, evaluate, pitch and track natural backlink and content partnerships. Prospects come from the GEO citation data rather than a generic blog search: the targets are the pages an AI already cites when answering your category questions. Research runs on the Monid tool layer (web search and scrape, authority metrics, company enrichment, email validation). Triggers "backlink", "link building", "outreach email", "who is citing us", "find link partners", "guest placement", "backlink-outreach". Research and drafting are always allowed; SENDING, PUBLISHING and PROMISING a link are never done without an explicit instruction.
    ---
    
    # Backlink outreach
    
    Build editorially useful partnerships. A backlink is the result of a content
    collaboration that helps a reader, not a swap.
    
    ## The one rule that must never break
    
    ```
    research -> evaluate -> draft -> approve -> send
             -> receive materials -> write -> review -> publish -> verify
    ```
    
    **No stage advances without the user saying so.** In particular:
    
    - "look at", "review", "draft a reply", "who should we contact" are read-only
      or draft-only. They never authorise a send.
    - A finished draft is not permission to send it. Sending needs its own yes.
    - Never promise placement, guarantee a followed link, or say you will
      "definitely include" a partner before editorial review.
    - Never edit or publish a live article as part of an outreach commitment
      without explicit approval.
    
    Editorial independence outranks the partnership. Mention a product when it
    helps the reader, and the writing pipeline's honesty rules still apply: no
    invented traffic, ranking, funding, customer or performance claims about
    anyone.
    
    ## Step 1: take prospects from the GEO data, do not re-derive them
    
    ```bash
    node scripts/prospects-from-geo.mjs --min 2
    node scripts/prospects-from-geo.mjs --min 2 --authority   # paid, adds Domain Rating
    ```
    
    This reads `data/geo-latest.json` and returns the hosts an AI actually cited
    when answering your registry questions, ranked by how often **you were absent**
    from those answers.
    
    That ranking is the point. A host cited on a question where the engine named
    two rivals and not you is a page actively shaping an answer you are losing. A
    generic search for "<topic> blogs" finds a similar set with none of that
    evidence attached.
    
    Four tiers, and the tier decides the play:
    
    | Tier | What it means | The play |
    |---|---|---|
    | **Partner** | Already a customer, supplier, integration or existing relationship | Warmest. A contact and a reason to talk exist. |
    | **Prospect** | Cited, not a competitor or a platform | The normal research and pitch path. |
    | **Competitor** | Sells what you sell | Never pitch. Read what they publish; that is the gap. |
    | **Directory** | Review sites, listicle farms | Getting listed is a different task, not an article email. |
    
    The competitor tier is read from the confirmed dictionary that `geo-monitor`
    maintains, so it improves as that file does. Partners come from
    `outreach.partnerHosts` in the config, which you fill in by hand.
    
    **Partners first, always.** Where their own article about their category is
    cited and omits that you exist alongside them, that is a gap in *their*
    coverage as much as in your link profile. That framing is honest and it is the
    whole pitch.
    
    A competitor being highly cited is a finding about the category. Report it, do
    not email it.
    
    ## Step 2: research through the tool layer
    
    Every command below runs through Monid, so there is no separate contract for
    each of these. Run `monid inspect` for the current price before a batch.
    
    **Find and read the exact target page.** Never pitch from a homepage skim.
    
    ```bash
    monid run -p context.dev -e /web/search \
      --query '{"query":"<their topic> site:<their domain>","limit":10}'
    
    monid run -p context.dev -e /web/scrape/markdown \
      --query '{"url":"<the exact article URL>"}'
    ```
    
    Scraping the page to clean markdown costs a fraction of a cent and is what
    makes a real observation possible instead of a generic compliment.
    
    **Measure their authority instead of guessing it.**
    
    ```bash
    node scripts/prospects-from-geo.mjs --min 2 --authority
    ```
    
    One batched call returns Domain Rating, referring domains and traffic estimates
    for up to a hundred hosts. Do it once the list is short enough that a measured
    number changes a decision, not before.
    
    **Confirm who they are, and validate the address before it is ever used.** A
    bounced first email burns the prospect.
    
    ```bash
    monid run -p pdl -e /v5/company/enrich --query '{"website":"<domain>"}'
    monid run -p api.strale.io -e /x402/email-validate --query '{"email":"<address>"}'
    ```
    
    Read `valid`, MX records, whether it is a role address, and any typo
    suggestion. A role address (`info@`, `hello@`) is not disqualifying but lowers
    the reply odds and should be recorded as such. **Validation is not permission
    to send.**
    
    Record every address with its source, the exact source URL, the date checked
    and a confidence note. Source preference, best first: an inbound message, an
    official partnership or contact page, the help centre, a named employee author,
    then a clearly labelled third party.
    
    ## Step 2b: the authority floor, which is a gate and not a score
    
    Apply this before anything is scored, pitched or drafted. A prospect below the
    floor is not a low-scoring prospect. It is not a prospect.
    
    **The floor is your own Domain Rating.** Not a constant. Measure your own
    number at the start of every batch and compare each candidate against it, so
    the bar rises as you do.
    
    ```bash
    monid run -p ahrefs -e /site-explorer/domain-rating \
      --query '{"target":"<your domain>","date":"<today>"}'
    
    monid run -p ahrefs -e /site-explorer/domain-rating \
      --query '{"target":"<their domain>","date":"<today>"}'
    ```
    
    Why a floor at all. On one site this kit was run against, Domain Rating moved
    25 to 30 over three months while referring domains went 122 to 324. Volume did
    almost nothing. The nineteen point jump that followed came from six DR 90+
    domains landing in a single week. A link from below your own DR does not move
    the number and costs the same week of work as one that does.
    
    ### Three checks a Domain Rating will not catch
    
    DR is a backlink metric and it can be inflated. Run these on anything that
    clears the floor.
    
    ```bash
    monid run -p ahrefs -e /site-explorer/metrics \
      --query '{"target":"<domain>","date":"<today>","mode":"domain","country":"us"}'
    
    monid run -p ahrefs -e /site-explorer/backlinks-stats \
      --query '{"target":"<domain>","date":"<today>","mode":"domain"}'
    ```
    
    **Dead shell.** Many referring domains, near zero organic traffic, near zero
    ranking keywords. Reject whatever the DR says. A real example offered as a
    partner: DR 6, 361 referring domains, 0 US traffic, 0 keywords. Referring
    domains without traffic means somebody bought them.
    
    **Inflated DR.** Backlinks divided by referring domains above roughly 20 means
    sitewide, footer or badge links rather than editorial ones. A real example: a
    directory at DR 74 carrying 341,070 backlinks from 3,816 domains, which
    converted into 167 ranking keywords. Not an automatic rejection, but score
    authority as if the DR were far lower, and prefer a free listing to an email.
    
    **Link shop neighbourhood.** Referring domains named like `backlinkshop.site`
    or `linkbooster.shop`. If a prospect's profile is built from these, reject.
    
    ### Paid placement is refused, at any Domain Rating
    
    Priced menus (a rate card for link insertions and guest posts), brokers reselling
    placements on third party sites, and any seller advertising that they omit
    sponsored labelling.
    
    Selling followed links without disclosure is what Google's link spam policy
    names, and buying them is a violation on the buyer's side too. Offer a content
    exchange instead. A site worth having usually accepts one; a site that will
    only take cash is telling you what the link is worth.
    
    Before any money conversation, check whether the site has a free submission or
    "write for
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/jasper0122-agent-seo-kit-skills-backlink-outreach.md

// REPO STATS

8 stars
0 open issues
Last commit: 2mo ago