Token导航 LogoToken导航

Agent Skill · 研究检索

linkedin-bulk-connect(linkedin 批量连接)

linkedin-bulk-connect 用于处理浏览器自动化、网页检查和页面信息提取,适合在 OpenClaw 中需要让 Agent 打开页面、读取网页或验证前端流程时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

linkedin-bulk-connect 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为操作浏览器;许可证为 MIT-0,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 3,888。

总安装 38,556周安装 1,575GitHub Stars 1下载 12,348核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.1.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:linkedin-bulk-connect(linkedin 批量连接)
来源仓库:https://github.com/10madh/linkedin-bulk-connect
安装命令:
openclaw skills install linkedin-bulk-connect
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install linkedin-bulk-connect

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

通过浏览器自动化向人员列表发送 LinkedIn 连接请求,并在 CSV/TSV 文件中跟踪状态。当用户想要从包含 LinkedIn 个人资料 URL 的电子表格或列表中批量连接 LinkedIn 上的人员列表(创始人、演讲者、潜在客户等)时使用。

处理连接按钮、关注模式配置文件、已连接检测、通过 LinkedIn 搜索和 Google 搜索进行过时 URL 回退以及增量状态跟踪。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install linkedin-bulk-connect;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要操作浏览器,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

linkedin-bulk-connect 怎么安装?

在终端执行 openclaw skills install linkedin-bulk-connect。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

linkedin-bulk-connect 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

linkedin-bulk-connect 需要什么权限?

权限级别是操作浏览器。该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

linkedin-bulk-connect 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

linkedin-bulk-connect 用的人多吗?

公开数据是累计安装 38,556 次,近一周安装 1,575 次,下载 12,348 次,GitHub 1 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

linkedin-bulk-connect 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
linkedin-bulk-connect

linkedin 批量连接 · 本页

38,5561操作浏览器MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
linkedin-connect
description
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.

LinkedIn Connect

Automates sending LinkedIn connection requests from a list and tracks results in a data file.

⚠️ Pre-flight Checklist — Confirm Before Starting

Before doing anything else, confirm all of the following with the user. Do not proceed until each item is confirmed.

1. Data File

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.

2. Browser Setup

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.

3. Ready Check

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)

Browser Profile

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.

Data File Setup

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='\	')
    fieldnames = reader.fieldnames + ['Connection Status']
    rows = list(reader)
with open('file.tsv', 'w', newline='') as f:
    writer = csv.DictWriter(f, fieldnames=fieldnames, delimiter='\	')
    writer.writeheader()
    for row in rows:
        row['Connection Status'] = ''
        writer.writerow(row)

Three-Tier Profile Discovery (Priority Order)

Always try in this order. Move to the next tier only if the current one fails.

Tier 1 — Direct LinkedIn URL (fastest, zero ambiguity)

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

Tier 2 — Google Search (reliable fallback, preserves accuracy)

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

Tier 3 — LinkedIn People Search (last resort)

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.

Connecting on a Profile

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.

Status Values

StatusMeaning
Request SentConnection request sent this session
Already Connected1st degree - no action needed
PendingRequest already sent previously
Follow OnlyNo Connect option available on this profile
Profile Not FoundAll three tiers failed
SkippedIntentionally skipped

Multi-founder Rows

When a TSV row has multiple founders, track per-founder status separated by | :

Founder1Slug: Request Sent | Founder2Slug: Already Connected

Rate Limiting & Anti-Detection

⚠️ 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.

Saving Progress

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

  • references/browser-workflow.md - Detailed browser steps for all three tiers and both connect patterns

平台分布

OpenClaw

96.46%
按下载量换算11,911

安全审计

VirusTotal

可疑

ClawScan

通过

Static analysis

未展示

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills