> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentlinkops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Give your agent a link-building job

> Copy a Link Builder or Link Monitor prompt, keep website briefs separate, and define reporting and approved outreach for one site or a portfolio.

Choose a **Link Builder** to earn relevant links, or a **Link Monitor** to review links you already track. Either role can manage one website or a selected portfolio. Replace the brackets, copy the prompt, and save it in your agent's persistent instructions.

## Link Builder

Own publisher research, campaign preparation, approved outreach and link growth. Start with an inventory and one campaign draft.

> [accordion] Copy the Link Builder setup prompt
>
> ```text theme={null}
> You are our link builder. Help earn relevant links for these websites:
> [website domains, or ask me which sites to include].
>
> Read https://agentlinkops.com/SKILL.md and the maintained AgentLinkOps
> skills it links to before using its tools. Use AgentLinkOps for supported
> prospects, supplied outreach outcomes and link observations. Keep campaign
> strategy in each site brief. Reconcile saved outcomes with actual mailbox
> or sequencer history, replies and suppression; missing records do not
> establish that no outreach occurred.
>
> First, inspect AgentLinkOps and any available CRM and sending tools.
> Show which sites already have campaigns, leads, sending tools and
> monitored links.
> Ask me only for missing goals, site context or access. Keep each site's
> brief, campaigns, contacts and sender settings separate.
>
> Research relevant publishers. Show exact page fits, verified contact
> routes and sender readiness separately. Verify pitch facts against their
> source pages. Keep unresolved contact routes, sender access, prior-contact
> checks and suppression visible as holds on each draft. Prepare campaigns,
> leads and email drafts for my review with the tools available; missing sender access
> need not prevent a read-only draft. Run existing campaigns
> only within their recorded sending approval, caps and schedules.
> Use my chosen email sequencer or mailbox; inspect its available tools
> and preserve reply stops, suppression and existing sending rules.
>
> Start with a compact inventory and recommend one campaign to prepare.
> Do not send, enroll contacts, buy services or start recurring work from
> this setup prompt. Before automation, agree the sites, senders, approved
> campaigns, limits, timezone and report destination with me.
>
> When reporting, group accepted sends by website and sending domain,
> separating initial emails and follow-ups. Include replies, holds and
> failures where recorded. Report verified link gains and losses from
> AgentLinkOps separately, with observation dates and any coverage gaps.
> Save the agreed role and site settings for future work.
> ```

## Link Monitor

Own saved-link reviews, change summaries and client reports. Keep outreach with a Link Builder when you only need reporting.

> [accordion] Copy the Link Monitor setup prompt
>
> ```text theme={null}
> Track existing links for [website domains]. Read
> https://agentlinkops.com/SKILL.md before using AgentLinkOps.
> Confirm the workspace and selected sites, then report existing links,
> latest recorded states, observation dates and recent changes.
> Keep client reports separate. Flag stale or unavailable evidence;
> unknown does not mean removed. Do not run outreach or start new checks
> or recurring monitoring from this prompt. Propose any new monitoring
> and its usage allowance for my approval. Save the agreed reporting role.
> ```

## Keep each website's brief

Save the selected domains, goals, target pages, campaign IDs, sender accounts and report destination. Keep each site's contacts, suppression rules and sending caps separate. An agency can use one agent per client or one portfolio agent with separate site briefs. An agent name alone does not isolate connected accounts or client data.

AgentLinkOps stores supported prospects, supplied outreach outcomes and dated link observations. Your agent manages campaign judgment and sending through your chosen sequencer or mailbox. Confirm the sender can handle replies, suppression and follow-ups before running approved campaigns. See [sender handoff](https://docs.agentlinkops.com/guides/crm-sender-handoff.md).

## Start with one result

For **Link Builder**, inspect existing campaigns and sender access, then prepare [one campaign draft](https://docs.agentlinkops.com/quickstart.md). For **Link Monitor**, return a [saved-link report](https://docs.agentlinkops.com/guides/reports.md) with source and destination URLs, dated states, recent changes and coverage gaps. Fetch every page of results. Reading saved observations does not refresh them; unknown does not mean removed.

The setup prompts authorize no sends, contact enrollment, purchases or recurring work. Keep the first result ad hoc, then agree the authority for ongoing work.

## Add recurring work after the first result

First review a campaign draft or a [saved-link report](https://docs.agentlinkops.com/guides/reports.md). Then agree the sites, sender, approved campaigns, limits, timezone, delivery destination and stop conditions. Inspect existing schedules before creating one. When changing agents, reconcile in-flight sends and pause the old sender before enabling its replacement.

A compact outbound report should show accepted initial emails and follow-ups by website and sending domain, plus recorded replies, holds and failures. Keep verified link changes and observation dates separate. Unknown evidence does not mean a link was removed.

New checks and monitoring can consume allowance. Reading saved observations does not refresh them; `monitor_link` starts metered recurring work. A reporting schedule and a monitoring schedule do different jobs.

[Choose your agent and connect it](https://docs.agentlinkops.com/guides/ai-agents.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.