What problem does it solve? Confirming whether a reported bug in the linkedin-mcp-server project actually exists requires manually setting up the server, authenticating, and replaying the failing tool call. This Skill automates that investigation, producing concrete evidence that confirms or refutes an issue on the current branch. ## Core Features & Use Cases - Issue Parsing and Code Mapping: Reads a GitHub issue via gh, extracts the affected MCP tool, exact arguments, and expected behavior, then maps them to the relevant scraper code path. - Live MCP Server Reproduction: Starts the streamable-http MCP server from the current workspace with uv run, initializes an MCP session over curl, and replays the exact failing tool call against the real LinkedIn profile at ~/.linkedin-mcp/profile/. - Verdict and Baseline Capture: Classifies the result as Reproduced, Reproduced different mode, Not reproduced, or Inconclusive, and saves the response plus request metadata to /tmp for the follow-up /3-verify-pr-fix workflow. - Use Case: A maintainer sees issue #442 claiming get_person_profile returns empty sections. Run this Skill with the issue number to replay the call against real LinkedIn and get a verdict with evidence and the likely code path. ## Quick Start Ask the assistant to reproduce issue 442 from stickerdaniel/linkedin-mcp-server locally and report whether the bug is confirmed on the current branch.