message-connections

Files (1)

• SKILL.md

SKILL.md (first lines)

## Browser Preflight (MANDATORY — do this FIRST)

Before delegating to any agent, attach the Claude Chrome extension to this session:

1. Tell the user in chat:
   > "I need browser access to LinkedIn. You may see a permission prompt — please approve it. I'll wait."
2. Navigate to `https://www.linkedin.com/feed/` using the Browser tool. This triggers Claude's permission system and attaches the Chrome extension to the session.
3. Confirm the LinkedIn feed page loaded (content visible, not an error/login wall). If it fails, tell the user the extension isn't connected and stop — do NOT delegate to the agent.

If LinkedIn already loaded earlier in this session, this step passes instantly.

Delegate to the **outreach** agent in **message-connections mode**:

- Read ICP connections: **Pro plan** — fetch from API via browser tab using `references/api.md` (`/v1/gtm/connections?status=new&icp_tier=1`); **Basic plan** — read from the "ICP Connections" tab in the user's spreadsheet
- Filter to Status = "New" (skip already messaged or skipped)
- For each connection:
  1. Check `messages-sent.json` — skip if already messaged
  2. Run the **Mandatory Message History Check** (see outreach agent) — skip if they fail the history rules
  3. Research their profile (brief — they're already ICP-qualified)
  4. Check existing LinkedIn message thread — if prior conversation exists, frame as follow-up
  5. Draft contextual DM following the 3-paragraph message structure
- Present messages one-by-one or as a clearly enumerated batch for user approval (Approve / Edit / Skip), including during `run-all`
- Update status to "Messaged" after sending — sync per `references/storage.md`
- Log all messages to agent memory (`messages-sent.json` with method "ConnectionListDM") and sync per `references/storage.md` using the canonical dashboard `lead_id` resolved from the matched lead (`id`, `_id.$oid`, then `original_id`), not a LinkedIn slug
- If a connection must be added as a lead first, sync/fetch the lead first, then write or sync the message
- Save `last-run-connections-list.json` with current timestamp
- Report: "{n} DMs sent, {m} skipped, {remaining} still in queue"

Rate limits: max 40-50 messages per day. Batch in groups of 15-20, pause between batches.

From Kasper-AI/gtm-kit-plugin, MIT.

More from Kasper-AI/gtm-kit-plugin