What problem does it solve? Confirming whether a reported GitHub issue for the linkedin-mcp-server is a real bug requires manually running the failing MCP tool against live LinkedIn, which is slow and error-prone. This Skill automates that reproduction workflow and produces concrete evidence tied to the exact code path. ## Core Features & Use Cases - Issue-to-Tool Mapping: Parses a GitHub issue (number or URL) to identify the affected MCP tool, triggering arguments, and expected versus actual behavior. - Live Reproduction: Starts the local MCP streamable-http server with uv run against the real authenticated profile at ~/.linkedin-mcp/profile/ and calls the failing tool via JSON-RPC. - Verdict and Baseline Capture: Classifies the result as Reproduced, Reproduced different mode, Not reproduced, or Inconclusive, and saves the response plus request metadata for the follow-up /3-verify-pr-fix skill. - Use Case: A maintainer sees issue #442 claiming get_person_profile returns empty sections. They invoke this Skill with "442" and receive a verdict with the exact tool output, the failing scraper file, and a saved baseline for verifying a fix later. ## Quick Start Ask the AI to reproduce issue 442 from stickerdaniel/linkedin-mcp-server locally and report whether the bug is confirmed on the current branch.