What problem does it solve? Confirming whether a reported bug in the LinkedIn MCP server actually exists requires manually starting the server, authenticating, and replaying the failing tool call. This Skill automates that reproduction workflow and produces concrete evidence tied to the exact code path. ## Core Features & Use Cases - Issue Parsing and Mapping: Extracts the affected MCP tool, arguments, and expected behavior from a GitHub issue, then maps them to the scraper code path in linkedin_mcp_server. - Live Reproduction: Starts the MCP streamable-http server from the current workspace with uv run, initializes an MCP session, and calls the failing tool against the real authenticated LinkedIn profile. - Verdict and Baseline: Classifies the result as reproduced, different mode, not reproduced, or inconclusive, and saves the response baseline for later PR-fix verification. - Use Case: A maintainer sees issue #442 claiming get_person_profile returns empty sections. They run this Skill with the issue number and receive a verdict with evidence JSON and the likely failing file. ## Quick Start Ask the assistant to reproduce issue 442 from the linkedin-mcp-server repository locally using this Skill.