{"id":"9bea1fc7-09b1-469c-b5ff-a6749f355aad","entityType":"agent","slug":"clawhub-upkuajing-linkedin-person-colleague","name":"Uncovering LinkedIn colleagues, locating colleagues and team members from LinkedIn data bycompany ID and personnel ID. Helping recruiters, sales teams, and B2B lead-generationspecialists discover team networks, map organizational relationships, and expand","canonicalUrl":"https://www.xpersona.co/agent/clawhub-upkuajing-linkedin-person-colleague","canonicalPath":"/agent/clawhub-upkuajing-linkedin-person-colleague","generatedAt":"2026-10-12T00:35:23.335Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T19:39:07.665Z","emptyReason":null},"description":"Find internal colleagues through company‑ID and personnel‑ID on LinkedIn. Map organizational structures and gather contacts for sales outreach and account intelligence. Trigger: LinkedIn colleague lookup, map organizational relationships, internal team discovery, account intelligence research, B2B contact expansion","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17304xrt0p2xssnmr7datqzks83gvsr:linkedin-person-colleague","sourceUrl":"https://clawhub.ai/upkuajing/linkedin-person-colleague","homepage":"https://clawhub.ai/upkuajing/skills/linkedin-person-colleague","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/upkuajing/linkedin-person-colleague","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/upkuajing/skills/linkedin-person-colleague","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Uncovering LinkedIn colleagues, locating colleagues and team members from LinkedIn data bycompany ID and personnel ID. Helping recruiters, sales teams, and B2B "},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T19:39:07.665Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T19:39:07.665Z","emptyReason":null},"stars":null,"forks":null,"downloads":1002,"likes":null,"task":null,"library":null,"packageName":null,"latestVersion":"1.0.5","tractionLabel":"1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T19:39:07.597Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T19:39:07.665Z","lastCrawledAt":"2026-10-11T19:39:07.597Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T19:39:07.597Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.5","createdAt":"2026-08-24T09:27:53.698Z","changelog":"updated","fileCount":11,"zipByteSize":18637},{"version":"1.0.4","createdAt":"2026-07-16T08:07:55.610Z","changelog":"updated","fileCount":9,"zipByteSize":15823},{"version":"1.0.1","createdAt":"2026-07-16T08:05:47.105Z","changelog":"updated","fileCount":9,"zipByteSize":15765},{"version":"1.0.0","createdAt":"2026-07-13T07:31:29.731Z","changelog":"updated","fileCount":9,"zipByteSize":15895}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17304xrt0p2xssnmr7datqzks83gvsr:linkedin-person-colleague","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s17304xrt0p2xssnmr7datqzks83gvsr:linkedin-person-colleague` 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-colleague before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-upkuajing-linkedin-person-colleague/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-upkuajing-linkedin-person-colleague/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-upkuajing-linkedin-person-colleague/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-upkuajing-linkedin-person-colleague/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-upkuajing-linkedin-person-colleague/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-upkuajing-linkedin-person-colleague/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-12T00:35:23.334Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-upkuajing-linkedin-person-colleague/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-upkuajing-linkedin-person-colleague/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-upkuajing-linkedin-person-colleague/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-upkuajing-linkedin-person-colleague/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T19:39:07.665Z","emptyReason":null},"readme":"Skill: Uncovering LinkedIn colleagues, locating colleagues and team members from LinkedIn data bycompany ID and personnel ID. Helping recruiters, sales teams, and B2B lead-generationspecialists discover team networks, map organizational relationships, and expand contactlists—suitable for network expansion, background research, and account intelligence.\n\nOwner: upkuajing\n\nSummary: Find internal colleagues through company‑ID and personnel‑ID on LinkedIn. Map organizational structures and gather contacts for sales outreach and account intelligence. Trigger: LinkedIn colleague lookup, map organizational relationships, internal team discovery, account intelligence research, B2B contact expansion\n\nTags: B2B:1.0.5, colleague:1.0.5, corporate:1.0.5, latest:1.0.5, linkedin:1.0.5, mapping:1.0.5, network:1.0.5, people-search:1.0.5, prospecting:1.0.5, relationship:1.0.5, team:1.0.5\n\nVersion history:\n\nv1.0.5 | 2026-08-24T09:27:53.698Z | user\n\nupdated\n\nv1.0.4 | 2026-07-16T08:07:55.610Z | user\n\nupdated\n\nv1.0.1 | 2026-07-16T08:05:47.105Z | user\n\nupdated\n\nv1.0.0 | 2026-07-13T07:31:29.731Z | user\n\nupdated\n\nArchive index:\n\nArchive v1.0.5: 11 files, 18637 bytes\n\nFiles: references/linkedin-person-colleague-list-api.md (1210b), references/skill-error-report-api.md (2070b), requirements.txt (14b), scripts/auth.py (5860b), scripts/common.py (14567b), scripts/error_report.py (1845b), scripts/linkedin_person_colleague_list.py (1993b), scripts/version_check.py (4933b), skill-card.md (2520b), SKILL.md (8676b), _meta.json (144b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: linkedin-person-colleague\ndescription: \"Find internal colleagues through company‑ID and personnel‑ID on LinkedIn. Map organizational structures and gather contacts for sales outreach and account intelligence.\\n\\nTrigger: LinkedIn colleague lookup, map organizational relationships, internal team discovery, account intelligence research, B2B contact expansion\"\nmetadata: {\"version\":\"1.0.5\",\"homepage\":\"https://www.upkuajing.com\",\"clawdbot\":{\"emoji\":\"🤝\",\"requires\":{\"bins\":[\"python\"],\"env\":[\"UPKUAJING_API_KEY\"]},\"primaryEnv\":\"UPKUAJING_API_KEY\"}}\n---\n\n# LinkedIn Person Colleague Query\n\nQuery colleague data from LinkedIn using the UpKuaJing Open Platform API.\n\n## Overview\n\nThis skill provides access to colleague information from UpKuaJing's LinkedIn data. Given a company ID (pid) and a person ID (hid), it returns the list of colleagues with their person IDs and job titles.\n\n**Prerequisite**: Both the company ID (pid) and person ID (hid) are required as input. If the user does not already have them, use the **linkedin-person-search** skill first to search for the target person and obtain their pid and hid, then proceed with this skill.\n\n## Running Scripts\n\n### Environment Setup\n\n1. **Check Python**: `python --version`\n2. **Install dependencies**: `pip install -r requirements.txt`\n\nScript directory: `scripts/*.py`\nRun example: `python scripts/*.py`\n\n**Important**: Always use direct script invocation like `python scripts/linkedin_person_colleague_list.py`. **Do NOT use** shell compound commands like `cd scripts && python linkedin_person_colleague_list.py`\n\n### Colleague List Query (`linkedin_person_colleague_list.py`)\n- **Return granularity**: Each colleague as one record\n- **Use cases**: Find colleagues of a specific person at a company\n- **Examples**:\n  - \"Find colleagues of person H_67890 at company US_12345\"\n  - \"Get more colleagues using the next page cursor\"\n- **Parameters**: See [Colleague List API](references/linkedin-person-colleague-list-api.md)\n\n## API Key and Top-up\n\nThis skill requires an API key. The API key is stored in the `~/.upkuajing/.env` file:\n```bash\ncat ~/.upkuajing/.env\n```\n**Example file content**:\n```\nUPKUAJING_API_KEY=your_api_key_here\n```\n### **API Key Not Set**\nFirst check if the `~/.upkuajing/.env` file has UPKUAJING_API_KEY;\nIf UPKUAJING_API_KEY is not set, prompt the user to choose:\n1. User has one: User provides it (manually add to ~/.upkuajing/.env file)\n2. 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\nWait for user selection;\n\n### **Account Top-up**\nWhen API response indicates insufficient balance, explain and guide user to top up:\n1. Create top-up order (`auth.py --new_rec_order`)\n2. Based on order response, send payment page URL to user, guide user to open URL and pay, user confirms after successful payment;\n\n### **Get Account Information**\nUse this script to get account information for UPKUAJING_API_KEY: `auth.py --account_info`\n\n## API Key and UpKuaJing Account\n- Newly applied API key: Register and login at [UpKuaJing Open Platform](https://developer.upkuajing.com/), then bind account\n\n### **Report Skill Call Errors**\nWhen 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. Only run the report after user confirmation:\n```bash\npython scripts/error_report.py --params '{\"requestPath\":\"/agent/search/linkedin/person/colleague/list\",\"requestId\":\"f47ac10b58cc4372a5670e02b2c3d479\",\"context\":\"LinkedIn colleague list query failed with a server error\"}'\n```\n- Do not report normal business conditions (insufficient balance, invalid API key, parameter errors) — handle them via their own flows\n- Error reporting does not incur query fees\n- **Parameters**: See [Error Report API](references/skill-error-report-api.md)\n\n## Fees\n\n**All API calls incur fees**, different interfaces have different billing methods.\n\n**Latest pricing**: Users can visit [Detailed Price Description](https://www.upkuajing.com/web/openapi/price.html)\nOr use: `python scripts/auth.py --price_info` (returns complete pricing for all interfaces)\n\n### Query Billing Rules\n\nBilled by **number of calls**, each call returns one page of colleague records:\n- Each API call incurs a fee\n- Use `--cursor` to get additional pages (each page is a separate call)\n- **Before execution:**\n  1. Inform user that this query will incur a fee\n  2. Stop, wait for explicit user confirmation in a separate message, then execute script\n\n### Fee Confirmation Principle\n\n**Any operation that incurs fees must first inform and wait for explicit user confirmation. Do not execute in the same message as the notification.**\n\n## Workflow\n\n### Decision Guide\n\n| User Intent | Use API |\n|-------------|---------|\n| \"Find colleagues of person H_67890 at company US_12345\" | Colleague List Query |\n| User has a person/company name but no pid/hid | linkedin-person-search (find the person and get pid/hid, then use this skill) |\n\n## Usage Examples\n\n### Query Colleague List\n\n**User request**: \"Find colleagues of person H_67890 at company US_12345\"\n```bash\npython scripts/linkedin_person_colleague_list.py --pid US_12345 --hid H_67890\n```\n\n**Get next page** (use cursor returned from previous response):\n```bash\npython scripts/linkedin_person_colleague_list.py --pid US_12345 --hid H_67890 --cursor 'cursor_string_from_previous_response'\n```\n\n## Error Handling\n\n- **API key invalid/non-existent**: Check `UPKUAJING_API_KEY` in `~/.upkuajing/.env` file\n- **Insufficient balance**: Guide user to top up\n- **Invalid parameters**: **Must first check the corresponding API documentation in references/ directory**, get correct parameter names and formats from documentation, do not guess\n- **Skill call errors / abnormal responses**: Explain to the user and, with user confirmation, report to the platform via `python scripts/error_report.py` (see [Report Skill Call Errors](#report-skill-call-errors))\n\n### API Documentation Reference\n\n- Colleague List: Check [references/linkedin-person-colleague-list-api.md](references/linkedin-person-colleague-list-api.md)\n- Error Report: Check [references/skill-error-report-api.md](references/skill-error-report-api.md)\n\n## Best Practices\n\n1. **Check API documentation**:\n   - **Before executing queries, must first check the corresponding API reference documentation**\n   - Check [references/linkedin-person-colleague-list-api.md](references/linkedin-person-colleague-list-api.md)\n   - Do not guess parameter names, get accurate parameter names and formats from documentation\n\n2. **Query parameters**:\n   - Both the company ID (pid) and person ID (hid) are required. If the user provides a person/company name instead, first use **linkedin-person-search** to find the target person and obtain their pid and hid.\n\n3. **Pagination**:\n   - When the response returns a non-empty `cursor`, more data is available\n   - Pass the `cursor` value to get the next page\n   - An empty `cursor` means there is no more data\n\n## Notes\n- Colleague records use `hid` as the person unique identifier; `pid` is the company identifier\n- `titleNames` is a list of job title strings for each colleague\n- File paths use forward slashes on all platforms\n- **Prohibit outputting technical parameter format**: Do not display code-style parameters in responses, convert to natural language\n- **Do not** estimate or guess per-call fees — use `python scripts/auth.py --price_info` to get accurate pricing information\n- **Do not** guess parameter names, get accurate parameter names and formats from documentation\n\n## Related Skills\n\nOther UpKuaJing skills you might find useful:\n\n- linkedin-person-search — Search people from LinkedIn data\n- linkedin-company-search — Search companies from LinkedIn data\n- global-company-person-colleague — Query colleague list from the global company database\n- linkedin-company-employee — Query employee list from LinkedIn data\n- linkedin-person-experience — Query work experience list from LinkedIn data\n- global-company-person-search — Search people from the global company database\n- upkuajing-global-company-people-search — Unified company and people search across all sources\n- upkuajing-contact-info-validity-check — Check contact info validity\n- phone-validity-check — Check phone number validity\n- email-validity-check — Check email address validity\n- domain-validity-check — Check domain validity and security- upkuajing-email-tool — Email verification and sending tool\n- upkuajing-sms-tool — SMS tool\n\nFile v1.0.5:_meta.json\n\n{\n  \"ownerId\": \"kn76ywjzma121r2rh959ejsf49834c6x\",\n  \"slug\": \"linkedin-person-colleague\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1787563673698\n}\n\nFile v1.0.5:references/linkedin-person-colleague-list-api.md\n\n# 领英同事列表 API 参考\n\n> 根据公司ID和人物ID获取某人的同事信息，支持游标翻页。\n> 接口路径：`POST /agent/search/linkedin/person/colleague/list`\n\n## python脚本参数\n\n- `--pid`：公司ID（必填），如 `US_12345`\n- `--hid`：人物ID（必填），如 `H_67890`\n- `--cursor`：分页游标（可选），首次查询不传，翻页时传入上一次响应返回的cursor\n\n## API请求参数\n\n| 参数 | 类型 | 必填 | 说明 |\n|------|------|------|------|\n| pid | string | 是 | 公司ID |\n| hid | string | 是 | 人物ID |\n| cursor | string | 否 | 分页游标，首次请求传空串，翻页时传入上一次响应返回的cursor |\n\n## 响应数据\n\n### 外层结构\n\n- code（integer）：响应码，0 表示成功\n- msg（string）：响应消息\n- data：同事列表数据（见下）\n- fee：计费信息（apiCost 本次扣费、accountBalance 账户余额、uuid 调用标识）\n\n### data 字段\n\n- cursor（string）：下一页游标，为空表示无更多数据\n- list（array）：同事列表\n\n### list 同事字段\n\n- pid（string）：公司ID\n- hid（string）：人物ID\n- titleNames（array[string]）：职位名称列表（如 [\"CTO\"]）\n\nFile v1.0.5:references/skill-error-report-api.md\n\n# Agent调用Skill异常上报 API 参考\n\n> 上报 Agent 调用 Skill 异常，用于平台侧问题追踪与优化。异常上报不产生查询费用。\n> 接口路径：`POST /agent/skill/error/report`\n> 鉴权：需要 Bearer 令牌（UPKUAJING_API_KEY）\n\n## python脚本参数\n\n- `--params`：JSON格式的上报参数（必填）\n- 未传 `skillId`/`skillVersion` 时，脚本会自动从当前 Skill 目录名与 SKILL.md 读取并填充\n- 必填参数：`skillId`、`skillVersion`、`requestId`、`requestPath`、`context`；其中 `requestId` 从出问题的请求响应（ApiResp.requestId）中获取\n\n## API请求参数\n\n| 参数 | 类型 | 必填 | 说明 |\n|------|------|------|------|\n| skillId | string | 是 | Skill 标识（最大128字符），如\"customs-analysis-area\" |\n| skillVersion | string | 是 | Skill 版本（最大32字符） |\n| agentName | string | 否 | Agent 名称（最大128字符） |\n| modelName | string | 否 | 模型名称（最大128字符） |\n| requestPath | string | 是 | 出问题的站内接口路径，以 / 开头（最大255字符），如\"/agent/customs/analysis/area\" |\n| requestId | string | 是 | 全请求唯一关联号（最大128字符），取失败请求响应中的 requestId |\n| requestTime | long | 否 | 请求发起时间戳（毫秒，≥0） |\n| requestParams | object | 否 | 请求参数（原始入参，敏感字段会自动脱敏；序列化后≤64KB） |\n| responseData | object | 否 | 响应数据（异常发生时的返回内容，敏感字段会自动脱敏；序列化后≤64KB） |\n| durationMs | long | 否 | 本次调用耗时（毫秒，≥0） |\n| context | string | 是 | 异常上下文（堆栈/错误信息，用于定位根因，最大2000字符） |\n\n## 响应数据\n\n### 外层结构\n\n- code（integer）：状态码，0 表示成功\n- msg（string）：提示信息\n- requestId（string）：全请求唯一关联号（32位无横线，与 MDC traceId 同值）\n\n### data 字段\n\n| 字段 | 类型 | 说明 |\n|------|------|------|\n| reportId | long | 上报记录 ID |\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nFind internal colleagues through company ID and personnel ID on LinkedIn to map organizational structures and gather contacts for sales outreach and account intelligence.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[upkuajing](https://clawhub.ai/user/upkuajing)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal recruiters, sales teams, and B2B lead-generation specialists use this skill to look up colleagues for a known LinkedIn company ID and person ID, map team networks, and expand account-intelligence contact lists.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The security summary flags paid-account credentials, top-up orders, and telemetry for review.\n\nMitigation: Use a safer secret mechanism for the API key where possible, avoid printing or sharing ~/.upkuajing/.env, and confirm paid queries or top-up actions before execution.\n\nRisk: LinkedIn colleague lookup can involve personal and organizational contact data for sales outreach or contact expansion.\n\nMitigation: Confirm the user's privacy, legal, and policy basis before collecting, using, or sharing returned colleague data.\n\nRisk: Error reporting sends troubleshooting context to the platform and may include request metadata.\n\nMitigation: Ask for user confirmation before reporting abnormal calls and avoid including unnecessary sensitive context.\n\n## Reference(s):\n\n- [Colleague List API Reference](references/linkedin-person-colleague-list-api.md)\n- [Skill Error Report API Reference](references/skill-error-report-api.md)\n- [UpKuaJing Homepage](https://www.upkuajing.com)\n- [UpKuaJing Open Platform](https://developer.upkuajing.com/)\n- [UpKuaJing API Pricing](https://www.upkuajing.com/web/openapi/price.html)\n- [ClawHub Skill Page](https://clawhub.ai/upkuajing/skills/linkedin-person-colleague)\n\n## Skill Output:\n\n**Output Type(s):** [JSON, Shell commands, Guidance]\n\n**Output Format:** [Markdown guidance with shell commands and JSON API responses]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Requires UPKUAJING_API_KEY and explicit confirmation before fee-incurring calls.]\n\n## Skill Version(s):\n\n1.0.5 (source: server release evidence and skill metadata)\n\n## Ethical Considerations:\n\nUsers 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.\n\nFile v1.0.5:requirements.txt\n\nhttpx>=0.23.0\n\nArchive v1.0.4: 9 files, 15823 bytes\n\nFiles: references/linkedin-person-colleague-list-api.md (1210b), requirements.txt (14b), scripts/auth.py (5860b), scripts/common.py (14567b), scripts/linkedin_person_colleague_list.py (1790b), scripts/version_check.py (4933b), skill-card.md (2622b), SKILL.md (7573b), _meta.json (144b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: linkedin-person-colleague\ndescription: \"Find internal colleagues through company‑ID and personnel‑ID on LinkedIn. Map organizational structures and gather contacts for sales outreach and account intelligence.\\n\\nTrigger: LinkedIn colleague lookup, map organizational relationships, internal team discovery, account intelligence research, B2B contact expansion\"\nmetadata: {\"version\":\"1.0.4\",\"homepage\":\"https://www.upkuajing.com\",\"clawdbot\":{\"emoji\":\"🤝\",\"requires\":{\"bins\":[\"python\"],\"env\":[\"UPKUAJING_API_KEY\"]},\"primaryEnv\":\"UPKUAJING_API_KEY\"}}\n---\n\n# LinkedIn Person Colleague Query\n\nQuery colleague data from LinkedIn using the UpKuaJing Open Platform API.\n\n## Overview\n\nThis skill provides access to colleague information from UpKuaJing's LinkedIn data. Given a company ID (pid) and a person ID (hid), it returns the list of colleagues with their person IDs and job titles.\n\n**Prerequisite**: Both the company ID (pid) and person ID (hid) are required as input. If the user does not already have them, use the **linkedin-person-search** skill first to search for the target person and obtain their pid and hid, then proceed with this skill.\n\n## Running Scripts\n\n### Environment Setup\n\n1. **Check Python**: `python --version`\n2. **Install dependencies**: `pip install -r requirements.txt`\n\nScript directory: `scripts/*.py`\nRun example: `python scripts/*.py`\n\n**Important**: Always use direct script invocation like `python scripts/linkedin_person_colleague_list.py`. **Do NOT use** shell compound commands like `cd scripts && python linkedin_person_colleague_list.py`\n\n### Colleague List Query (`linkedin_person_colleague_list.py`)\n- **Return granularity**: Each colleague as one record\n- **Use cases**: Find colleagues of a specific person at a company\n- **Examples**:\n  - \"Find colleagues of person H_67890 at company US_12345\"\n  - \"Get more colleagues using the next page cursor\"\n- **Parameters**: See [Colleague List API](references/linkedin-person-colleague-list-api.md)\n\n## API Key and Top-up\n\nThis skill requires an API key. The API key is stored in the `~/.upkuajing/.env` file:\n```bash\ncat ~/.upkuajing/.env\n```\n**Example file content**:\n```\nUPKUAJING_API_KEY=your_api_key_here\n```\n### **API Key Not Set**\nFirst check if the `~/.upkuajing/.env` file has UPKUAJING_API_KEY;\nIf UPKUAJING_API_KEY is not set, prompt the user to choose:\n1. User has one: User provides it (manually add to ~/.upkuajing/.env file)\n2. 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\nWait for user selection;\n\n### **Account Top-up**\nWhen API response indicates insufficient balance, explain and guide user to top up:\n1. Create top-up order (`auth.py --new_rec_order`)\n2. Based on order response, send payment page URL to user, guide user to open URL and pay, user confirms after successful payment;\n\n### **Get Account Information**\nUse this script to get account information for UPKUAJING_API_KEY: `auth.py --account_info`\n\n## API Key and UpKuaJing Account\n- Newly applied API key: Register and login at [UpKuaJing Open Platform](https://developer.upkuajing.com/), then bind account\n\n## Fees\n\n**All API calls incur fees**, different interfaces have different billing methods.\n\n**Latest pricing**: Users can visit [Detailed Price Description](https://www.upkuajing.com/web/openapi/price.html)\nOr use: `python scripts/auth.py --price_info` (returns complete pricing for all interfaces)\n\n### Query Billing Rules\n\nBilled by **number of calls**, each call returns one page of colleague records:\n- Each API call incurs a fee\n- Use `--cursor` to get additional pages (each page is a separate call)\n- **Before execution:**\n  1. Inform user that this query will incur a fee\n  2. Stop, wait for explicit user confirmation in a separate message, then execute script\n\n### Fee Confirmation Principle\n\n**Any operation that incurs fees must first inform and wait for explicit user confirmation. Do not execute in the same message as the notification.**\n\n## Workflow\n\n### Decision Guide\n\n| User Intent | Use API |\n|-------------|---------|\n| \"Find colleagues of person H_67890 at company US_12345\" | Colleague List Query |\n| User has a person/company name but no pid/hid | linkedin-person-search (find the person and get pid/hid, then use this skill) |\n\n## Usage Examples\n\n### Query Colleague List\n\n**User request**: \"Find colleagues of person H_67890 at company US_12345\"\n```bash\npython scripts/linkedin_person_colleague_list.py --pid US_12345 --hid H_67890\n```\n\n**Get next page** (use cursor returned from previous response):\n```bash\npython scripts/linkedin_person_colleague_list.py --pid US_12345 --hid H_67890 --cursor 'cursor_string_from_previous_response'\n```\n\n## Error Handling\n\n- **API key invalid/non-existent**: Check `UPKUAJING_API_KEY` in `~/.upkuajing/.env` file\n- **Insufficient balance**: Guide user to top up\n- **Invalid parameters**: **Must first check the corresponding API documentation in references/ directory**, get correct parameter names and formats from documentation, do not guess\n\n### API Documentation Reference\n\n- Colleague List: Check [references/linkedin-person-colleague-list-api.md](references/linkedin-person-colleague-list-api.md)\n\n## Best Practices\n\n1. **Check API documentation**:\n   - **Before executing queries, must first check the corresponding API reference documentation**\n   - Check [references/linkedin-person-colleague-list-api.md](references/linkedin-person-colleague-list-api.md)\n   - Do not guess parameter names, get accurate parameter names and formats from documentation\n\n2. **Query parameters**:\n   - Both the company ID (pid) and person ID (hid) are required. If the user provides a person/company name instead, first use **linkedin-person-search** to find the target person and obtain their pid and hid.\n\n3. **Pagination**:\n   - When the response returns a non-empty `cursor`, more data is available\n   - Pass the `cursor` value to get the next page\n   - An empty `cursor` means there is no more data\n\n## Notes\n- Colleague records use `hid` as the person unique identifier; `pid` is the company identifier\n- `titleNames` is a list of job title strings for each colleague\n- File paths use forward slashes on all platforms\n- **Prohibit outputting technical parameter format**: Do not display code-style parameters in responses, convert to natural language\n- **Do not** estimate or guess per-call fees — use `python scripts/auth.py --price_info` to get accurate pricing information\n- **Do not** guess parameter names, get accurate parameter names and formats from documentation\n\n## Related Skills\n\nOther UpKuaJing skills you might find useful:\n\n- linkedin-person-search — Search people from LinkedIn data\n- linkedin-company-search — Search companies from LinkedIn data\n- global-company-person-colleague — Query colleague list from the global company database\n- linkedin-company-employee — Query employee list from LinkedIn data\n- linkedin-person-experience — Query work experience list from LinkedIn data\n- global-company-person-search — Search people from the global company database\n- upkuajing-global-company-people-search — Unified company and people search across all sources\n- upkuajing-contact-info-validity-check — Check contact info validity\n- phone-validity-check — Check phone number validity\n- email-validity-check — Check email address validity\n- domain-validity-check — Check domain validity and security- upkuajing-email-tool — Email verification and sending tool\n- upkuajing-sms-tool — SMS tool\n\nFile v1.0.4:_meta.json\n\n{\n  \"ownerId\": \"kn76ywjzma121r2rh959ejsf49834c6x\",\n  \"slug\": \"linkedin-person-colleague\",\n  \"version\": \"1.0.4\",\n  \"publishedAt\": 1784189275610\n}\n\nFile v1.0.4:references/linkedin-person-colleague-list-api.md\n\n# 领英同事列表 API 参考\n\n> 根据公司ID和人物ID获取某人的同事信息，支持游标翻页。\n> 接口路径：`POST /agent/search/linkedin/person/colleague/list`\n\n## python脚本参数\n\n- `--pid`：公司ID（必填），如 `US_12345`\n- `--hid`：人物ID（必填），如 `H_67890`\n- `--cursor`：分页游标（可选），首次查询不传，翻页时传入上一次响应返回的cursor\n\n## API请求参数\n\n| 参数 | 类型 | 必填 | 说明 |\n|------|------|------|------|\n| pid | string | 是 | 公司ID |\n| hid | string | 是 | 人物ID |\n| cursor | string | 否 | 分页游标，首次请求传空串，翻页时传入上一次响应返回的cursor |\n\n## 响应数据\n\n### 外层结构\n\n- code（integer）：响应码，0 表示成功\n- msg（string）：响应消息\n- data：同事列表数据（见下）\n- fee：计费信息（apiCost 本次扣费、accountBalance 账户余额、uuid 调用标识）\n\n### data 字段\n\n- cursor（string）：下一页游标，为空表示无更多数据\n- list（array）：同事列表\n\n### list 同事字段\n\n- pid（string）：公司ID\n- hid（string）：人物ID\n- titleNames（array[string]）：职位名称列表（如 [\"CTO\"]）\n\nFile v1.0.4:skill-card.md\n\n## Description: <br>\nFind colleagues for a LinkedIn person using a company ID and personnel ID, then return colleague identifiers and job titles for recruiting, sales outreach, and account intelligence workflows. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[upkuajing](https://clawhub.ai/user/upkuajing) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nRecruiters, sales teams, B2B lead-generation specialists, and account-intelligence researchers use this skill to discover colleagues and team relationships from UpKuaJing LinkedIn data when they already have the required company and person identifiers. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: UpKuaJing API calls can incur fees. <br>\nMitigation: Tell the user a query or top-up can cost money, check current pricing through the provided pricing command or link, and wait for explicit confirmation before executing paid actions. <br>\nRisk: Company and person identifiers are sent to UpKuaJing for LinkedIn colleague lookup. <br>\nMitigation: Submit only identifiers needed for the user's approved recruiting, sales, or account-intelligence task, and avoid unnecessary personal data. <br>\nRisk: The API key may be stored in plaintext at ~/.upkuajing/.env. <br>\nMitigation: Protect the local environment file, avoid sharing the key, and prefer secure environment management where available. <br>\n\n\n## Reference(s): <br>\n- [Colleague List API Reference](references/linkedin-person-colleague-list-api.md) <br>\n- [ClawHub skill page](https://clawhub.ai/upkuajing/skills/linkedin-person-colleague) <br>\n- [UpKuaJing homepage](https://www.upkuajing.com) <br>\n- [UpKuaJing Open Platform](https://developer.upkuajing.com/) <br>\n- [UpKuaJing API pricing](https://www.upkuajing.com/web/openapi/price.html) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, JSON, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown guidance with inline shell commands and JSON API results] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Requires Python and UPKUAJING_API_KEY; colleague queries can return paginated results and fee information.] <br>\n\n## Skill Version(s): <br>\n1.0.4 (source: server release metadata and skill metadata) <br>\n\n## Ethical Considerations: <br>\nUsers 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. <br>\n\nFile v1.0.4:requirements.txt\n\nhttpx>=0.23.0\n\nArchive v1.0.1: 9 files, 15765 bytes\n\nFiles: references/linkedin-person-colleague-list-api.md (1210b), requirements.txt (14b), scripts/auth.py (5860b), scripts/common.py (14567b), scripts/linkedin_person_colleague_list.py (1790b), scripts/version_check.py (4933b), skill-card.md (2495b), SKILL.md (7573b), _meta.json (144b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: linkedin-person-colleague\ndescription: \"Find internal colleagues through company‑ID and personnel‑ID on LinkedIn. Map organizational structures and gather contacts for sales outreach and account intelligence.\\n\\nTrigger: LinkedIn colleague lookup, map organizational relationships, internal team discovery, account intelligence research, B2B contact expansion\"\nmetadata: {\"version\":\"1.0.1\",\"homepage\":\"https://www.upkuajing.com\",\"clawdbot\":{\"emoji\":\"🤝\",\"requires\":{\"bins\":[\"python\"],\"env\":[\"UPKUAJING_API_KEY\"]},\"primaryEnv\":\"UPKUAJING_API_KEY\"}}\n---\n\n# LinkedIn Person Colleague Query\n\nQuery colleague data from LinkedIn using the UpKuaJing Open Platform API.\n\n## Overview\n\nThis skill provides access to colleague information from UpKuaJing's LinkedIn data. Given a company ID (pid) and a person ID (hid), it returns the list of colleagues with their person IDs and job titles.\n\n**Prerequisite**: Both the company ID (pid) and person ID (hid) are required as input. If the user does not already have them, use the **linkedin-person-search** skill first to search for the target person and obtain their pid and hid, then proceed with this skill.\n\n## Running Scripts\n\n### Environment Setup\n\n1. **Check Python**: `python --version`\n2. **Install dependencies**: `pip install -r requirements.txt`\n\nScript directory: `scripts/*.py`\nRun example: `python scripts/*.py`\n\n**Important**: Always use direct script invocation like `python scripts/linkedin_person_colleague_list.py`. **Do NOT use** shell compound commands like `cd scripts && python linkedin_person_colleague_list.py`\n\n### Colleague List Query (`linkedin_person_colleague_list.py`)\n- **Return granularity**: Each colleague as one record\n- **Use cases**: Find colleagues of a specific person at a company\n- **Examples**:\n  - \"Find colleagues of person H_67890 at company US_12345\"\n  - \"Get more colleagues using the next page cursor\"\n- **Parameters**: See [Colleague List API](references/linkedin-person-colleague-list-api.md)\n\n## API Key and Top-up\n\nThis skill requires an API key. The API key is stored in the `~/.upkuajing/.env` file:\n```bash\ncat ~/.upkuajing/.env\n```\n**Example file content**:\n```\nUPKUAJING_API_KEY=your_api_key_here\n```\n### **API Key Not Set**\nFirst check if the `~/.upkuajing/.env` file has UPKUAJING_API_KEY;\nIf UPKUAJING_API_KEY is not set, prompt the user to choose:\n1. User has one: User provides it (manually add to ~/.upkuajing/.env file)\n2. 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\nWait for user selection;\n\n### **Account Top-up**\nWhen API response indicates insufficient balance, explain and guide user to top up:\n1. Create top-up order (`auth.py --new_rec_order`)\n2. Based on order response, send payment page URL to user, guide user to open URL and pay, user confirms after successful payment;\n\n### **Get Account Information**\nUse this script to get account information for UPKUAJING_API_KEY: `auth.py --account_info`\n\n## API Key and UpKuaJing Account\n- Newly applied API key: Register and login at [UpKuaJing Open Platform](https://developer.upkuajing.com/), then bind account\n\n## Fees\n\n**All API calls incur fees**, different interfaces have different billing methods.\n\n**Latest pricing**: Users can visit [Detailed Price Description](https://www.upkuajing.com/web/openapi/price.html)\nOr use: `python scripts/auth.py --price_info` (returns complete pricing for all interfaces)\n\n### Query Billing Rules\n\nBilled by **number of calls**, each call returns one page of colleague records:\n- Each API call incurs a fee\n- Use `--cursor` to get additional pages (each page is a separate call)\n- **Before execution:**\n  1. Inform user that this query will incur a fee\n  2. Stop, wait for explicit user confirmation in a separate message, then execute script\n\n### Fee Confirmation Principle\n\n**Any operation that incurs fees must first inform and wait for explicit user confirmation. Do not execute in the same message as the notification.**\n\n## Workflow\n\n### Decision Guide\n\n| User Intent | Use API |\n|-------------|---------|\n| \"Find colleagues of person H_67890 at company US_12345\" | Colleague List Query |\n| User has a person/company name but no pid/hid | linkedin-person-search (find the person and get pid/hid, then use this skill) |\n\n## Usage Examples\n\n### Query Colleague List\n\n**User request**: \"Find colleagues of person H_67890 at company US_12345\"\n```bash\npython scripts/linkedin_person_colleague_list.py --pid US_12345 --hid H_67890\n```\n\n**Get next page** (use cursor returned from previous response):\n```bash\npython scripts/linkedin_person_colleague_list.py --pid US_12345 --hid H_67890 --cursor 'cursor_string_from_previous_response'\n```\n\n## Error Handling\n\n- **API key invalid/non-existent**: Check `UPKUAJING_API_KEY` in `~/.upkuajing/.env` file\n- **Insufficient balance**: Guide user to top up\n- **Invalid parameters**: **Must first check the corresponding API documentation in references/ directory**, get correct parameter names and formats from documentation, do not guess\n\n### API Documentation Reference\n\n- Colleague List: Check [references/linkedin-person-colleague-list-api.md](references/linkedin-person-colleague-list-api.md)\n\n## Best Practices\n\n1. **Check API documentation**:\n   - **Before executing queries, must first check the corresponding API reference documentation**\n   - Check [references/linkedin-person-colleague-list-api.md](references/linkedin-person-colleague-list-api.md)\n   - Do not guess parameter names, get accurate parameter names and formats from documentation\n\n2. **Query parameters**:\n   - Both the company ID (pid) and person ID (hid) are required. If the user provides a person/company name instead, first use **linkedin-person-search** to find the target person and obtain their pid and hid.\n\n3. **Pagination**:\n   - When the response returns a non-empty `cursor`, more data is available\n   - Pass the `cursor` value to get the next page\n   - An empty `cursor` means there is no more data\n\n## Notes\n- Colleague records use `hid` as the person unique identifier; `pid` is the company identifier\n- `titleNames` is a list of job title strings for each colleague\n- File paths use forward slashes on all platforms\n- **Prohibit outputting technical parameter format**: Do not display code-style parameters in responses, convert to natural language\n- **Do not** estimate or guess per-call fees — use `python scripts/auth.py --price_info` to get accurate pricing information\n- **Do not** guess parameter names, get accurate parameter names and formats from documentation\n\n## Related Skills\n\nOther UpKuaJing skills you might find useful:\n\n- linkedin-person-search — Search people from LinkedIn data\n- linkedin-company-search — Search companies from LinkedIn data\n- global-company-person-colleague — Query colleague list from the global company database\n- linkedin-company-employee — Query employee list from LinkedIn data\n- linkedin-person-experience — Query work experience list from LinkedIn data\n- global-company-person-search — Search people from the global company database\n- upkuajing-global-company-people-search — Unified company and people search across all sources\n- upkuajing-contact-info-validity-check — Check contact info validity\n- phone-validity-check — Check phone number validity\n- email-validity-check — Check email address validity\n- domain-validity-check — Check domain validity and security- upkuajing-email-tool — Email verification and sending tool\n- upkuajing-sms-tool — SMS tool\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn76ywjzma121r2rh959ejsf49834c6x\",\n  \"slug\": \"linkedin-person-colleague\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1784189147105\n}\n\nFile v1.0.1:references/linkedin-person-colleague-list-api.md\n\n# 领英同事列表 API 参考\n\n> 根据公司ID和人物ID获取某人的同事信息，支持游标翻页。\n> 接口路径：`POST /agent/search/linkedin/person/colleague/list`\n\n## python脚本参数\n\n- `--pid`：公司ID（必填），如 `US_12345`\n- `--hid`：人物ID（必填），如 `H_67890`\n- `--cursor`：分页游标（可选），首次查询不传，翻页时传入上一次响应返回的cursor\n\n## API请求参数\n\n| 参数 | 类型 | 必填 | 说明 |\n|------|------|------|------|\n| pid | string | 是 | 公司ID |\n| hid | string | 是 | 人物ID |\n| cursor | string | 否 | 分页游标，首次请求传空串，翻页时传入上一次响应返回的cursor |\n\n## 响应数据\n\n### 外层结构\n\n- code（integer）：响应码，0 表示成功\n- msg（string）：响应消息\n- data：同事列表数据（见下）\n- fee：计费信息（apiCost 本次扣费、accountBalance 账户余额、uuid 调用标识）\n\n### data 字段\n\n- cursor（string）：下一页游标，为空表示无更多数据\n- list（array）：同事列表\n\n### list 同事字段\n\n- pid（string）：公司ID\n- hid（string）：人物ID\n- titleNames（array[string]）：职位名称列表（如 [\"CTO\"]）\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nFind internal colleagues through company ID and personnel ID on LinkedIn. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[upkuajing](https://clawhub.ai/user/upkuajing) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nRecruiters, sales teams, and B2B lead generation specialists use this skill to discover colleagues for a known LinkedIn company ID and personnel ID, map team relationships, and support account intelligence workflows. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill uses a paid UpKuaJing API service and each lookup page can incur fees. <br>\nMitigation: Confirm pricing and obtain explicit user approval before running fee-incurring lookup, pagination, API key, or top-up operations. <br>\nRisk: The skill stores and reads an UpKuaJing API key from the user's environment or ~/.upkuajing/.env file. <br>\nMitigation: Keep the API key out of chat output and logs, and only display or edit it when necessary for setup or troubleshooting. <br>\nRisk: The skill makes network requests to UpKuaJing to retrieve LinkedIn colleague data. <br>\nMitigation: Use the skill only when the user is comfortable sending the requested company and personnel identifiers to the UpKuaJing API. <br>\n\n\n## Reference(s): <br>\n- [Colleague List API Reference](references/linkedin-person-colleague-list-api.md) <br>\n- [ClawHub Skill Page](https://clawhub.ai/upkuajing/skills/linkedin-person-colleague) <br>\n- [UpKuaJing Homepage](https://www.upkuajing.com) <br>\n- [UpKuaJing Open Platform](https://developer.upkuajing.com/) <br>\n- [UpKuaJing API Pricing](https://www.upkuajing.com/web/openapi/price.html) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, shell commands, configuration, guidance, JSON] <br>\n**Output Format:** [Markdown guidance with shell commands and JSON API responses] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [API responses include colleague records, pagination cursor data, and fee information when returned by the service.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: artifact metadata and server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers 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. <br>\n\nFile v1.0.1:requirements.txt\n\nhttpx>=0.23.0\n\nArchive v1.0.0: 9 files, 15895 bytes\n\nFiles: references/linkedin-person-colleague-list-api.md (1210b), requirements.txt (14b), scripts/auth.py (5860b), scripts/common.py (14567b), scripts/linkedin_person_colleague_list.py (1790b), scripts/version_check.py (4933b), skill-card.md (2974b), SKILL.md (7389b), _meta.json (144b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: linkedin-person-colleague\ndescription: Official skill for upkuajing (跨境魔方). Query colleague list (同事列表) from LinkedIn data. Get colleague information including person IDs and job titles by company ID (pid) and person ID (hid), with cursor-based pagination. Requires pid and hid — obtain them first via the linkedin-person-search skill.\nmetadata: {\"version\":\"1.0.0\",\"homepage\":\"https://www.upkuajing.com\",\"clawdbot\":{\"emoji\":\"🤝\",\"requires\":{\"bins\":[\"python\"],\"env\":[\"UPKUAJING_API_KEY\"]},\"primaryEnv\":\"UPKUAJING_API_KEY\"}}\n---\n\n# LinkedIn Person Colleague Query\n\nQuery colleague data from LinkedIn using the UpKuaJing Open Platform API.\n\n## Overview\n\nThis skill provides access to colleague information from UpKuaJing's LinkedIn data. Given a company ID (pid) and a person ID (hid), it returns the list of colleagues with their person IDs and job titles.\n\n**Prerequisite**: Both the company ID (pid) and person ID (hid) are required as input. If the user does not already have them, use the **linkedin-person-search** skill first to search for the target person and obtain their pid and hid, then proceed with this skill.\n\n## Running Scripts\n\n### Environment Setup\n\n1. **Check Python**: `python --version`\n2. **Install dependencies**: `pip install -r requirements.txt`\n\nScript directory: `scripts/*.py`\nRun example: `python scripts/*.py`\n\n**Important**: Always use direct script invocation like `python scripts/linkedin_person_colleague_list.py`. **Do NOT use** shell compound commands like `cd scripts && python linkedin_person_colleague_list.py`\n\n### Colleague List Query (`linkedin_person_colleague_list.py`)\n- **Return granularity**: Each colleague as one record\n- **Use cases**: Find colleagues of a specific person at a company\n- **Examples**:\n  - \"Find colleagues of person H_67890 at company US_12345\"\n  - \"Get more colleagues using the next page cursor\"\n- **Parameters**: See [Colleague List API](references/linkedin-person-colleague-list-api.md)\n\n## API Key and Top-up\n\nThis skill requires an API key. The API key is stored in the `~/.upkuajing/.env` file:\n```bash\ncat ~/.upkuajing/.env\n```\n**Example file content**:\n```\nUPKUAJING_API_KEY=your_api_key_here\n```\n### **API Key Not Set**\nFirst check if the `~/.upkuajing/.env` file has UPKUAJING_API_KEY;\nIf UPKUAJING_API_KEY is not set, prompt the user to choose:\n1. User has one: User provides it (manually add to ~/.upkuajing/.env file)\n2. 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\nWait for user selection;\n\n### **Account Top-up**\nWhen API response indicates insufficient balance, explain and guide user to top up:\n1. Create top-up order (`auth.py --new_rec_order`)\n2. Based on order response, send payment page URL to user, guide user to open URL and pay, user confirms after successful payment;\n\n### **Get Account Information**\nUse this script to get account information for UPKUAJING_API_KEY: `auth.py --account_info`\n\n## API Key and UpKuaJing Account\n- Newly applied API key: Register and login at [UpKuaJing Open Platform](https://developer.upkuajing.com/), then bind account\n\n## Fees\n\n**All API calls incur fees**, different interfaces have different billing methods.\n\n**Latest pricing**: Users can visit [Detailed Price Description](https://www.upkuajing.com/web/openapi/price.html)\nOr use: `python scripts/auth.py --price_info` (returns complete pricing for all interfaces)\n\n### Query Billing Rules\n\nBilled by **number of calls**, each call returns one page of colleague records:\n- Each API call incurs a fee\n- Use `--cursor` to get additional pages (each page is a separate call)\n- **Before execution:**\n  1. Inform user that this query will incur a fee\n  2. Stop, wait for explicit user confirmation in a separate message, then execute script\n\n### Fee Confirmation Principle\n\n**Any operation that incurs fees must first inform and wait for explicit user confirmation. Do not execute in the same message as the notification.**\n\n## Workflow\n\n### Decision Guide\n\n| User Intent | Use API |\n|-------------|---------|\n| \"Find colleagues of person H_67890 at company US_12345\" | Colleague List Query |\n| User has a person/company name but no pid/hid | linkedin-person-search (find the person and get pid/hid, then use this skill) |\n\n## Usage Examples\n\n### Query Colleague List\n\n**User request**: \"Find colleagues of person H_67890 at company US_12345\"\n```bash\npython scripts/linkedin_person_colleague_list.py --pid US_12345 --hid H_67890\n```\n\n**Get next page** (use cursor returned from previous response):\n```bash\npython scripts/linkedin_person_colleague_list.py --pid US_12345 --hid H_67890 --cursor 'cursor_string_from_previous_response'\n```\n\n## Error Handling\n\n- **API key invalid/non-existent**: Check `UPKUAJING_API_KEY` in `~/.upkuajing/.env` file\n- **Insufficient balance**: Guide user to top up\n- **Invalid parameters**: **Must first check the corresponding API documentation in references/ directory**, get correct parameter names and formats from documentation, do not guess\n\n### API Documentation Reference\n\n- Colleague List: Check [references/linkedin-person-colleague-list-api.md](references/linkedin-person-colleague-list-api.md)\n\n## Best Practices\n\n1. **Check API documentation**:\n   - **Before executing queries, must first check the corresponding API reference documentation**\n   - Check [references/linkedin-person-colleague-list-api.md](references/linkedin-person-colleague-list-api.md)\n   - Do not guess parameter names, get accurate parameter names and formats from documentation\n\n2. **Query parameters**:\n   - Both the company ID (pid) and person ID (hid) are required. If the user provides a person/company name instead, first use **linkedin-person-search** to find the target person and obtain their pid and hid.\n\n3. **Pagination**:\n   - When the response returns a non-empty `cursor`, more data is available\n   - Pass the `cursor` value to get the next page\n   - An empty `cursor` means there is no more data\n\n## Notes\n- Colleague records use `hid` as the person unique identifier; `pid` is the company identifier\n- `titleNames` is a list of job title strings for each colleague\n- File paths use forward slashes on all platforms\n- **Prohibit outputting technical parameter format**: Do not display code-style parameters in responses, convert to natural language\n- **Do not** estimate or guess per-call fees — use `python scripts/auth.py --price_info` to get accurate pricing information\n- **Do not** guess parameter names, get accurate parameter names and formats from documentation\n\n## Related Skills\n\nOther UpKuaJing skills you might find useful:\n\n- linkedin-person-search — Search people from LinkedIn data\n- linkedin-company-search — Search companies from LinkedIn data\n- global-company-person-colleague — Query colleague list from the global company database\n- linkedin-company-employee — Query employee list from LinkedIn data\n- linkedin-person-experience — Query work experience list from LinkedIn data\n- global-company-person-search — Search people from the global company database\n- upkuajing-global-company-people-search — Unified company and people search across all sources\n- upkuajing-contact-info-validity-check — Check contact info validity\n- upkuajing-email-tool — Email verification and sending tool\n- upkuajing-sms-tool — SMS tool\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn76ywjzma121r2rh959ejsf49834c6x\",\n  \"slug\": \"linkedin-person-colleague\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1783927889731\n}\n\nFile v1.0.0:references/linkedin-person-colleague-list-api.md\n\n# 领英同事列表 API 参考\n\n> 根据公司ID和人物ID获取某人的同事信息，支持游标翻页。\n> 接口路径：`POST /agent/search/linkedin/person/colleague/list`\n\n## python脚本参数\n\n- `--pid`：公司ID（必填），如 `US_12345`\n- `--hid`：人物ID（必填），如 `H_67890`\n- `--cursor`：分页游标（可选），首次查询不传，翻页时传入上一次响应返回的cursor\n\n## API请求参数\n\n| 参数 | 类型 | 必填 | 说明 |\n|------|------|------|------|\n| pid | string | 是 | 公司ID |\n| hid | string | 是 | 人物ID |\n| cursor | string | 否 | 分页游标，首次请求传空串，翻页时传入上一次响应返回的cursor |\n\n## 响应数据\n\n### 外层结构\n\n- code（integer）：响应码，0 表示成功\n- msg（string）：响应消息\n- data：同事列表数据（见下）\n- fee：计费信息（apiCost 本次扣费、accountBalance 账户余额、uuid 调用标识）\n\n### data 字段\n\n- cursor（string）：下一页游标，为空表示无更多数据\n- list（array）：同事列表\n\n### list 同事字段\n\n- pid（string）：公司ID\n- hid（string）：人物ID\n- titleNames（array[string]）：职位名称列表（如 [\"CTO\"]）\n\nFile v1.0.0:skill-card.md\n\n## Description: <br>\nQueries UpKuaJing LinkedIn data for a person's colleagues at a company, returning colleague person IDs and job titles from a required company ID and person ID with cursor-based pagination. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[upkuajing](https://clawhub.ai/user/upkuajing) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nRecruiters, sales teams, B2B lead builders, and account intelligence users can use this skill to find colleagues and team members associated with a known LinkedIn company ID and person ID. It is intended for network expansion, reference research, organizational mapping, and contact-list enrichment after the required identifiers have been obtained. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill uses a local UpKuaJing API key for LinkedIn/company-person lookups. <br>\nMitigation: Set UPKUAJING_API_KEY through a secure environment or secret store and avoid printing ~/.upkuajing/.env in shared logs or chats. <br>\nRisk: Each colleague-list request can incur paid API usage, and top-up helpers may return a payment URL. <br>\nMitigation: Inform the user that a fee may be charged, wait for explicit confirmation before running paid queries, and review any top-up payment URL before paying. <br>\nRisk: Local request and response logs could contain lookup details if API logging is enabled. <br>\nMitigation: Keep API logging disabled unless local request and response records are intentionally needed. <br>\nRisk: The query requires accurate company and person identifiers and cursor handling. <br>\nMitigation: Use the referenced API documentation and obtain the required identifiers before querying; use returned cursors only for intentional pagination. <br>\n\n\n## Reference(s): <br>\n- [Colleague List API reference](references/linkedin-person-colleague-list-api.md) <br>\n- [ClawHub skill page](https://clawhub.ai/upkuajing/skills/linkedin-person-colleague) <br>\n- [UpKuaJing homepage](https://www.upkuajing.com) <br>\n- [UpKuaJing Open Platform](https://developer.upkuajing.com/) <br>\n- [UpKuaJing OpenAPI pricing](https://www.upkuajing.com/web/openapi/price.html) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown guidance with shell commands and JSON API results] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Requires UPKUAJING_API_KEY and may include fee information returned by the UpKuaJing API.] <br>\n\n## Skill Version(s): <br>\n1.0.0 (source: server release metadata and artifact metadata) <br>\n\n## Ethical Considerations: <br>\nUsers 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. <br>\n\nFile v1.0.0:requirements.txt\n\nhttpx>=0.23.0","readmeExcerpt":"Skill: Uncovering LinkedIn colleagues, locating colleagues and team members from LinkedIn data bycompany ID and personnel ID. Helping recruiters, sales teams, and B2B lead-generationspecialists discover team networks, map organizational relationships, and expand contactlists—suitable for network expansion, background research, and account intelligence. Owner: upkuajing Summary: Find internal colleagues through compan","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"cat ~/.upkuajing/.env"},{"language":"text","snippet":"UPKUAJING_API_KEY=your_api_key_here"},{"language":"bash","snippet":"python scripts/error_report.py --params '{\"requestPath\":\"/agent/search/linkedin/person/colleague/list\",\"requestId\":\"f47ac10b58cc4372a5670e02b2c3d479\",\"context\":\"LinkedIn colleague list query failed with a server error\"}'"},{"language":"bash","snippet":"python scripts/linkedin_person_colleague_list.py --pid US_12345 --hid H_67890"},{"language":"bash","snippet":"python scripts/linkedin_person_colleague_list.py --pid US_12345 --hid H_67890 --cursor 'cursor_string_from_previous_response'"},{"language":"bash","snippet":"cat ~/.upkuajing/.env"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: linkedin-person-colleague\ndescription: \"Find internal colleagues through company‑ID and personnel‑ID on LinkedIn. Map organizational structures and gather contacts for sales outreach and account intelligence.\\n\\nTrigger: LinkedIn colleague lookup, map organizational relationships, internal team discovery, account intelligence research, B2B contact expansion\"\nmetadata: {\"version\":\"1.0.5\",\"homepage\":\"https://www.upkuajing.com\",\"clawdbot\":{\"emoji\":\"🤝\",\"requires\":{\"bins\":[\"python\"],\"env\":[\"UPKUAJING_API_KEY\"]},\"primaryEnv\":\"UPKUAJING_API_KEY\"}}\n---\n\n# LinkedIn Person Colleague Query\n\nQuery colleague data from LinkedIn using the UpKuaJing Open Platform API.\n\n## Overview\n\nThis skill provides access to colleague information from UpKuaJing's LinkedIn data. Given a company ID (pid) and a person ID (hid), it returns the list of colleagues with their person IDs and job titles.\n\n**Prerequisite**: Both the company ID (pid) and person ID (hid) are required as input. If the user does not already have them, use the **linkedin-person-search** skill first to search for the target person and obtain their pid and hid, then proceed with this skill.\n\n## Running Scripts\n\n### Environment Setup\n\n1. **Check Python**: `python --version`\n2. **Install dependencies**: `pip install -r requirements.txt`\n\nScript directory: `scripts/*.py`\nRun example: `python scripts/*.py`\n\n**Important**: Always use direct script invocation like `python scripts/linkedin_person_colleague_list.py`. **Do NOT use** shell compound commands like `cd scripts && python linkedin_person_colleague_list.py`\n\n### Colleague List Query (`linkedin_person_colleague_list.py`)\n- **Return granularity**: Each colleague as one record\n- **Use cases**: Find colleagues of a specific person at a company\n- **Examples**:\n  - \"Find colleagues of person H_67890 at company US_12345\"\n  - \"Get more colleagues using the next page cursor\"\n- **Parameters**: See [Colleague List API](references/linkedin-person-colleague-list-api.md)\n\n## API Key and Top-up\n\nThis skill requires an API key. The API key is stored in the `~/.upkuajing/.env` file:\n```bash\ncat ~/.upkuajing/.env\n```\n**Example file content**:\n```\nUPKUAJING_API_KEY=your_api_key_here\n```\n### **API Key Not Set**\nFirst check if the `~/.upkuajing/.env` file has UPKUAJING_API_KEY;\nIf UPKUAJING_API_KEY is not set, prompt the user to choose:\n1. User has one: User provides it (manually add to ~/.upkuajing/.env file)\n2. 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\nWait for user selection;\n\n### **Account Top-up**\nWhen API response indicates insufficient balance, explain and guide user to top up:\n1. Create top-up order (`auth.py --new_rec_order`)\n2. Based on order response, send payment page URL to user, guide user to open URL and pay, user confirms after successful payment;\n\n### **Get Account Information**\nUse this script to get account information for UPKUAJING_API_KEY: `auth.py -"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn76ywjzma121r2rh959ejsf49834c6x\",\n  \"slug\": \"linkedin-person-colleague\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1787563673698\n}"},{"path":"references/linkedin-person-colleague-list-api.md","content":"# 领英同事列表 API 参考\n\n> 根据公司ID和人物ID获取某人的同事信息，支持游标翻页。\n> 接口路径：`POST /agent/search/linkedin/person/colleague/list`\n\n## python脚本参数\n\n- `--pid`：公司ID（必填），如 `US_12345`\n- `--hid`：人物ID（必填），如 `H_67890`\n- `--cursor`：分页游标（可选），首次查询不传，翻页时传入上一次响应返回的cursor\n\n## API请求参数\n\n| 参数 | 类型 | 必填 | 说明 |\n|------|------|------|------|\n| pid | string | 是 | 公司ID |\n| hid | string | 是 | 人物ID |\n| cursor | string | 否 | 分页游标，首次请求传空串，翻页时传入上一次响应返回的cursor |\n\n## 响应数据\n\n### 外层结构\n\n- code（integer）：响应码，0 表示成功\n- msg（string）：响应消息\n- data：同事列表数据（见下）\n- fee：计费信息（apiCost 本次扣费、accountBalance 账户余额、uuid 调用标识）\n\n### data 字段\n\n- cursor（string）：下一页游标，为空表示无更多数据\n- list（array）：同事列表\n\n### list 同事字段\n\n- pid（string）：公司ID\n- hid（string）：人物ID\n- titleNames（array[string]）：职位名称列表（如 [\"CTO\"]）"},{"path":"references/skill-error-report-api.md","content":"# Agent调用Skill异常上报 API 参考\n\n> 上报 Agent 调用 Skill 异常，用于平台侧问题追踪与优化。异常上报不产生查询费用。\n> 接口路径：`POST /agent/skill/error/report`\n> 鉴权：需要 Bearer 令牌（UPKUAJING_API_KEY）\n\n## python脚本参数\n\n- `--params`：JSON格式的上报参数（必填）\n- 未传 `skillId`/`skillVersion` 时，脚本会自动从当前 Skill 目录名与 SKILL.md 读取并填充\n- 必填参数：`skillId`、`skillVersion`、`requestId`、`requestPath`、`context`；其中 `requestId` 从出问题的请求响应（ApiResp.requestId）中获取\n\n## API请求参数\n\n| 参数 | 类型 | 必填 | 说明 |\n|------|------|------|------|\n| skillId | string | 是 | Skill 标识（最大128字符），如\"customs-analysis-area\" |\n| skillVersion | string | 是 | Skill 版本（最大32字符） |\n| agentName | string | 否 | Agent 名称（最大128字符） |\n| modelName | string | 否 | 模型名称（最大128字符） |\n| requestPath | string | 是 | 出问题的站内接口路径，以 / 开头（最大255字符），如\"/agent/customs/analysis/area\" |\n| requestId | string | 是 | 全请求唯一关联号（最大128字符），取失败请求响应中的 requestId |\n| requestTime | long | 否 | 请求发起时间戳（毫秒，≥0） |\n| requestParams | object | 否 | 请求参数（原始入参，敏感字段会自动脱敏；序列化后≤64KB） |\n| responseData | object | 否 | 响应数据（异常发生时的返回内容，敏感字段会自动脱敏；序列化后≤64KB） |\n| durationMs | long | 否 | 本次调用耗时（毫秒，≥0） |\n| context | string | 是 | 异常上下文（堆栈/错误信息，用于定位根因，最大2000字符） |\n\n## 响应数据\n\n### 外层结构\n\n- code（integer）：状态码，0 表示成功\n- msg（string）：提示信息\n- requestId（string）：全请求唯一关联号（32位无横线，与 MDC traceId 同值）\n\n### data 字段\n\n| 字段 | 类型 | 说明 |\n|------|------|------|\n| reportId | long | 上报记录 ID |"},{"path":"skill-card.md","content":"## Description:\n\nFind internal colleagues through company ID and personnel ID on LinkedIn to map organizational structures and gather contacts for sales outreach and account intelligence.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[upkuajing](https://clawhub.ai/user/upkuajing)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal recruiters, sales teams, and B2B lead-generation specialists use this skill to look up colleagues for a known LinkedIn company ID and person ID, map team networks, and expand account-intelligence contact lists.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The security summary flags paid-account credentials, top-up orders, and telemetry for review.\n\nMitigation: Use a safer secret mechanism for the API key where possible, avoid printing or sharing ~/.upkuajing/.env, and confirm paid queries or top-up actions before execution.\n\nRisk: LinkedIn colleague lookup can involve personal and organizational contact data for sales outreach or contact expansion.\n\nMitigation: Confirm the user's privacy, legal, and policy basis before collecting, using, or sharing returned colleague data.\n\nRisk: Error reporting sends troubleshooting context to the platform and may include request metadata.\n\nMitigation: Ask for user confirmation before reporting abnormal calls and avoid including unnecessary sensitive context.\n\n## Reference(s):\n\n- [Colleague List API Reference](references/linkedin-person-colleague-list-api.md)\n- [Skill Error Report API Reference](references/skill-error-report-api.md)\n- [UpKuaJing Homepage](https://www.upkuajing.com)\n- [UpKuaJing Open Platform](https://developer.upkuajing.com/)\n- [UpKuaJing API Pricing](https://www.upkuajing.com/web/openapi/price.html)\n- [ClawHub Skill Page](https://clawhub.ai/upkuajing/skills/linkedin-person-colleague)\n\n## Skill Output:\n\n**Output Type(s):** [JSON, Shell commands, Guidance]\n\n**Output Format:** [Markdown guidance with shell commands and JSON API responses]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Requires UPKUAJING_API_KEY and explicit confirmation before fee-incurring calls.]\n\n## Skill Version(s):\n\n1.0.5 (source: server release evidence and skill metadata)\n\n## Ethical Considerations:\n\nUsers 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."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":1581,"uniquenessScore":36,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T19:39:07.665Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T19:39:07.665Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-12T00:35:23.335Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"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!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"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","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}