agentleFS
khadinakbarlabskhadinakbarlabs/vibeseo-plugin/skills/link-building/SKILL.md

link-building

Skill0 starsChanged 33 days agoMITView on GitHub

Find and qualify relevant link-building opportunities, resource pages, broken-link prospects and editorial pitches, then draft outreach for review. Use for backlink opportunities, link prospect research, competitor link research from supplied exports, or outreach drafts. Uses owned Apify Actors and source evidence; never treats a prospect as an acquired backlink or sends messages automatically.

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use conversion-tracking, attribution and 10 more.

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

    conversion-tracking

    Set up, audit, verify, or fix website conversion tracking. Use when the conversion is a form submission, booked meeting, chat, phone call, signup, or purchase; when conversions must reach Google Ads, Meta, GA4, LinkedIn, TikTok, or Microsoft Ads; when the work involves GTM tags and dataLayer events, pixels, the Conversions API (CAPI), Enhanced Conversions, server-side tagging, or gclid and fbclid capture; or when the user reports conversion problems like "conversions stopped", "double counting", "spend but no conversions", "GA4 and Google Ads don't match", or an Unverified or Inactive status. Covers lead gen and ecommerce. Always fire on confirmed success, never the submit click; verify a test conversion arrives; diagnose before changing anything; offer free and native paths alongside paid ones and disclose partner tools. For tracking plans and UTMs, see analytics. For attribution models, see attribution. For campaigns and bidding, see ads. For CRM lead-stage design, see revops.

    Also in 3 projects that use this

  • riggyzSkill

    attribution

    Attribution rules for issues, pull requests, work items, reviews, and comments created or edited by the agent in GitHub, Linear, Azure DevOps, or similar collaboration systems. Use when creating, commenting on, reviewing, or modifying external tracker content.

    Also in 3 projects that use this

  • CesarjoquinSkill

    offers

    When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,' 'value stack,' 'bonus stack,' 'guarantee,' 'risk reversal,' 'money-back guarantee,' 'scarcity,' 'urgency,' 'high-ticket offer,' 'productize a service,' 'naming an offer,' 'payment plan,' 'down-sell,' 'upsell offer,' or 'why isn't my offer converting.' Best for services, agencies, courses, coaching, info products, high-ticket B2B, and direct-response. If you run pure self-serve SaaS, read pricing first — tiers and packaging do more work there. For price level itself (tiers, freemium, value metric), see pricing. For the page that presents the offer, see copywriting. For the launch moment, see launch. For sales collateral, see sales-enablement.

    Also in 3 projects that use this

  • CesarjoquinSkill

    competitors

    When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.

    Also in 3 projects that use this

  • roerohanSkill

    emails

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

    Also in 3 projects that use this

  • timruebenachSkill

    competitor-profiling

    When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitor-alternatives. For sales-specific battle cards, see sales-enablement.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read shared rules, CLI guidance, and Actor contracts.

    line 8
  2. Very specific:

    Use supplied backlink/prospect exports or plan a bounded backlink-opportunity-finder run.

    line 11
  3. Distinctive:

    Prefer earned editorial relevance, useful resources and honest contributions.

    line 14

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

Qualified link opportunities

Read shared rules, CLI guidance, and Actor contracts.

  1. Reuse the site/audience and identify the useful asset: original research, a tool, a guide, a template or an expert contribution. With no useful asset, prepare an asset plan first. Obtain relevant topics, market/language, preferred opportunity types and excluded domains.
  2. Use supplied backlink/prospect exports or plan a bounded backlink-opportunity-finder run. Its rows are search-derived candidate opportunities. The seo-domain-keyword-scraper backlink summary is aggregate context, not a complete competitor backlink index. Don't claim URL-level link gaps without actual link rows.
  3. Deduplicate normalized source URLs and domains, retaining evidence of distinct editorial opportunities. Qualify topical/audience fit, current page existence, visible editorial purpose, whether the proposed asset adds value, and where a relevant link could appear. Keep unvisited pages Needs verification. Don't fabricate contacts, authority ratings, traffic or placement availability.
  4. For a broken-link pitch, validate the exact outgoing link with broken-link-checker within approved bounds or an existing checked export. A timeout, block or 403 alone does not prove a dead link. Recheck ambiguous failures and inspect the referring page/context before proposing a replacement. The checker proves only its sampled observation.
  5. Prefer earned editorial relevance, useful resources and honest contributions. Exclude spam networks, automated comment links, manipulative exchanges and guarantees. Paid advertising/sponsorship requires a separate explicit user decision, disclosure and appropriate link qualification; this plugin does not buy placements. Review Google link-spam policies.
  6. Deliver a shortlist: source URL, topic/asset fit, opportunity type, observed evidence/date, verified/proposed link context, missing checks, public business contact if actually observed, priority/reason and next step. Distinguish Discovered → Qualified → Drafted → Contacted → Responded → Placement observed. Only update later stages with evidence of the actual action/result.
  7. Draft a short relevant pitch with the real reason to contact that publisher and the supplied asset. Use placeholders for unknown recipient details. Never add fake praise, first-hand claims or promised benefits. Do not send it. Sending later needs the exact recipient and message approved through a separately available authorized channel.

Done when the owner can review the prospects and drafts. No hidden self-promotion or affiliate link is appended to the user's deliverable. Use report template.

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.