skills.rest
larscolombia avatar

larscolombia

Community

@larscolombia

0Followers
|
3Public Repos
|
5Published Skills

Maintainer-focused skills for triaging, reproducing, and verifying issues and PRs in the stickerdaniel/linkedin-mcp-server repository.

🐙 GitHub ↗
Skills Distribution
DomainDeveloper To...Issue & PR Triage (30%)Bug Reproduction &.. (30%)PR Verification & .. (25%)MCP Server Operati.. (15%)

Agent Skills by larscolombia

Showing 5 vetted skills indexed across 1 GitHub repositories.

larscolombialarscolombia

btca-local

Searches locally cloned git repositories to answer questions with cited code examples.

Community
Basic
larscolombialarscolombia

2-repro-issue

Reproduce LinkedIn MCP server issues locally against a real authenticated session.

Community
Advanced
larscolombialarscolombia

1-triage-issues

Ranks open GitHub issues and PRs by severity, mergeability, and contributor history.

Community
Advanced
larscolombialarscolombia

3-verify-pr-fix

Verifies whether a candidate GitHub PR fixes a reproduced issue by replaying the same MCP tool call and diffing outputs.

Community
Advanced
larscolombialarscolombia

triage-reviews

Fetch GitHub PR review comments, verify findings against code, fix valid issues, and resolve threads.

Community
Advanced

Frequently Asked Questions About larscolombia

FAQPage Schema
What tasks can I perform with larscolombia's skills?▼

You can triage and rank open issues and PRs, reproduce a specific issue locally against the real authenticated LinkedIn session, verify whether a candidate PR actually fixes a reproduced issue by diffing outputs, and process PR review comments by verifying each against real code, fixing valid ones, and pushing commits.

Who are these skills designed for?▼

They target core maintainers and contributors of the stickerdaniel/linkedin-mcp-server repository who need to prioritize backlogs, investigate reported bugs, validate incoming pull requests, and resolve reviewer feedback against the actual codebase.

How does the issue reproduction and PR verification flow work?▼

First run 2-repro-issue with an issue number or URL to capture the failure baseline at /tmp/repro-issue-<linked>-main.json. Then run 3-verify-pr-fix with a PR number: it checks out the branch, restarts the MCP server, re-runs the same tool call, and diffs outputs while auditing locale-independence and DOM-stability.

What prerequisites and dependencies are required?▼

You need a local clone of stickerdaniel/linkedin-mcp-server, an authenticated LinkedIn session stored at ~/.linkedin-mcp/profile/, and the MCP streamable-http server runnable locally. PR verification additionally requires that 2-repro-issue has already captured the on-main baseline output.

Do these skills modify code or only analyze it?▼

Mostly analysis: triage outputs ranked lists, and reproduction captures failure modes without attempting fixes. The exception is triage-reviews, which verifies each PR review comment against real code and docs, fixes valid issues, then commits and pushes the changes.