skills.rest
stickerdaniel
stickerdanielCOMMUNITY
Explore all skills by this author →
GitHub

2-repro-issue

Reproduce LinkedIn-MCP issues locally using the authenticated session.

3.1k|528|Updated Apr 13, 2025
Search Tags:#debugging#reproduce#reproducibility#issue-tracking#local-server#linkedin-mcp
One-click install
npx skills add https://github.com/stickerdaniel/linkedin-mcp-server --skill 2-repro-issue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 2-repro-issue
Source: https://github.com/stickerdaniel/linkedin-mcp-server/tree/main/.agents/skills/2-repro-issue
Command: npx skills add https://github.com/stickerdaniel/linkedin-mcp-server --skill 2-repro-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproduce a LinkedIn-MCP issue locally on the current branch by using the authenticated LinkedIn session to verify the bug on the current branch.

Core Features & Use Cases

  • Reproduce a specific issue by executing the exact failing tool against the live LinkedIn surface via the local MCP server.
  • Capture tool outputs, error messages, and state to map to the relevant scraper and tool code paths.
  • Validate environment readiness (workspace cleanliness, valid profile) and output structured evidence for /3-verify-pr-fix workflows.

Quick Start

Reproduce the specified issue locally on the current branch using the authenticated profile at ~/.linkedin-mcp/profile/.

Frequently Asked Questions about 2-repro-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reproduce a LinkedIn-MCP issue locally against a live authenticated session?▼

Reproducing a LinkedIn-MCP issue locally requires executing the exact failing tool against the live LinkedIn surface via the local MCP server. It uses the authenticated profile at ~/.linkedin-mcp/profile/ to verify the bug on the current branch.

What do I need to run a local LinkedIn-MCP reproduction workflow?▼

Running a local LinkedIn-MCP reproduction requires a clean workspace, an authenticated profile at ~/.linkedin-mcp/profile/, and the ability to execute uv run with a temporary port allocation to test the failing tool.

Can I capture stdout and error messages when reproducing LinkedIn-MCP bugs?▼

Yes, the reproduction workflow captures tool outputs, error messages, and state to map to the relevant scraper and tool code paths. This structured evidence is saved under /tmp for later analysis.

How does reproducing an issue locally help verify a bug on the current branch?▼

Reproducing an issue locally verifies the bug on the current branch by executing the exact failing tool against the live LinkedIn surface via the local MCP server. It validates environment readiness and outputs structured evidence for subsequent verification workflows.

Why does my LinkedIn-MCP issue reproduction require a clean workspace?▼

A clean workspace is required to validate environment readiness and ensure the reproduction targets a single issue accurately. It prevents local state conflicts when running the failing tool via uv run with a temporary port allocation.

Related Skills

Explore More Software Engineering Skills→
BasedHardwareBasedHardware
13.1k

local-dev

Launch a Python backend and macOS app in local development environments.

Official
Intermediate
hackethacket
38

deep-reading-analyst

Apply 10+ thinking frameworks to analyze articles and extract insights.

Community
Advanced
tr4m0ryptr4m0ryp

2-repro-issue

Reproduce LinkedIn-MCP issues locally against an authenticated session.

Community
Advanced
cy-walicy-wali

debug

Guide structured debugging sessions to reproduce, isolate, diagnose, and fix bugs.

Community
Intermediate