skills.rest
tr4m0ryp
tr4m0rypCOMMUNITY
Explore all skills by this author →
𝕏@tr4m0rypGitHub

2-repro-issue

Reproduce LinkedIn-MCP issues locally against an authenticated session.

Updated Jul 10, 2026
Search Tags:#tool development#bug tracking#local testing#linkedin-mcp#issue reproduction
One-click install
npx skills add https://github.com/tr4m0ryp/linkedin-mcp-server --skill 2-repro-issue-tr4m0ryp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 2-repro-issue
Source: https://github.com/tr4m0ryp/linkedin-mcp-server/tree/main/.agents/skills/2-repro-issue
Command: npx skills add https://github.com/tr4m0ryp/linkedin-mcp-server --skill 2-repro-issue-tr4m0ryp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows you to locally reproduce LinkedIn-MCP issues, ensuring the exact failure mode is captured for further analysis.

Core Features & Use Cases

  • Issue Reproduction: Reproduce a LinkedIn-MCP issue locally against your authenticated session.
  • Local Branch Testing: Test against the current branch to verify the bug without PR or fix checks.
  • Data Capture: Capture the exact output, errors, and missing data from the failing tool to pinpoint the issue's source.

Quick Start

Use the 2-repro-issue skill with an issue number, e.g., '2-repro-issue 442'.

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?▼

To reproduce a LinkedIn-MCP issue locally, you run the skill with a specific issue number. It executes tool calls against your authenticated session to capture the exact failure mode and map errors to code paths.

What do I need to reproduce LinkedIn-MCP tool errors on my machine?▼

Reproducing LinkedIn-MCP tool errors requires access to the LinkedIn-MCP toolset and a local development environment. You must also have an authenticated LinkedIn session to run the failing tool calls and capture accurate outputs.

Can I test a LinkedIn-MCP bug fix locally without opening a pull request?▼

Yes, you can test a LinkedIn-MCP bug fix locally against your current branch. The skill verifies the issue without requiring PR or fix checks, directly capturing missing data and errors from the tool.

Why does my LinkedIn-MCP tool call fail on an authenticated session?▼

A LinkedIn-MCP tool call may fail due to code path errors or missing data. Running the reproduction skill captures the exact output and errors from the failing tool, pinpointing the issue's source for further analysis.

How do I capture tool outputs and map them to LinkedIn-MCP code paths?▼

You capture tool outputs and map them to LinkedIn-MCP code paths by executing the reproduction skill. It runs the failing tool calls on a real authenticated session and records the exact errors for source analysis.

What is local branch testing for LinkedIn-MCP issue reproduction?▼

Local branch testing for LinkedIn-MCP issue reproduction is the process of running failing tool calls against your current local development branch. It captures exact errors and outputs to verify the bug without enforcing fix checks.

Related Skills

Explore More Software Engineering Skills→
tr4m0ryptr4m0ryp

3-verify-pr-fix

Compare tool call outputs before and after a pull request fix.

Community
Advanced
AgentSystemLabsAgentSystemLabs
121

fix-pr-tests

Diagnoses GitHub CI test failures and applies minimal fixes to resolve them.

Official
Advanced
arthrodarthrod

dogfood

Explore web applications and generate bug reports with screenshots and videos.

Community
Advanced
zli5460zli5460
2

native-mcp

Connect Hermes Agent to external MCP servers via stdio or HTTP, registering discovered tools automatically.

Community
Intermediate