Skip to main content
Agent skills are instructions written for coding agents rather than for people. Each one covers a single Edges endpoint — its inputs, the URL formats it accepts, what it returns, and the mistakes agents typically make with it — so an agent building against Edges gets it right the first time instead of inferring it from the reference. They live in a public repository, under Apache 2.0.

edgesrun/linkedin-skills

76 skills covering the LinkedIn and Sales Navigator API, plus five guides.

​
Installing

The repository ships as a plugin, so an agent that supports plugins picks up every skill at once rather than needing them pasted in. Clone it, or point your agent’s plugin configuration at the repository — see the README for the exact steps for your tool.
Skills describe how to call Edges. They don’t hold your API key, and they don’t run anything on their own — your agent still authenticates and makes the calls.

​
What’s covered

One skill per action

Extraction, search, messaging, engagement and Sales Navigator — each documented action has a matching skill, linked from its API reference page.

Five cross-cutting guides

Getting started, URL construction, identities, outreach sequencing and error handling — the parts an agent gets wrong across every endpoint.
Every action page in the API Reference carries a link to its skill where one exists. Going the other way, a skill names the action it belongs to, so the two stay in step.
Cookieless by default. The skills assume managed mode, so an agent can extract and search without a LinkedIn account being connected first. Outreach skills still require a connected identity, because the action has to come from a real person.

​
URL construction

The single most common source of failed calls is a malformed LinkedIn URL — Sales Navigator URLs in particular carry query state that has to be preserved exactly. The edges-url-construction skill covers this across every endpoint, and is worth loading even when your agent only uses one action.

edges-url-construction

Which URL each action accepts, and how to build one that works.

SDKs

The official clients, for when you’re writing the integration yourself.

API Reference

Every endpoint, with its limits and credit cost.

Identity Modes

Whether an action needs a connected account.