Linkedin skill for Claude Code & Codex

Agent skill

by unifapi-agent in unifapi-agent/agents

When a workflow needs public LinkedIn data through UnifAPI — company pages, follower/employee counts, open jobs and job-count, member insights, people, posts, or engagement.

MITAuto-check passedSales & Support

Install Linkedin

skills CLI

$ npx skills add unifapi-agent/agents --skill linkedin -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install unifapi-agent/agents linkedin --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/unifapi-agent/agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/linkedin-agent/linkedin .claude/skills/linkedin && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "linkedin" agent skill from https://github.com/unifapi-agent/agents/tree/main/skills/linkedin-agent/linkedin into .claude/skills/linkedin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/unifapi-agent/agents/tree/main/skills/linkedin-agent/linkedin

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add unifapi-agent/agents --skill linkedin -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install unifapi-agent/agents linkedin --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/unifapi-agent/agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/linkedin-agent/linkedin .agents/skills/linkedin && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "linkedin" agent skill from https://github.com/unifapi-agent/agents/tree/main/skills/linkedin-agent/linkedin into .agents/skills/linkedin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add unifapi-agent/agents --skill linkedin -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install unifapi-agent/agents linkedin --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/unifapi-agent/agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/linkedin-agent/linkedin .cursor/skills/linkedin && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "linkedin" agent skill from https://github.com/unifapi-agent/agents/tree/main/skills/linkedin-agent/linkedin into .cursor/skills/linkedin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/unifapi-agent/agents.git --path skills/linkedin-agent/linkedin

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add unifapi-agent/agents --skill linkedin -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install unifapi-agent/agents linkedin --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/unifapi-agent/agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/linkedin-agent/linkedin .gemini/skills/linkedin && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "linkedin" agent skill from https://github.com/unifapi-agent/agents/tree/main/skills/linkedin-agent/linkedin into .gemini/skills/linkedin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install unifapi-agent/agents linkedin

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add unifapi-agent/agents --skill linkedin -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/unifapi-agent/agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/linkedin-agent/linkedin .github/skills/linkedin && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "linkedin" agent skill from https://github.com/unifapi-agent/agents/tree/main/skills/linkedin-agent/linkedin into .github/skills/linkedin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add unifapi-agent/agents --skill linkedin -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install unifapi-agent/agents linkedin --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/unifapi-agent/agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/linkedin-agent/linkedin .opencode/skills/linkedin && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "linkedin" agent skill from https://github.com/unifapi-agent/agents/tree/main/skills/linkedin-agent/linkedin into .opencode/skills/linkedin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: linkedin
GitHub stars: 587
Token cost: ~1.9k tokens
SKILL.md length: 646 words
Files: 2
Skills in repo: 47
Repo updated: Sep 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

When a workflow needs public LinkedIn data through UnifAPI — company pages, follower/employee counts, open jobs and job-count, member insights, people, posts, or engagement.

Works in 7 steps: Resolve an account. Take the company… → Size hiring as an investment signal. Call → Map the buying committee. Call… → …
Tasks that involve Sales call preparation
SKILL.md covers Use the unifapi skill for live…, Response contract, Core operations and Workflow, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Linkedin is an agent skill from unifapi-agent/agents. When a workflow needs public LinkedIn data through UnifAPI — company pages, follower/employee counts, open jobs and job-count, member insights, people, posts, or engagement. Also use on "research this company on LinkedIn," "who works at," "open roles at," "LinkedIn profile for," "company posts," or when another skill (account research, news signal, buying signal, competitor profiling) needs the deterministic LinkedIn read path. Connect via the unifapi skill first. Read-only research, never connects or messages.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).

It sits in Sales & Support, covering Sales call preparation and Resume and CV writing. It works with LinkedIn. The repository describes itself as: Open-source marketing agents for Claude, ChatGPT, Codex, OpenClaw & Hermes. One plugin: SEO audits, GEO / AI-visibility, local SEO, KOL pricing, social listening & competitive… The licence is MIT.

When your agent uses it

Tasks that involve Sales call preparation
Tasks that involve Resume and CV writing

Example prompts

“research this company on LinkedIn,”
“who works at,”
“open roles at,”
“/linkedin”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

Resolve an account. Take the company {slug} from its LinkedIn URL, then
Size hiring as an investment signal. Call
Map the buying committee. Call linkedin/companies/{slug}/people and
Read a person. Call linkedin/users/{username} plus .../about and
Read posts and engagement. Call linkedin/companies/{slug}/posts or
Search the surface. Use linkedin/search/people|jobs|posts with filters;
Cite everything. Every claim ties back to the company, person, or post it

What it can do on your machine

Read from SKILL.md and the folder at commit fb53247. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Linkedin loads about 1.9k tokens when it runs. Until then it costs about 132 tokens; SKILL.md has 646 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~132
When it runs · the whole SKILL.md, loaded when a task matches: ~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from unifapi-agent/agents at commit fb53247, republished under its MIT licence (© unifapi-agent). 646 words, ~1,889 tokens.

Download SKILL.mdSave it as .claude/skills/linkedin/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: linkedin
description: When a workflow needs public LinkedIn data through UnifAPI — company pages, follower/employee counts, open jobs and job-count, member insights, people, posts, or engagement. Also use on "research this company on LinkedIn," "who works at," "open roles at," "LinkedIn profile for," "company posts," or when another skill (account research, news signal, buying signal, competitor profiling) needs the deterministic LinkedIn read path. Connect via the `unifapi` skill first. Read-only research, never connects or messages.
license: MIT
metadata.author: UnifAPI
metadata.version: 1.0.0
metadata.homepage: https://unifapi.com/agents/linkedin
metadata.source: https://github.com/unifapi-agent/agents

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.

Use the `unifapi` skill for live evidence

Connect 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.

Response contract

Single-entity endpoints return the object in data:

json

{
  "request_id": "unif_...",
  "data": {},
  "billing": { "records_charged": 1, "balance_remaining": 99 }
}

List endpoints return an array in data plus pagination:

json

{
  "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.

Core operations

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=&current_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.

Workflow

The deterministic recipes. Pick the one that matches the job; each names exactly what to call.

Resolve an account. Take the company {slug} from its LinkedIn URL, then call linkedin/companies/{slug} for follower_count, employee_count, industries, and headquarters.
Size hiring as an investment signal. Call 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.
Map the buying committee. Call linkedin/companies/{slug}/people and linkedin/companies/{slug}/member-insights, or narrow with linkedin/search/people?current_company=...&title=... for specific roles.
Read a person. Call linkedin/users/{username} plus .../about and .../experience; .../follower-count for reach (a separate LinkedinFollowerStats object); .../posts for what they publish.
Read posts and engagement. Call linkedin/companies/{slug}/posts or linkedin/users/{username}/posts; each LinkedinPost carries like_count, comment_count, and share_count. Page via next_cursor.
Search the surface. Use linkedin/search/people|jobs|posts with filters; resolve a geocode_location via linkedin/search/locations and an industry id via linkedin/search/industries first.
Cite everything. Every claim ties back to the company, person, or post it came from; report billing.records_charged (or estimate when billing metadata is absent).

Show full SKILL.md (208 more words)Show less

Shape notes

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 }.

Gotchas

Companies are keyed by {slug}, people by {username} — both read from the public LinkedIn URL, never a numeric id.
Follower and connection counts come from 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.
A low balance can silently truncate list pages: check billing.truncated_due_to_balance — when true the page is partial, so top up before trusting any count computed from it.

Output

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:

markdown

**{Company}** — {followers} followers, {employees} employees, {industry}. Open roles: {N} ({trend}). Recent posts: {engagement}. Likely buyers: {names/titles}. Evidence: {URLs}. Records: ~{N}.

linkedin-account-research, account-news-signals (Lead & Company Research) — turn this read path into account briefs and news-tied signals.
buying-signal-monitor (Social Selling), competitor-profiling (Competitive Intelligence) — B2B intent and competitor work on top of LinkedIn reads.
unifapi — the shared data skill: connect MCP and look up exact schemas with get_operation.

Files

SKILL.md and 1 other file in skills/linkedin-agent/linkedin of unifapi-agent/agents.

SKILL.md
README.md

Open the folder on GitHubat commit fb53247

Compare with similar skills

Linkedin next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Linkedin compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Linkedin this skillunifapi-agent/agents	587	—	~1.9k	Automated safety check: Pass	MIT	1 mo ago
Company Researchliangdabiao/exa-research-mcp-skill	110	1 repos	~452	Automated safety check: Pass	None	2 mo ago
Account Researchexplorium-ai/gtm-skills	163	—	~2.8k	Automated safety check: Pass	MIT	13 days ago
Enrich Contactexplorium-ai/gtm-skills	163	—	~1k	Automated safety check: Pass	MIT	13 days ago
Linkedin Outbound AngleOthmane-Khadri/YALC-the-GTM-operating-system	317	—	~3.5k	Automated safety check: Pass	MIT	1 mo ago
Referral IntroTheCraigHewitt/skills	157	—	~6.7k	Automated safety check: Pass	MIT	4 mo ago

Similar skills

Company Research
liangdabiao/exa-research-mcp-skill
Company research using Exa search. An agent skill from liangdabiao/exa-research-mcp-skill.
110 GitHub starsUsed in 1 repo~452 tokens
Sales & SupportAuto-check passed
Account Research
explorium-ai/gtm-skills
Account research skill for Claude Code and Codex: generate a high-signal company intelligence brief including firmographics, technographics, funding history, hiring signals, business events, recent…
163 GitHub stars~2.8k tokensUpdated 13 days ago
Sales & SupportAuto-check passed
Enrich Contact
explorium-ai/gtm-skills
Contact enrichment skill for Claude Code and Codex: look up a B2B prospect's full professional profile including work email, phone number, LinkedIn profile, title, seniority, department, and company…
163 GitHub stars~1k tokensUpdated 13 days ago
Business, Finance & HRAuto-check passed
Linkedin Outbound Angle
Othmane-Khadri/YALC-the-GTM-operating-system
Analyzes a LinkedIn profile and identifies the perfect outbound attack angle for personalized outreach.
317 GitHub stars~3.5k tokensUpdated 1 mo ago
Marketing & SEOAuto-check passed
Referral Intro
TheCraigHewitt/skills
When the user wants to ask for a warm introduction, build a referral program, or systematize their referral channel.
157 GitHub stars~6.7k tokensUpdated 4 mo ago
Sales & SupportAuto-check passed
Contact Hunter
OneWave-AI/claude-skills
Search and extract contact information for people or companies including names, phone numbers, emails, job titles, and LinkedIn profiles.
323 GitHub stars~767 tokensUpdated 5 days ago
Marketing & SEOAuto-check passed

More from unifapi-agent/agents

All 47 skills in this repo

LLM Mention Tracking
unifapi-agent/agents
When the user wants to track how often their brand or domain gets mentioned across ChatGPT and AI search engines over a set of prompts, and how that share of voice compares to named competitors over…
587 GitHub stars~1.8k tokensUpdated 1 mo ago
Auto-check passed
Buying Signal Monitor
unifapi-agent/agents
When a seller or SDR wants to catch public buying intent on X/Twitter and LinkedIn — someone asking for a tool they sell, complaining about or switching off a competitor, or hiring for a role that…
587 GitHub stars~2.4k tokensUpdated 1 mo ago
Auto-check passed
Customer Research
unifapi-agent/agents
When the user wants to research customers from public communities, or synthesize customer language, pains, and objections.
587 GitHub stars~2.1k tokensUpdated 1 mo ago
Auto-check passed
Keyword Research
unifapi-agent/agents
When the user wants to research keywords, find keyword opportunities, run a keyword gap analysis, build topic clusters, or compare what competitors rank for.
587 GitHub stars~2.7k tokensUpdated 1 mo ago
Auto-check passed
Schema
unifapi-agent/agents
When the user wants to add, fix, or optimize schema markup and structured data on their site.
587 GitHub stars~2.1k tokensUpdated 1 mo ago
Auto-check passed
SEO Audit
unifapi-agent/agents
When the user wants to audit, review, or diagnose SEO issues on their site.
587 GitHub stars~3.4k tokensUpdated 1 mo ago
Auto-check passed

Works with

Questions about Linkedin

What does Linkedin do?

When a workflow needs public LinkedIn data through UnifAPI — company pages, follower/employee counts, open jobs and job-count, member insights, people, posts, or engagement. Linkedin is an agent skill from unifapi-agent/agents. When a workflow needs public LinkedIn data through UnifAPI — company pages, follower/employee counts, open jobs and job-count, member insights, people, posts, or engagement.

When should I use Linkedin?

Linkedin fits situations like: tasks that involve Sales call preparation; tasks that involve Resume and CV writing.

How do I install Linkedin in Claude Code?

Run `npx skills add unifapi-agent/agents --skill linkedin -a claude-code`. Or copy the skill folder (skills/linkedin-agent/linkedin in unifapi-agent/agents) into .claude/skills/linkedin in your project. Claude Code loads it when a task matches its description.

How do I install Linkedin in Codex?

Run `npx skills add unifapi-agent/agents --skill linkedin -a codex`. Or copy the skill folder (skills/linkedin-agent/linkedin in unifapi-agent/agents) into .agents/skills/linkedin in your project. Codex loads it when a task matches its description.

Can I use Linkedin in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add unifapi-agent/agents --skill linkedin -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linkedin, .gemini/skills/linkedin, .github/skills/linkedin and .opencode/skills/linkedin in your project.

What does Linkedin need to run?

SKILL.md names no scripts, command-line tools or credentials: Linkedin is instructions for the agent only.

Does Linkedin access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Linkedin safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Linkedin use?

Linkedin is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Linkedin use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Linkedin?

Skills that share tags, products or a category with Linkedin: Company Research (liangdabiao/exa-research-mcp-skill, 110 stars), Account Research (explorium-ai/gtm-skills, 163 stars), Enrich Contact (explorium-ai/gtm-skills, 163 stars) and Linkedin Outbound Angle (Othmane-Khadri/YALC-the-GTM-operating-system, 317 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Linkedin?

unifapi-agent (a GitHub organization) maintains it in unifapi-agent/agents, which has 587 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on September 5, 2026.

Source: unifapi-agent/agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Linkedin

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

linkedin

Use the unifapi skill for live evidence

Response contract

Core operations

Workflow

Shape notes

Gotchas

Output

Related skills

Files

Compare with similar skills

Similar skills

More from unifapi-agent/agents

Related

Questions about Linkedin

Use the `unifapi` skill for live evidence