React Router Bug Fix Workflow
remix-run/react-router
Fixes a React Router bug reported in a GitHub issue end to end: fetching the issue, validating the reproduction, writing a failing test and implementing the fix on a new branch.
Investigates a reported LinkedIn-MCP issue by matching the reporter's tool call to the exact source file and tests, without applying a fix.
$ npx skills add stickerdaniel/linkedin-mcp-server --skill 2-repro-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install stickerdaniel/linkedin-mcp-server 2-repro-issue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/stickerdaniel/linkedin-mcp-server.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/2-repro-issue .claude/skills/2-repro-issue && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "2-repro-issue" agent skill from https://github.com/stickerdaniel/linkedin-mcp-server/tree/main/.agents/skills/2-repro-issue into .claude/skills/2-repro-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "2-repro-issue", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/stickerdaniel/linkedin-mcp-server/tree/main/.agents/skills/2-repro-issueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add stickerdaniel/linkedin-mcp-server --skill 2-repro-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install stickerdaniel/linkedin-mcp-server 2-repro-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stickerdaniel/linkedin-mcp-server.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/2-repro-issue .agents/skills/2-repro-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "2-repro-issue" agent skill from https://github.com/stickerdaniel/linkedin-mcp-server/tree/main/.agents/skills/2-repro-issue into .agents/skills/2-repro-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "2-repro-issue", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add stickerdaniel/linkedin-mcp-server --skill 2-repro-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install stickerdaniel/linkedin-mcp-server 2-repro-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stickerdaniel/linkedin-mcp-server.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/2-repro-issue .cursor/skills/2-repro-issue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "2-repro-issue" agent skill from https://github.com/stickerdaniel/linkedin-mcp-server/tree/main/.agents/skills/2-repro-issue into .cursor/skills/2-repro-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "2-repro-issue", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/stickerdaniel/linkedin-mcp-server.git --path .agents/skills/2-repro-issue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add stickerdaniel/linkedin-mcp-server --skill 2-repro-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install stickerdaniel/linkedin-mcp-server 2-repro-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stickerdaniel/linkedin-mcp-server.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/2-repro-issue .gemini/skills/2-repro-issue && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "2-repro-issue" agent skill from https://github.com/stickerdaniel/linkedin-mcp-server/tree/main/.agents/skills/2-repro-issue into .gemini/skills/2-repro-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "2-repro-issue", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install stickerdaniel/linkedin-mcp-server 2-repro-issueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add stickerdaniel/linkedin-mcp-server --skill 2-repro-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/stickerdaniel/linkedin-mcp-server.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/2-repro-issue .github/skills/2-repro-issue && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "2-repro-issue" agent skill from https://github.com/stickerdaniel/linkedin-mcp-server/tree/main/.agents/skills/2-repro-issue into .github/skills/2-repro-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "2-repro-issue", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add stickerdaniel/linkedin-mcp-server --skill 2-repro-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install stickerdaniel/linkedin-mcp-server 2-repro-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stickerdaniel/linkedin-mcp-server.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/2-repro-issue .opencode/skills/2-repro-issue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "2-repro-issue" agent skill from https://github.com/stickerdaniel/linkedin-mcp-server/tree/main/.agents/skills/2-repro-issue into .opencode/skills/2-repro-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "2-repro-issue", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
2-repro-issueInvestigates a reported LinkedIn-MCP issue by matching the reporter's tool call to the exact source file and tests, without applying a fix.
This skill is scoped to investigation only - reproducing and evaluating a reported bug, not fixing it, since a separate skill handles verifying a fix. Given an issue number or URL, it pulls the GitHub thread and extracts the tool called, its arguments, the observed result, the runtime, the LinkedIn variant, and any related issues, keeping observations, source findings, hypotheses and work not yet done clearly separate.
It maps the reported tool to code through a fixed chain: the MCP entrypoint for that surface, a generated ownership table that points to the real implementation file rather than treating a shared extractor file as authoritative, the section definitions file, and the matching owner-level test file. Every finding gets labeled as supported by reporter evidence, confirmed in source, needing more evidence, or not supported by the evidence supplied.
It treats a successful call from the maintainer's own account as no refutation of a failure on the reporter's account, and explicitly withholds authorization for any reporter command with real side effects - sending a message, a connection request, a forced login, or a repeated call - even when the issue grants publishing permission generally.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit b71682f. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gituvcurlghjqFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, uv, curl and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
LinkedIn MCP Issue Investigator loads about 2k tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 542 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from stickerdaniel/linkedin-mcp-server at commit b71682f, republished under its Apache-2.0 licence (© stickerdaniel). 542 words, ~1,961 tokens.
.claude/skills/2-repro-issue/SKILL.md (or your agent's skills folder).Evaluate the reporter packet and the matching source. A live LinkedIn call is optional. Do not check out a PR or attempt a fix. That is /3-verify-pr-fix.
NUM=$(echo "$ARGUMENTS" | sed -E 's|.*/||; s|#||g' | grep -oE '^[0-9]+' | head -1)
[ -z "$NUM" ] && { echo "Invalid input: '$ARGUMENTS'. Pass an issue number or URL." >&2; exit 1; }
REPO=stickerdaniel/linkedin-mcp-server
gh issue view $NUM --repo $REPO --commentsFrom the thread extract the tool, arguments, observed result, runtime, LinkedIn variant, and related issues. Distinguish observations, source findings, hypotheses, and work not run.
Map the tool to code:
linkedin_mcp_server/tools/<surface>.py. MCP entrypoint and arg validationdocs/linkedin-architecture.md. Generated ownership table; follow it to linkedin_mcp_server/linkedin/<owner>.py rather than treating linkedin/extractor.py as the implementationlinkedin_mcp_server/linkedin/fields.py. PERSON_SECTIONS / COMPANY_SECTIONS (each entry = one navigation)tests/linkedin/test_<owner>.py; use tests/test_fields.py, tests/test_identifiers.py, and tests/test_link_metadata.py for those owners, and tests/linkedin/test_facade_*.py only for facade contractsInspect the relevant source at the current SHA. Do not invent a LinkedIn result or an unimplemented tool call.
This step is complete when the report names the issue, the code SHA, the inspected evidence, the facts established, the unverified runtime claims, and the next decision.
Use one of:
A successful call on the maintainer's different account never refutes a failure on the reporter's account. Target content language is not the authenticated account's UI language. Captures and URL or attribute evidence may establish the needed variation without another live call.
Review reporter commands before execution. Publishing permission does not authorize send_message, a connection request, a forced login, or repeated calls with account side effects. Record sent, recipient_selected, and retry_safe as observed fields, not as replay authorization.
If the next decision needs a live observation, name the exact unresolved question and ask before login, session changes, or LinkedIn writes. If the human declines, keep the packet-and-source verdict.
Only after an explicit yes for this run. Use uv run, never uvx, so the server reflects the workspace. Record the actual tool, arguments, runtime, account variant, code SHA, and timestamp before the call. Keep the reporter's installed-launcher context distinct from a workspace check.
git status --porcelain | head -5
git log -1 --onelineIf the workspace is dirty, ask before continuing. If a login is required, ask; do not run --login as a default.
PORT=8765
while lsof -nP -iTCP:$PORT -sTCP:LISTEN >/dev/null 2>&1; do PORT=$((PORT+1)); done
echo $PORT > /tmp/repro-$NUM.port
uv run -m linkedin_mcp_server --transport streamable-http --port $PORT --log-level INFO > /tmp/repro-$NUM.log 2>&1 &
SERVER_PID=$!
echo $SERVER_PID > /tmp/repro-$NUM.pid
for i in $(seq 1 30); do
lsof -nP -iTCP:$PORT -sTCP:LISTEN >/dev/null 2>&1 && break
kill -0 $SERVER_PID 2>/dev/null || { echo "Server died during startup. Tail of /tmp/repro-$NUM.log:" >&2; tail -20 /tmp/repro-$NUM.log >&2; exit 1; }
sleep 1
done
lsof -nP -iTCP:$PORT -sTCP:LISTEN >/dev/null 2>&1 || { echo "Server never bound port $PORT after 30s" >&2; tail -20 /tmp/repro-$NUM.log >&2; exit 1; }PORT=$(cat /tmp/repro-$NUM.port)
curl -s -D /tmp/repro-$NUM-headers -X POST http://127.0.0.1:$PORT/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"repro-issue","version":"1.0"}}}' \
> /tmp/repro-$NUM-init.json
SESSION_ID=$(grep -i 'Mcp-Session-Id' /tmp/repro-$NUM-headers | awk '{print $2}' | tr -d '\r')
[ -z "$SESSION_ID" ] && { echo "MCP initialize returned no Mcp-Session-Id. Tail of /tmp/repro-$NUM.log:" >&2; tail -20 /tmp/repro-$NUM.log >&2; kill $SERVER_PID 2>/dev/null; exit 1; }
grep -q '"error"' /tmp/repro-$NUM-init.json && { echo "Initialize returned a protocol error. Execution limit." >&2; cat /tmp/repro-$NUM-init.json >&2; kill $SERVER_PID 2>/dev/null; exit 1; }
curl -s -X POST http://127.0.0.1:$PORT/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "Mcp-Session-Id: $SESSION_ID" \
-d '{"jsonrpc":"2.0","id":2,"method":"notifications/initialized","params":{}}' \
> /tmp/repro-$NUM-initialized.json
grep -q '"error"' /tmp/repro-$NUM-initialized.json && { echo "notifications/initialized returned a protocol error. Execution limit." >&2; cat /tmp/repro-$NUM-initialized.json >&2; kill $SERVER_PID 2>/dev/null; exit 1; }Capture and inspect both response bodies before tools/call. A protocol or validation error is an execution limit. Do not retry around it.
SHA=$(git rev-parse HEAD)
TOOL="<TOOL>"
ARGS_JSON='{<ARGS>}'
jq -n --arg t "$TOOL" --argjson a "$ARGS_JSON" --arg sha "$SHA" \
'{tool: $t, arguments: $a, sha: $sha}' \
> /tmp/repro-issue-$NUM-meta.json
curl -s -X POST http://127.0.0.1:$PORT/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "Mcp-Session-Id: $SESSION_ID" \
-d "{\"jsonrpc\":\"2.0\",\"id\":3,\"method\":\"tools/call\",\"params\":{\"name\":\"$TOOL\",\"arguments\":$ARGS_JSON}}" \
| tee /tmp/repro-issue-$NUM-main.json | head -200If the issue does not pin a concrete target, do not invent one to complete the live check. Ask, or stop with the packet-and-source verdict.
Preserve /tmp/repro-issue-$NUM-main.json and /tmp/repro-issue-$NUM-meta.json only for a genuine captured run. A run from a non-main commit must identify that SHA in the meta file. Do not claim an on-main baseline because of the filename.
kill $SERVER_PID 2>/dev/null
wait $SERVER_PID 2>/dev/null
rm -f /tmp/repro-$NUM-headers /tmp/repro-$NUM.log /tmp/repro-$NUM.port /tmp/repro-$NUM.pid /tmp/repro-$NUM-init.json /tmp/repro-$NUM-initialized.jsonLive verdicts, when a run happened:
**#<N>**. <one-line issue summary>
**SHA:** <short-sha>
**Inspected:** <packet fields and source files>
**Facts established:** <list>
**Unverified:** <runtime claims not checked>
**Verdict:** <supported by reporter evidence | confirmed in source | reproduced in the stated environment | needs more evidence | not supported by the supplied evidence>
**Evidence:** <2 to 4 lines>
**Likely code path:** <file:line>. <one-line why>
**Baseline:** <path and SHA, or none>
**Next:** <missing fields | /3-verify-pr-fix N | fix sketch | no live check needed>uv run, not uvx, for a workspace live check. Use the reporter's launcher only to test that installation./3-verify-pr-fix.© stickerdaniel, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/2-repro-issue of stickerdaniel/linkedin-mcp-server.
Open the folder on GitHubat commit b71682f
LinkedIn MCP Issue Investigator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| LinkedIn MCP Issue Investigator this skillstickerdaniel/linkedin-mcp-server | 3.8k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| React Router Bug Fix Workflowremix-run/react-router | 57k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Extension Puppeteer Debuggingmengxi-ream/read-frog | 10k | — | ~2k | Automated safety check: Notes | GPL-3.0 | |
| Triagebot Action Bug Triagewithastro/astro | 63k | — | ~639 | Automated safety check: Pass | Custom licence | |
| OpenROAD Issue TriageThe-OpenROAD-Project/OpenROAD | 3.2k | — | ~842 | Automated safety check: Pass | BSD-3-Clause | |
| Playground Website DebuggingWordPress/wordpress-playground | 2k | — | ~1.9k | Automated safety check: Pass | GPL-2.0 |
remix-run/react-router
Fixes a React Router bug reported in a GitHub issue end to end: fetching the issue, validating the reproduction, writing a failing test and implementing the fix on a new branch.
mengxi-ream/read-frog
Debug the built Read Frog extension in real Chrome. An agent skill from mengxi-ream/read-frog.
withastro/astro
Takes a bug report for the triagebot-action GitHub Action through reproduction, root-cause diagnosis, an intended-behavior check and a fix attempt.
The-OpenROAD-Project/OpenROAD
Reproduces an OpenROAD GitHub bug from an attached tarball and shrinks the failing design with whittle.py so maintainers get a minimal test case.
WordPress/wordpress-playground
Debug the WordPress Playground website by running the dev server from source and interacting with it via Playwright MCP.
ZaxbyHub/opencode-swarm
Drives a bug report from validation and root-cause tracing through a critic-reviewed plan, an approved minimal fix and a PR-ready closure, never merging without recorded human approval.
stickerdaniel/linkedin-mcp-server
Turns the open issues and pull requests of the linkedin-mcp-server repository into a read-only priority list for maintainers.
stickerdaniel/linkedin-mcp-server
Reviews a candidate pull request's diff and tests against its linked issue, with an optional live comparison against a previously captured baseline, without editing, merging or pushing.
stickerdaniel/linkedin-mcp-server
Searches git repositories cloned locally under a sandbox folder to answer questions with cited links and complete code snippets.
stickerdaniel/linkedin-mcp-server
Collects every review comment on a pull request, checks each against the real code, fixes the valid ones, pushes, and replies on and resolves each thread.
stickerdaniel/linkedin-mcp-server
Turns a bug report or feature idea into a properly sourced GitHub issue or comment, only after searching for a matching issue first.
stickerdaniel/linkedin-mcp-server
Rules for using the bundled LinkedIn MCP server for profile, company, job, post, feed and inbox work, with explicit authorization required for messages and connection requests.
Works with
Categories
Investigates a reported LinkedIn-MCP issue by matching the reporter's tool call to the exact source file and tests, without applying a fix. This skill is scoped to investigation only - reproducing and evaluating a reported bug, not fixing it, since a separate skill handles verifying a fix. Given an issue number or URL, it pulls the GitHub thread and extracts the tool called, its arguments, the observed result, the runtime, the LinkedIn variant, and any related issues, keeping observations, source findings, hypotheses and work not yet done clearly separate.
LinkedIn MCP Issue Investigator fits situations like: investigating a reported bug in the LinkedIn MCP server; checking whether a GitHub issue's claim holds up against the source; mapping a reported tool failure to the exact implementation file.
Run `npx skills add stickerdaniel/linkedin-mcp-server --skill 2-repro-issue -a claude-code`. Or copy the skill folder (.agents/skills/2-repro-issue in stickerdaniel/linkedin-mcp-server) into .claude/skills/2-repro-issue in your project. Claude Code loads it when a task matches its description.
Run `npx skills add stickerdaniel/linkedin-mcp-server --skill 2-repro-issue -a codex`. Or copy the skill folder (.agents/skills/2-repro-issue in stickerdaniel/linkedin-mcp-server) into .agents/skills/2-repro-issue in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add stickerdaniel/linkedin-mcp-server --skill 2-repro-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/2-repro-issue, .gemini/skills/2-repro-issue, .github/skills/2-repro-issue and .opencode/skills/2-repro-issue in your project.
Going by SKILL.md and its folder, LinkedIn MCP Issue Investigator needs the command-line tools its instructions call (git, uv, curl, gh and jq). Our summary lists: gh CLI access to the repository's issues.
SKILL.md contains no URLs. Its commands use git, uv, curl and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
LinkedIn MCP Issue Investigator is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with LinkedIn MCP Issue Investigator: React Router Bug Fix Workflow (remix-run/react-router, 57k stars), Extension Puppeteer Debugging (mengxi-ream/read-frog, 10k stars), Triagebot Action Bug Triage (withastro/astro, 63k stars) and OpenROAD Issue Triage (The-OpenROAD-Project/OpenROAD, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
stickerdaniel (a GitHub user) maintains it in stickerdaniel/linkedin-mcp-server, which has 3,782 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.
Source: stickerdaniel/linkedin-mcp-server on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.