Turn a Competitor's LinkedIn Post into a Warm Lead List with an AI Agent

# Scout — Loadout

```yaml
loadout: competitor-post-capture
tier: apex                # Apex tier (or an active Apex trial)
mcp: https://apex.leadshark.io/mcp
```

**The job:** Their audience is your audience. Pull everyone who engaged with a competitor's post, qualify them, and reach out with the context of what they just engaged with.

## Before you run — ask the user

Only ask what you don't already know — check the conversation, your memory,
and the account itself first. Confirm anything you inferred in one line
instead of re-interviewing.

1. **Which competitor or creator's audience are you capturing?**
2. **What filter makes someone worth contacting?** (title, company size, region)
3. **What's the note angle — how do you reference what they engaged with?**

## Steps

1. **See** — call `list_post_engagers`: Pull every commenter and reactor from the competitor's post.
2. **Decide** — call `enrich`: Enrich each engager; keep only ICP fits.
3. **Decide** — call `enrich_company`: Check the accounts behind the best fits.
4. **Decide** — call `manage_activity_limits`: Preflight: check remaining connect budgets before drafting — nothing staged into a cap that's already spent.
5. **Decide** — call `list_actions`: Preflight: check the action log — engagers already touched by any Loadout get skipped, never double-touched.
6. **Act** — call `send_connection_request`: Connect with a note referencing the post they engaged with — approval-gated.

## STOP — approval gate

Present everything you found and drafted BEFORE any write. Do not send,
schedule, publish, connect, or create automations until the user approves.
Edits beat re-drafts: apply their changes, don't start over.

## Never

- Write to LinkedIn without explicit approval this run.
- Invent facts, numbers, results, or people.
- Contact anyone on the do-not-engage list, or double-touch someone
  (check `list_actions` first).
- Retry around a refusal — report what was refused and why.

## Done means

- The user approved the drafts (aim for ≤2 edit rounds).
- Approved actions are queued or scheduled — verify via `list_actions`.
- Report back: what ran, what's staged, and where to monitor it.

## Why this stays account-safe

Reads are unlimited; the writes (connects) are paced, capped, deduped against people you've already touched (list_actions), and queued for your approval.

Using Apex, pull everyone who commented on {competitor}'s last 3 posts. Enrich each for title and company, keep only VP+ at 50–500-employee B2B SaaS, and draft a personalized connection note referencing their comment. Put every request in the approval queue — send nothing until I confirm.