---
name: aibb-outreach-drafter
version: 0.1.0
description: Draft link-building, partner, and prospect outreach.
triggers:
  - "aibb outreach drafter"
  - "AIBB draft link-building, partner, and prospect outreach"
tools:
  - terminal
  - file
  - web
  - browser
  - linear
mutating: true
---

# aibb-outreach-drafter

## Purpose

Draft link-building, partner, and prospect outreach.

## When to use

Use for AI Business Boomer SEO, content, outreach, or growth work when this exact procedural lane is needed. Do not use as a generic writing assistant.

## Required inputs

- Target AIBB offer or page.
- Target URL(s), keyword(s), audience, and constraints.
- Current source material or page content.
- Available data: GSC, crawl, SERP, AI citation checks, or prior Linear context.
- Repo/worktree and branch target when code/content changes are expected.

## Tools/access required

- Business Boomer repo access.
- Linear access for tickets/proof comments.
- GitHub CLI for PRs when changes are made.
- Vercel/GitHub deployment status readback when publishing.
- Google Search Console / Sheets only when specifically needed; if unavailable, log blocker and continue with local/exported data.

## Workflow

1. Restate the specific outcome and proof target.
2. Confirm required inputs from files, GSC exports, Linear, repo, or live URL.
3. Execute the smallest useful batch; avoid planning-only output.
4. Write artifacts under `automation-outputs/aibb-agent-skills/` or the active sprint folder.
5. If code/content changes are made, run build/tests that apply.
6. Open or update a PR when the change is ready.
7. Add Linear proof comment with artifact paths, PR URL, build result, and blockers.
8. Hand to Hermes QA before claiming done.

## Output format

target, reason for outreach, email draft, follow-up draft, target AIBB page, approval status

## Acceptance criteria

draft-only unless Sam approves sending; no spam/fake personalization/misleading claims

## Proof required

- File paths or Google Sheet/Doc links for artifacts.
- PR URL if code/content changed.
- Build command and output summary.
- Live URL verification after deploy where applicable.
- Linear ticket/comment URL for traceability.

## Failure modes and recovery

- Missing GSC/GitHub/Vercel/Sheets access: document exact blocker, use existing exports/local data, and create a Linear blocker ticket.
- Build failure: stop, capture error, fix if in scope, otherwise ticket it.
- Dirty unrelated files: do not include them; isolate branch/worktree.
- SERP/API/browser failure: retry once with alternate source, then log limitation.
- Risky external action: ask Sam before sending, publishing outreach, changing bot policies, redirects, or noindex decisions.

## When to ask Sam

Ask only for access, irreversible publishing/indexing/redirect decisions, external sending/outreach approval, or policy changes around GPTBot/training-bot access.

## Anti-patterns

- Generic SEO advice with no artifact.
- Fake citations, fake metrics, fake testimonials, or made-up customer proof.
- Mass publishing thin content.
- Installing random tools without vetting.
- Saying done without PR/build/live/proof evidence.

## Skill quality rubric

Before using or modifying this skill, check:
1. Outcome clarity — produces a concrete deliverable.
2. Explicit inputs — URLs/keywords/audience/constraints/data/repo/offer are known.
3. Progressive disclosure — stays narrow and loads only when relevant.
4. Failure handling — includes access/API/build/deploy fallbacks.
5. Maintainability — versioned, editable, not brittle-site dependent.
6. Safety and permissions — no broad secrets, fake citations, spam, traffic bots, or risky automated publishing.

## Core rule

No AIBB SEO/marketing skill is done unless it produces at least one of:
- PR opened
- page deployed
- indexing submitted/logged
- QA proof created
- Linear ticket created for blocked fixes