Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Send LinkedIn connection requests to a list of people via browser automation and track status in a CSV/TSV file. Use when the user wants to bulk-connect with a list of people on LinkedIn (founders, speakers, leads, etc.) from a spreadsheet or list containing LinkedIn profile URLs. Handles Connect button, Follow-mode profiles, already-connected detection, stale URL fallback via LinkedIn search and Google search, and incremental status tracking.
Send LinkedIn connection requests to a list of people via browser automation and track status in a CSV/TSV file. Use when the user wants to bulk-connect with a list of people on LinkedIn (founders, speakers, leads, etc.) from a spreadsheet or list containing LinkedIn profile URLs. Handles Connect button, Follow-mode profiles, already-connected detection, stale URL fallback via LinkedIn search and Google search, and incremental status tracking.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Automates sending LinkedIn connection requests from a list and tracks results in a data file.
Before doing anything else, confirm all of the following with the user. Do not proceed until each item is confirmed.
Ask the user to provide their spreadsheet/CSV/TSV file and confirm it has (or can have) these columns: Person/Founder Name โ full name of the person to connect with Company/Brand Name โ their company or brand (used for search fallback) LinkedIn Profile URL โ optional but highly recommended; reduces automation footprint If the file lacks any column, tell the user which columns are missing and offer to add them.
Ask which browser setup they're using: Option A โ Chrome Browser Relay (recommended for accounts flagged for automation) User must have the OpenClaw Browser Relay Chrome extension installed User opens LinkedIn in their regular Chrome browser and clicks the OpenClaw Relay toolbar icon on that tab (badge turns ON) Use profile="chrome" for all browser tool calls in this mode Option B โ OpenClaw Isolated Browser (openclaw profile) OpenClaw manages a separate Chrome instance On first use, navigate to https://www.linkedin.com and let the user log in; cookies persist across sessions Use profile="openclaw" for all browser tool calls in this mode Confirm which option they've set up. Default to Option A (Chrome Relay) if the user's account has been flagged or warned about automation.
Only proceed once the user says: โ File is ready and accessible โ Browser is open with LinkedIn logged in (and relay is attached if Option A)
Set the profile variable based on user's choice in the Pre-flight Checklist: Option A: profile="chrome" โ reuse the relay-attached tab; get targetId via browser action=tabs Option B: profile="openclaw" โ OpenClaw-managed isolated Chrome instance Do not mix profiles mid-run. Pick one and use it consistently for every browser tool call.
Ensure the tracking file has a Connection Status column. If missing, add it: import csv rows = [] with open('file.tsv', 'r') as f: reader = csv.DictReader(f, delimiter='\t') fieldnames = reader.fieldnames + ['Connection Status'] rows = list(reader) with open('file.tsv', 'w', newline='') as f: writer = csv.DictWriter(f, fieldnames=fieldnames, delimiter='\t') writer.writeheader() for row in rows: row['Connection Status'] = '' writer.writerow(row)
Always try in this order. Move to the next tier only if the current one fails.
Navigate directly to the LinkedIn profile URL from the data file. โ URL loads โ correct profile, proceed to connect โ Returns 404 โ escalate to Tier 2 Skip Tier 1 if no URL is in the data file for this person
Search Google for "Founder Name" "Brand/Company" linkedin. Navigate to: https://www.google.com/search?q=<Name>+<Company>+linkedin Find the LinkedIn profile link in results (usually first result), click it Once on the profile, proceed to Connect step โ ๏ธ Only escalate to Tier 3 if Google can't find the right person or returns no LinkedIn result
Run a LinkedIn people search for the founder + brand directly inside LinkedIn. Navigate to: https://www.linkedin.com/search/results/people/?keywords=<Name>+<Company> Look for inline Connect buttons first; otherwise open the profile from search results Confirm name + headline/company match before connecting โ No trustworthy match โ mark Profile Not Found See references/browser-workflow.md for detailed browser steps for each tier.
Once on the correct profile, two patterns exist: Pattern A - Direct Connect button visible on profile โ click it โ confirm dialog โ Send without a note Pattern B - Follow mode (no Connect button, only Follow + Message + More) โ click More actions โ use selector .artdeco-dropdown__content--is-open to get dropdown โ click Invite [Name] to connect โ confirm dialog โ Send without a note If neither Connect nor Invite is available โ mark Follow Only.
StatusMeaningRequest SentConnection request sent this sessionAlready Connected1st degree - no action neededPendingRequest already sent previouslyFollow OnlyNo Connect option available on this profileProfile Not FoundAll three tiers failedSkippedIntentionally skipped
When a TSV row has multiple founders, track per-founder status separated by |: Founder1Slug: Request Sent | Founder2Slug: Already Connected
โ ๏ธ LinkedIn flags accounts that jump directly between profile URLs. Always visit the feed between profiles โ no exceptions. Navigate to /feed/ before every single profile, without exception. See references/browser-workflow.md for the exact call. This is the primary anti-detection measure. Add a short natural pause (2โ4 seconds) after loading the feed before navigating to the next profile. If >3 consecutive clean URLs return 404, pause for 10 seconds on the feed before continuing (then fall back to Google/LinkedIn search). Do not open new browser tabs โ the relay breaks; reuse the same attached tab for every action. Aim for no more than 20โ25 connection requests per session. Stop and tell the user if you're approaching this limit.
Use a linkedin_progress.json sidecar file: { "statuses": { "https://www.linkedin.com/in/username/": "Request Sent" } } Update the TSV from this dict every 10 profiles or at the end.
references/browser-workflow.md - Detailed browser steps for all three tiers and both connect patterns
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.