About this skill

Problem

LinkedIn data requests often sit between web pages, endpoints, and parameters: a user may want companies, people, jobs, or posts, but a direct API call still requires the right object, route, filters, pagination depth, and response shape. This skill turns natural-language business goals into KeyAPI REST workflows, grounding endpoint selection in the current docs.keyapi.ai contracts before running search, detail, ranking, comparison, or report tasks.

How It Works

It first infers goal, entity, scope, metric, pagination, and output format, then maps the request to a LinkedIn scenario such as profile due diligence, company discovery, hiring intelligence, or job analysis. Key steps include:
- checking local KEYAPI_TOKEN authentication before live execution;
- resolving the current method, /v1/... path, parameters, enums, pagination, and response envelope from docs;
- preferring scripts/keyapi-api.mjs for REST calls and falling back to the host HTTP client when needed;
- separating observed API facts from inference in the final answer.

Boundaries

It is best for structured LinkedIn analysis that needs auditable endpoints and stable response handling. It does not replace platform browsing, and it should not guess routes from memory; when official docs differ from skill rules, the official docs win.

Screenshots

Use Cases

Validate target accounts, key people, company size, and hiring status before B2B outreach.
Aggregate job counts, job details, and posting companies around a keyword or role for market review.
Analyze company post engagement and hiring signals into a checked LinkedIn intelligence brief.
Separate people, companies, jobs, and posts into due-diligence or competitor comparison notes.

Best For

B2B researchers who must validate target accounts, roles, and key people before outreach.
Sales ops analysts who need job counts, company distribution, and hiring signals for reports.
Due-diligence analysts who split LinkedIn people, companies, and post signals into findings.
Engineers integrating KeyAPI LinkedIn endpoints and checking parameters and response shapes.