Help us improve
Share bugs, ideas, or general feedback.
From UnifAPI
Read-only LinkedIn data via UnifAPI — company pages, follower/employee counts, jobs, people, posts, and member insights. Use for account research, competitor profiling, or buying signals.
npx claudepluginhub unifapi-agent/agents --plugin unifapiHow this skill is triggered — by the user, by Claude, or both
Slash command
/unifapi:linkedinThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The deterministic read path for public **LinkedIn** data through UnifAPI. This is
Automates LinkedIn actions via CLI: fetch profiles, search people/companies, send messages, manage connections, create posts, and use Sales Navigator for outreach workflows.
Scrapes LinkedIn post engagers (commenters + reactors) from profiles, deduplicates, and enriches with full profile data and company websites. Triggers on post engagement lead gen queries.
Builds a structured B2B account brief from a company's public LinkedIn presence — page, posts, open jobs, employees, and visible profiles. Useful when a seller needs pre-call research, buying committee identification, or hiring signal analysis.
Share bugs, ideas, or general feedback.
The deterministic read path for public LinkedIn data through UnifAPI. This is
a Data Skill: it does not run a marketing job on its own — it names the
concrete linkedin/... operations, response shapes, and gotchas so any
B2B-first workflow (account research, news signals, buying signals, competitor
profiling) reads from one known recipe instead of rediscovering the surface each
time.
Read-only — eyes, not hands. It researches public LinkedIn data and returns cited records; it never connects, messages, or applies, and UnifAPI never holds LinkedIn credentials.
unifapi skill for live evidenceConnect once through the shared unifapi skill (OAuth MCP), then call the
operations below. Companies are keyed by their public {slug} (the vanity
segment of the company URL) and people by their public {username} — read
both from the LinkedIn URL, not a numeric id. Keep any billing metadata so the
output can state record cost.
Single-entity endpoints return the object in data:
{
"request_id": "unif_...",
"data": {},
"billing": { "records_charged": 1, "balance_remaining": 99 }
}
List endpoints return an array in data plus pagination:
{
"request_id": "unif_...",
"data": [],
"pagination": { "has_more": false, "next_cursor": null },
"billing": { "records_charged": 1 }
}
When pagination.has_more is true, pass pagination.next_cursor as the next
request's cursor. Always preserve billing when reporting cost.
| Need | Operation |
|---|---|
| Company page | linkedin/companies/{slug} |
| Company headcount signal | linkedin/companies/{slug}/job-count · .../jobs |
| Company people | linkedin/companies/{slug}/people |
| Member insights | linkedin/companies/{slug}/member-insights |
| Company posts | linkedin/companies/{slug}/posts |
| Person profile | linkedin/users/{username} · .../about · .../experience |
| Person reach | linkedin/users/{username}/follower-count |
| Person posts / reactions | linkedin/users/{username}/posts · .../reactions |
| Search people | linkedin/search/people (?title=¤t_company=&industry=) |
| Search jobs / posts | linkedin/search/jobs · linkedin/search/posts |
| Job / post by id | linkedin/jobs/{id} · linkedin/posts/{id} (.../comments) |
| Resolve a geocode / industry | linkedin/search/locations · linkedin/search/industries |
Need a field not listed here? Use the unifapi skill's get_operation to read
the exact schema before calling — but pick the operation from this table, don't
discover blind.
The deterministic recipes. Pick the one that matches the job; each names exactly what to call.
{slug} from its LinkedIn URL, then
call linkedin/companies/{slug} for follower_count, employee_count,
industries, and headquarters.linkedin/companies/{slug}/job-count (returns a single total) and
linkedin/companies/{slug}/jobs for the open roles — a rising count or a
cluster of senior roles is a growth/priority signal.linkedin/companies/{slug}/people and
linkedin/companies/{slug}/member-insights, or narrow with
linkedin/search/people?current_company=...&title=... for specific roles.linkedin/users/{username} plus .../about and
.../experience; .../follower-count for reach (a separate
LinkedinFollowerStats object); .../posts for what they publish.linkedin/companies/{slug}/posts or
linkedin/users/{username}/posts; each LinkedinPost carries like_count,
comment_count, and share_count. Page via next_cursor.linkedin/search/people|jobs|posts with filters;
resolve a geocode_location via linkedin/search/locations and an industry
id via linkedin/search/industries first.billing.records_charged (or estimate when billing
metadata is absent).LinkedinCompany — keyed by {slug}. follower_count, employee_count,
employee_count_range, industries, headquarters, is_verified.LinkedinUser — keyed by {username}. Profile flags at top level:
is_open_to_work, is_hiring, is_top_voice, is_creator, is_premium.
Follower/connection counts are not here — read them from
.../follower-count (LinkedinFollowerStats: follower_count,
connection_count).LinkedinPost — like_count, comment_count, share_count, reactions,
author, post_type.LinkedinJob — title, location, salary, level, employment_type,
listed_at, company. LinkedinJobCount is just { total }.{slug}, people by {username} — both read from the
public LinkedIn URL, never a numeric id.linkedin/users/{username}/follower-count, not the base profile object.linkedin/search/people needs at least one filter — there is no all-of-LinkedIn
dump.billing.truncated_due_to_balance — when true the page is partial, so top up
before trusting any count computed from it.Return the records the calling workflow needs, each cited to its company,
person, or post, plus a one-line cost note (records_charged). When this skill
is used directly, a compact account brief is the default:
**{Company}** — {followers} followers, {employees} employees, {industry}. Open roles: {N} ({trend}). Recent posts: {engagement}. Likely buyers: {names/titles}. Evidence: {URLs}. Records: ~{N}.
get_operation.