# 2 Repro Issue

Reproduce #N, investigate #N, try #N locally, or verify the bug in #N.

- Repository: https://github.com/stickerdaniel/linkedin-mcp-server (4081 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add stickerdaniel/linkedin-mcp-server --skill 2-repro-issue -g -a claude-code -y`
Codex: `npx skills add stickerdaniel/linkedin-mcp-server --skill 2-repro-issue -g -a codex -y`
Cursor: `npx skills add stickerdaniel/linkedin-mcp-server --skill 2-repro-issue -g -a cursor -y`
Gemini CLI: `npx skills add stickerdaniel/linkedin-mcp-server --skill 2-repro-issue -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add stickerdaniel/linkedin-mcp-server`

## Description

Reproduce #N, investigate #N, try #N locally, or verify the bug in #N.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Investigate a LinkedIn-MCP issue

Evaluate the reporter packet and the matching source. A live LinkedIn call is optional. Do not check out a PR or attempt a fix. That is `/3-verify-pr-fix`.

## 1. Read the issue

```bash
NUM=$(echo "$ARGUMENTS" | sed -E 's|.*/||; s|#||g' | grep -oE '^[0-9]+' | head -1)
[ -z "$NUM" ] && { echo "Invalid input: '$ARGUMENTS'. Pass an issue number or URL." >&2; exit 1; }
REPO=stickerdaniel/linkedin-mcp-server

gh issue view $NUM --repo $REPO --comments
```

From the thread extract the tool, arguments, observed result, runtime, LinkedIn variant, and related issues. Distinguish observations, source findings, hypotheses, and work not run.

Map the tool to code:

1. `linkedin_mcp_server/tools/<surface>.py`. MCP entrypoint and arg validation
2. `docs/linkedin-architecture.md`. Generated ownership table; follow it to `linkedin_mcp_server/linkedin/<owner>.py` rather than treating `linkedin/extractor.py` as the implementation
3. `linkedin_mcp_server/linkedin/fields.py`. `PERSON_SECTIONS` / `COMPANY_SECTIONS` (each entry = one navigation)
4. The owner-local test, usually `tests/linkedin/test_<owner>.py`; use `tests/test_fields.py`, `tests/test_identifiers.py`, and `tests/test_link_metadata.py` for those owners, and `tests/linkedin/test_facade_*.py` only for facade contracts

## 2. Packet and source

Inspect the relevant source at the current SHA. Do not invent a LinkedIn result or an unimplemented tool call.

This step is complete when the report names the issue, the code SHA, the inspected evidence, the facts established, the unverified runtime claims, and the next decision.

Use one of:

- supported by reporter evidence
- confirmed in source
- needs more evidence (list the specific missing fields)
- not supported by the supplied evidence

The rest: https://github.com/stickerdaniel/linkedin-mcp-server/blob/HEAD/.agents/skills/2-repro-issue/SKILL.md