Skip to content
Back to skills

Linkedin Research

ASecurity

Research companies, professionals, job markets, and industry content on LinkedIn through SandBase. Use when asked for LinkedIn research, company analysis, professional profiling, job market research, or B2B competitive intelligence.

  • 200 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 5, 2026
ai-agentsreactapi

Works with

  • api
  • mcp

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 26, 2026

npx -y skills add sandbaseai/sandbase-skills --skill linkedin-research --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Linkedin Research?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Linkedin Research
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sandbaseai-linkedin-research/badge)](https://www.skillsdirectory.com/skills/sandbaseai-linkedin-research)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: linkedin-research
description: Research companies, professionals, job markets, and industry content on LinkedIn through SandBase. Use when asked for LinkedIn research, company analysis, professional profiling, job market research, or B2B competitive intelligence.
---

# LinkedIn Research

LinkedIn professional intelligence through SandBase. Research companies, analyze professional profiles, track industry content, and monitor job markets. Read [the API map](references/sandbase-api-map.md) before selecting a capability.

## Call SandBase capabilities

Use the capability identifiers below as discovery hints, not MCP tool names. Find the matching endpoint with `sandbase_discover(q: "<provider and capability>")`; use its returned `name` in `sandbase_inspect(name: "<returned name>")`. Read `inputSchema`, pricing, and `execute_as`, then call `sandbase_run` using `execute_as.arguments.name` and schema-defined `arguments`. If a `run_id` is returned, poll `sandbase_run_get(run_id: "<returned run_id>")` within the task budget until `completed` or `failed`; report pending or failed runs without resubmitting them automatically.

## Operating principles

- Use LinkedIn data for professional research and B2B intelligence only.
- Respect professional privacy — report on public information only.
- Preserve context: include company names, titles, dates, and engagement.
- Never attempt to connect, message, or apply on behalf of the user.

## Workflow

### 1. Company research

Use `linkedin_web_v2_company_profile` for company details (size, industry, description, specialties).
Use `linkedin_web_v2_company_posts` for company content strategy and engagement.

### 2. Professional research

Use `linkedin_web_v2_user_profile` for professional background and current role.
Use `linkedin_web_v2_user_posts` for thought leadership and content activity.

### 3. Job market research

Use `linkedin_web_v2_search_jobs` to find open positions by keyword, location, or company.
Use `linkedin_web_v2_job_detail` for detailed job requirements and qualifications.

### 4. Content analysis

Use `linkedin_web_v2_post_detail` for specific post metrics.
Use `linkedin_web_v2_post_comments` for professional discourse and reactions.

## Output

Return: company overview, team structure insights, content strategy analysis, job market signals, and competitive positioning.

## Example tasks

- "Research [company] on LinkedIn — size, industry positioning, recent posts."
- "What is [person]'s professional background and current role?"
- "Find open [role] positions at companies in [industry] in [location]."
- "What content is [company] posting on LinkedIn? Analyze their strategy."
- "Compare hiring patterns between [company A] and [company B]."

Files in this skill

  • SKILL.md2.3 KB
  • references/sandbase-api-map.md964 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…