Kai Stenberg
Community@kaistenberg · Siggerud, Norway
Microsoft MVP M365 Apps & Services | Teams
Agent Skills by Kai Stenberg
Showing 5 vetted skills indexed across 1 GitHub repositories.
kaistenbergbtca-local
Searches locally cloned git repositories to answer questions with cited code examples.
kaistenberg2-repro-issue
Reproduce LinkedIn-MCP GitHub issues locally against a real authenticated LinkedIn session.
kaistenberg1-triage-issues
Ranks open GitHub issues and PRs by severity, mergeability, and contributor history.
kaistenberg3-verify-pr-fix
Verify a candidate PR fixes a reproduced issue by replaying the same MCP tool call and diffing outputs.
kaistenbergtriage-reviews
Fetch, verify, and resolve GitHub PR review comments against actual code.
Frequently Asked Questions About Kai Stenberg
FAQPage SchemaWhat tasks can I perform with kaistenberg's skills?▼
You can triage and rank open issues and PRs in stickerdaniel/linkedin-mcp-server, reproduce a specific issue locally against the real authenticated LinkedIn session, verify whether a candidate PR actually fixes a reproduced issue, and process PR review comments by fixing valid issues 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, validate community pull requests, and resolve review feedback. They assume familiarity with GitHub issue/PR workflows and the repo's scraping rules in CLAUDE.md.
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 against that baseline.
What prerequisites and dependencies do these skills require?▼
A locally cloned stickerdaniel/linkedin-mcp-server repository, 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 for the linked issue.
Do these skills apply fixes automatically during triage?▼
No. The 1-triage-issues skill only outputs a ranked list with rationale, and 2-repro-issue only captures the failure mode without checking out PRs or attempting fixes. Only triage-reviews modifies code, by fixing valid review comments, committing, and pushing.