Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计提醒

linkdapi-officiallinkdapi 官方

Agent Skill

linkdapi-official 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

9,932

周安装

418

GitHub Stars

公开资料未说明

下载量

3,478
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install linkdapi-official

简介

集成 LinkdAPI 的 OpenClaw 技能。

  • 包含 50 多个端点和多语言 SDK。
  • 涵盖身份验证和速率限制说明。
  • 需提供有效凭证方可调用。适用宿主包括 OpenClaw,接入前应确认版本、权限和运行环境要求。
  • linkdapi-official 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

name
linkdapi-openclaw
description
Complete LinkdAPI integration OpenClaw skill. Includes all 50+ endpoints, Python/Node.js/Go SDKs, authentication, rate limits, and real-world examples. Use this skill whenever the user wants to look up LinkedIn profiles, search LinkedIn people or companies, enrich leads, research LinkedIn jobs, scrape LinkedIn posts or articles, do B2B prospecting, get LinkedIn company data, or call any LinkedIn data API. Always use this skill for ANY LinkedIn data task, even if the user just says "find me on LinkedIn" or "look up this company" or "search LinkedIn for engineers in Berlin".
version
1.0.0
author
LinkdAPI Team

LinkdAPI Skill — LinkedIn Data API

Use this skill to access LinkedIn professional data via the LinkdAPI REST API.

Full endpoint reference with params, enums, and response schemas → references/api-ref.md Structured endpoint manifest (JSON) → references/skills.json

⚠️ Authentication — READ FIRST

Value
Auth headerX-linkdapi-apikey
Base URLhttps://linkdapi.com
Env varLINKDAPI_KEY
curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/profile/overview?username=ryanroslansky" | jq .

NEVER use x-api-key or Authorization: Bearer — they will return 401. The only correct header is X-linkdapi-apikey.


Core Concepts

TermMeaningHow to Get
usernameLinkedIn vanity slug (linkedin.com/in/USERNAME)From the URL
urnInternal LinkedIn ID (ACoAAAA...)From profile/overview response
id (company)Numeric LinkedIn company IDFrom companies/company/info or companies/name-lookup
jobIdNumeric LinkedIn job IDFrom job search results
geoUrnLocation filter IDFrom geos/name-lookup
cursorPagination tokenFrom previous response

Always get URN first when working with profile endpoints that require it.


Endpoint Quick Reference

Profile — /api/v1/profile/

EndpointParamsUse
overviewusernameBasic info + URN ← start here
detailsurnPositions, education, languages
contact-infousernameEmail, phone, websites
abouturnAbout section
fullusername or urnEverything in 1 request
full-experienceurnComplete work history
certificationsurnCertifications
educationurnEducation history
skillsurnSkills + endorsements
social-matrixusernameFollowers + connections
recommendationsurnGiven + received
similarurnSimilar profiles
reactionsurn, cursorProfile reactions
interestsurnInterests
servicesurnServices offered
username-to-urnusernameUsername → URN

Companies — /api/v1/companies/

EndpointParamsUse
name-lookupquerySearch by name
company/infoid or nameCompany details
company/info-v2idExtended info
company/similaridSimilar companies
company/employees-dataidHeadcount + distribution
company/affiliated-pagesidSubsidiaries
company/postsid, startCompany posts
company/universal-name-to-iduniversalNameUniversal name → ID
jobscompanyIDs, startJob listings

Jobs — /api/v1/jobs/

EndpointParamsUse
searchkeyword, location, timePosted, workArrangement, geoId, companyIds, jobTypes, experience, salary, startV1 job search
job/detailsjobIdJob info (open only)
job/details-v2jobIdJob info (all statuses)
job/similarjobIdSimilar jobs
job/people-also-viewedjobIdRelated jobs
job/hiring-teamjobId, startHiring team
posted-by-profileprofileUrn, start, countJobs by a person

Search — /api/v1/search/

EndpointKey ParamsUse
peoplekeyword, title, currentCompany, geoUrn, industry, firstName, lastName, start, countFind professionals
companieskeyword, geoUrn, companySize, hasJobs, industry, start, countFind companies
postskeyword, sortBy, datePosted, authorJobTitle, fromOrganization, contentType, startFind posts
jobskeyword, workplaceTypes, datePosted, easyApply, companies, locations, experience, salary, under10Applicants, start, countV2 job search
serviceskeyword, geoUrn, serviceCategory, profileLanguage, start, countService providers
schoolskeyword, start, countSchools

Posts — /api/v1/posts/

EndpointParamsUse
featuredurnFeatured posts
allurn, cursor, startAll posts paginated
infournSingle post
commentsurn, start, count, cursorComments
likesurn, startLikes

Comments — /api/v1/comments/

EndpointParamsUse
allurn, cursorAll comments
likesurn, startComment likes

Articles — /api/v1/articles/

EndpointParamsUse
allurn, startAll articles
article/infourlArticle details
article/reactionsurn, startReactions

Lookups

PathParamsUse
/api/v1/geos/name-lookupquery→ geoUrn for location filters
/api/v1/g/title-skills-lookupquery→ skill/title IDs
/api/v1/g/services-lookupquery→ service category IDs

Services — /api/v1/services/

EndpointParamsUse
service/detailsvanitynameService page
service/similarvanitynameSimilar services

System

PathUse
status/Health check (no auth)

Common Workflows

Lead Enrichment (Profile Research)

# Step 1: Get URN
PROFILE=$(curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/profile/overview?username=TARGET_USERNAME")
URN=$(echo $PROFILE | jq -r '.data.urn')
echo "$(echo $PROFILE | jq -r '.data.fullName') → $URN"

# Step 2: Enrich in parallel
curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/profile/full-experience?urn=$URN" | jq '.data.experience[0]' &
curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/profile/skills?urn=$URN" | jq '.data.skills[:5]' &
curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/profile/contact-info?username=TARGET_USERNAME" | jq '.data' &
wait

# Or use full endpoint (one request, more credits)
curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/profile/full?username=TARGET_USERNAME" | jq .data

Company Research

CO_ID=$(curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/companies/company/info?name=google" | jq -r '.data.id')

curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/companies/company/employees-data?id=$CO_ID" | jq .data &
curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/companies/company/similar?id=$CO_ID" | jq .data &
curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/companies/jobs?companyIDs=$CO_ID&start=0" | jq .data &
wait

ICP People Search

GEO_URN=$(curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/geos/name-lookup?query=San+Francisco" | jq -r '.data[0].urn')

curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/search/people?keyword=VP+Sales&title=VP+Sales&geoUrn=$GEO_URN&start=0" \
  | jq '.data.items'

Job Market Intel

# V2 (richest filters)
curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/search/jobs?keyword=Software+Engineer&workplaceTypes=remote&datePosted=1week&easyApply=true" \
  | jq .data

# V1 (classic, location string)
curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/jobs/search?keyword=Marketing+Manager&location=London&timePosted=1week&workArrangement=hybrid" \
  | jq .data

Content Research

# Posts by a profile
curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/posts/all?urn=$URN&start=0" | jq .data

# Search posts by keyword
curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/search/posts?keyword=AI+marketing&sortBy=date_posted&datePosted=past-week" \
  | jq .data

# Articles
curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/articles/all?urn=$URN&start=0" | jq .data

Error Handling

All responses: { "success": bool, "statusCode": int, "message": string, "errors": null|string, "data": ... }

RESULT=$(curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
  "https://linkdapi.com/api/v1/profile/overview?username=someuser")

if echo $RESULT | jq -e '.success == true' > /dev/null 2>&1; then
  echo "OK: $(echo $RESULT | jq -r '.data.fullName')"
else
  CODE=$(echo $RESULT | jq -r '.statusCode')
  MSG=$(echo $RESULT | jq -r '.message')
  echo "Error $CODE: $MSG"
  # 401=invalid key | 404=not found | 429=rate limited (retry with backoff) | 500=server error
  [ "$CODE" = "429" ] && sleep 5 && echo "Retry after backoff"
fi

B2B Marketing Playbook

GoalEndpoints
Lead enrichmentprofile/overviewprofile/full-experience + profile/skills + profile/contact-info
ICP targetinggeos/name-lookupsearch/people with title + currentCompany + geoUrn
Competitor intelcompanies/company/posts or search/posts?fromOrganization=ID
Hiring signalscompanies/jobs?companyIDs=ID reveals growth areas
Content inspirationposts/all on top voices + posts/info for engagement stats
Warm outreach prepprofile/recommendations + posts/all before messaging
Job trigger eventsjobs/posted-by-profile to find who is hiring actively

Reference Files

  • references/api-ref.md — Full parameter schemas, all enums, and response field descriptions for every endpoint. Read this when you need exact param names or response field shapes.
  • references/skills.json — Machine-readable manifest of all endpoints (for dynamic tooling or integrations).

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

96.77%
按下载量换算3,366

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills