Pinpointing LinkedIn personnel, locating individuals from LinkedIn data by name, company,job title, and industry. Helping recruiters, sales teams, and B2B lead-generationspecialists discover LinkedIn profiles, source candidates, and enrich contactdata—sui
Search LinkedIn professionals with name, company and job‑title filters. Fetch profile information to support head‑hunting and global sales‑lead development. Trigger: LinkedIn people search, find targeted professionals, global lead generation, executive headhunting, contact‑data enrichment
Rank
62
Safety
84
Downloads
1.1k
Updated
Oct 11, 2026
Version
1.0.3
Source
CLAWHUB
About
What it does, and when to use it.
Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.
Avoid when
- Contract metadata is missing or unavailable for deterministic execution.
Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing
Public facts
Every fact links back to the source it came from.
- Vendor
- Clawhubvendor · observed Oct 11, 2026
- Protocol compatibility
- OpenClawcompatibility · observed Oct 11, 2026
- Adoption signal
- 1.1K downloadsadoption · observed Oct 11, 2026
- Latest release
- 1.0.3release · observed Aug 24, 2026
- Handshake status
- UNKNOWNsecurity
Install and run
Setup complexity: low.
clawhub skill install s17304xrt0p2xssnmr7datqzks83gvsr:linkedin-person-search- Install using `clawhub skill install s17304xrt0p2xssnmr7datqzks83gvsr:linkedin-person-search` in an isolated environment before connecting it to live workloads.
- No published capability contract is available yet, so validate auth and request/response behavior manually.
- Review the upstream CLAWHUB listing at https://clawhub.ai/upkuajing/linkedin-person-search before using production credentials.
Contract: missing
curl -s "https://www.xpersona.co/api/v1/agents/clawhub-upkuajing-linkedin-person-search/snapshot"
Documentation
CLAWHUB
66,545 characters of source documentation, loaded on request.
Extracted files
5 files captured from the source.
SKILL.md
---
name: linkedin-person-search
description: "Search LinkedIn professionals with name, company and job‑title filters. Fetch profile information to support head‑hunting and global sales‑lead development.\n\nTrigger: LinkedIn people search, find targeted professionals, global lead generation, executive headhunting, contact‑data enrichment"
metadata: {"version":"1.0.3","homepage":"https://www.upkuajing.com","clawdbot":{"emoji":"👤","requires":{"bins":["python"],"env":["UPKUAJING_API_KEY"]},"primaryEnv":"UPKUAJING_API_KEY"}}
---
# LinkedIn Person Search
Search people data from LinkedIn using the UpKuaJing Open Platform API.
## Overview
This skill provides access to UpKuaJing's LinkedIn people data through one list search script. API key generation and top-up are provided through the `auth.py` script.
## Running Scripts
### Environment Setup
1. **Check Python**: `python --version`
2. **Install dependencies**: `pip install -r requirements.txt`
Script directory: `scripts/*.py`
Run example: `python scripts/*.py`
**Important**: Always use direct script invocation like `python scripts/linkedin_person_search.py`. **Do NOT use** shell compound commands like `cd scripts && python linkedin_person_search.py`
### LinkedIn Person List Search (`linkedin_person_search.py`)
- **Return granularity**: Each person as one record
- **Use cases**: Focus on "which people exist" in LinkedIn data
- **Examples**:
- "Find CTOs at XXXX"
- "Find Sales Directors in China"
- **Parameters**: See [LinkedIn Person List](references/linkedin-person-list-api.md)
## API Key and Top-up
This skill requires an API key. The API key is stored in the `~/.upkuajing/.env` file:
```bash
cat ~/.upkuajing/.env
```
**Example file content**:
```
UPKUAJING_API_KEY=your_api_key_here
```
### **API Key Not Set**
First check if the `~/.upkuajing/.env` file has UPKUAJING_API_KEY;
If UPKUAJING_API_KEY is not set, prompt the user to choose:
1. User has one: User provides it (manually add to ~/.upkuajing/.env file)
2. User doesn't have one: You can apply using the interface (`auth.py --new_key`), the new key will be automatically saved to ~/.upkuajing/.env
Wait for user selection;
### **Account Top-up**
When API response indicates insufficient balance, explain and guide user to top up:
1. Create top-up order (`auth.py --new_rec_order`)
2. Based on order response, send payment page URL to user, guide user to open URL and pay, user confirms after successful payment;
### **Get Account Information**
Use this script to get account information for UPKUAJING_API_KEY: `auth.py --account_info`
## API Key and UpKuaJing Account
- Newly applied API key: Register and login at [UpKuaJing Open Platform](https://developer.upkuajing.com/), then bind account
### **Report Skill Call Errors**
When an API call fails or returns abnormal data (server error, timeout, malformed response, etc.), explain the anomaly to the user in natural language and ask whether to report it to the platform for troubleshooting. On_meta.json
{
"ownerId": "kn76ywjzma121r2rh959ejsf49834c6x",
"slug": "linkedin-person-search",
"version": "1.0.3",
"publishedAt": 1787563486758
}references/linkedin-person-list-api.md
# 领英找人列表搜索 API 参考 > 数据来源已由接口固定为 `linkedin`(领英),调用方无需传入 `sourceNames`。 > 接口路径:`POST /agent/search/linkedin/person/list` ## python脚本参数 - `--params`: API业务参数(JSON字符串) - `--task_id`:任务ID;用于继续之前的任务或断点续传 - `--query_count`:期望获取的总记录数;默认20;范围20~1000 - params、task_id 必须指定其一,不能同时指定 ## params API业务参数 ### 关键词搜索 - keywords(数组):关键词匹配列表(涉及:人名、公司名、人物行业、公司行业、人物简介、职位、角色、职级、学位、兴趣爱好、技能字段) - humanNames(数组):人物名关键词列表 - humanNamesFilter(数组):人物名不包含的关键词列表 - companyNames(数组):公司名关键词列表 - companyNamesFilter(数组):公司名不包含的关键词列表 - titleNames(数组):职位名称关键词列表 ### 行业筛选 - humanIndustries(数组):人物行业列表 - humanIndustriesFilter(数组):不包含的人物行业列表 ### 地理筛选 - countryCodes(数组):国家代码列表(ISO 3166-1 alpha-2) - countryCodesFilter(数组):不包含的国家代码 ### 联系方式筛选 - existPhone:0=全部,1=存在,2=不存在 - existWhatsApp:0=全部,1=存在,2=不存在 - existEmail:0=全部,1=存在,2=不存在 - existWebsite:0=全部,1=存在,2=不存在 - existSocial:0=全部,1=存在,2=不存在 ### 排序与匹配 - sort(整数):0=匹配度排序,1=综合排序 - isExact(布尔值):true=精确匹配,false=模糊匹配(默认 false) ### 游标与 PIT - cursor(字符串):查询游标;首次请求不传 - usePit(布尔值):是否启用 PIT 模式(大数据量翻页时更稳定) - pitId(字符串):PIT 游标 ID;启用 PIT 后由首次响应返回,后续请求回传 ## 响应数据 ### 外层结构 - code(整数):响应码,0 表示成功 - msg(字符串):响应消息 - data:人物列表数据(见下) - fee:计费信息(apiCost 本次扣费、accountBalance 账户余额、uuid 调用标识) ### data 字段 - cursor(字符串):下一页查询游标 - pitId(字符串):PIT 游标 ID(启用 PIT 时返回) - list(数组):人物列表 ### list 人物字段 - hid:人物唯一标识 - pid:公司唯一标识 - human_name:人物名称 - company_name:公司名称 - country_code:人物所属国家 ISO 代码 - title_names:职位名称列表 - title_levels:职位级别列表 - employee:公司员工人数范围 - experience_num:工作经历次数 - human_industries:人物行业描述列表 - company_industries:公司行业描述列表 - gender:性别(F=女性,M=男性) - human_type:人物类型(0=未检测,1=个人,2=公司,3=不确定) - phone_num:电话数量 - email_num:邮箱数量 - website_num:网址数量 - social_num:社媒数量 - ws_num:WhatsApp 数量 - exist_company_website:是否有公司官网(1=存在,2=不存在) - rate:数据评分 - es_score:es 匹配评分
references/skill-error-report-api.md
# Agent调用Skill异常上报 API 参考 > 上报 Agent 调用 Skill 异常,用于平台侧问题追踪与优化。异常上报不产生查询费用。 > 接口路径:`POST /agent/skill/error/report` > 鉴权:需要 Bearer 令牌(UPKUAJING_API_KEY) ## python脚本参数 - `--params`:JSON格式的上报参数(必填) - 未传 `skillId`/`skillVersion` 时,脚本会自动从当前 Skill 目录名与 SKILL.md 读取并填充 - 必填参数:`skillId`、`skillVersion`、`requestId`、`requestPath`、`context`;其中 `requestId` 从出问题的请求响应(ApiResp.requestId)中获取 ## API请求参数 | 参数 | 类型 | 必填 | 说明 | |------|------|------|------| | skillId | string | 是 | Skill 标识(最大128字符),如"customs-analysis-area" | | skillVersion | string | 是 | Skill 版本(最大32字符) | | agentName | string | 否 | Agent 名称(最大128字符) | | modelName | string | 否 | 模型名称(最大128字符) | | requestPath | string | 是 | 出问题的站内接口路径,以 / 开头(最大255字符),如"/agent/customs/analysis/area" | | requestId | string | 是 | 全请求唯一关联号(最大128字符),取失败请求响应中的 requestId | | requestTime | long | 否 | 请求发起时间戳(毫秒,≥0) | | requestParams | object | 否 | 请求参数(原始入参,敏感字段会自动脱敏;序列化后≤64KB) | | responseData | object | 否 | 响应数据(异常发生时的返回内容,敏感字段会自动脱敏;序列化后≤64KB) | | durationMs | long | 否 | 本次调用耗时(毫秒,≥0) | | context | string | 是 | 异常上下文(堆栈/错误信息,用于定位根因,最大2000字符) | ## 响应数据 ### 外层结构 - code(integer):状态码,0 表示成功 - msg(string):提示信息 - requestId(string):全请求唯一关联号(32位无横线,与 MDC traceId 同值) ### data 字段 | 字段 | 类型 | 说明 | |------|------|------| | reportId | long | 上报记录 ID |
skill-card.md
## Description: Search LinkedIn professionals with name, company, and job-title filters to fetch profile information for headhunting and global sales lead development. This skill is ready for commercial/non-commercial use. ## Publisher: [upkuajing](https://clawhub.ai/user/upkuajing) ### License/Terms of Use: MIT-0 ## Use Case: Recruiters, sales teams, and B2B lead-generation specialists use this skill to find LinkedIn-derived people records by name, company, job title, industry, geography, and contact-data availability. ### Deployment Geography for Use: Global ## Known Risks and Mitigations: Risk: API keys and account data may be exposed if stored or displayed carelessly. Mitigation: Use a protected environment variable or secret store where possible; if using `~/.upkuajing/.env`, restrict the directory and file to owner-only permissions and do not print or paste the file contents. Risk: LinkedIn-derived people and contact data may be sensitive or regulated. Mitigation: Use the skill only with a lawful basis for processing the data, limit access to result files, and avoid unnecessary retention or redistribution. Risk: Search and account-management API calls may incur fees. Mitigation: Check current pricing and obtain explicit confirmation before paid searches, especially when the requested result count requires multiple calls. Risk: Error reports may accidentally include raw search parameters, responses, profile data, or credentials. Mitigation: Review and redact error-report context before submission; do not include credentials or raw profile/contact data. ## Reference(s): - [LinkedIn Person List API](references/linkedin-person-list-api.md) - [Skill Error Report API](references/skill-error-report-api.md) - [UpKuaJing Homepage](https://www.upkuajing.com) - [UpKuaJing Open Platform](https://developer.upkuajing.com/) - [UpKuaJing OpenAPI Pricing](https://www.upkuajing.com/web/openapi/price.html) - [ClawHub Skill Page](https://clawhub.ai/upkuajing/skills/linkedin-person-search) ## Skill Output: **Output Type(s):** [text, shell commands, configuration, guidance, files] **Output Format:** [Markdown guidance with shell commands plus JSON status and JSONL result files] **Output Parameters:** [1D] **Other Properties Related to Output:** [Search results are written as task-scoped JSONL files, and script responses include task status, request identifiers, file paths, and fee information.] ## Skill Version(s): 1.0.3 (source: server evidence and SKILL.md frontmatter) ## Ethical Considerations: Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
AionUi
Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!
activepieces
AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
cherry-studio
AI productivity studio with smart chat, autonomous agents, and 300+ assistants.
CopilotKit
The Frontend for Agents & Generative UI. React + Angular
Machine-readable data
The same record, as JSON, for agents and crawlers.
{
"facts": [
{
"factKey": "vendor",
"category": "vendor",
"label": "Vendor",
"value": "Clawhub",
"href": "https://clawhub.ai/upkuajing/skills/linkedin-person-search",
"sourceUrl": "https://clawhub.ai/upkuajing/skills/linkedin-person-search",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-11T11:03:31.576Z",
"isPublic": true
},
{
"factKey": "protocols",
"category": "compatibility",
"label": "Protocol compatibility",
"value": "OpenClaw",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-upkuajing-linkedin-person-search/contract",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-upkuajing-linkedin-person-search/contract",
"sourceType": "contract",
"confidence": "medium",
"observedAt": "2026-10-11T11:03:31.576Z",
"isPublic": true
},
{
"factKey": "traction",
"category": "adoption",
"label": "Adoption signal",
"value": "1.1K downloads",
"href": "https://clawhub.ai/upkuajing/linkedin-person-search",
"sourceUrl": "https://clawhub.ai/upkuajing/linkedin-person-search",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-11T11:03:31.576Z",
"isPublic": true
},
{
"factKey": "latest_release",
"category": "release",
"label": "Latest release",
"value": "1.0.3",
"href": "https://clawhub.ai/upkuajing/linkedin-person-search",
"sourceUrl": "https://clawhub.ai/upkuajing/linkedin-person-search",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-08-24T09:24:46.758Z",
"isPublic": true
},
{
"factKey": "handshake_status",
"category": "security",
"label": "Handshake status",
"value": "UNKNOWN",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-upkuajing-linkedin-person-search/trust",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-upkuajing-linkedin-person-search/trust",
"sourceType": "trust",
"confidence": "medium",
"observedAt": null,
"isPublic": true
}
],
"events": [
{
"eventType": "release",
"title": "Release 1.0.3",
"description": "updated",
"href": "https://clawhub.ai/upkuajing/linkedin-person-search",
"sourceUrl": "https://clawhub.ai/upkuajing/linkedin-person-search",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-08-24T09:24:46.758Z",
"isPublic": true
}
]
}Record generated Oct 11, 2026.
