CtrlK
BlogDocsLog inGet started
Tessl Logo

2-repro-issue

Reproduce a single LinkedIn-MCP issue locally on the current branch against the real authenticated LinkedIn session at ~/.linkedin-mcp/profile/, using the MCP streamable-http server. Captures the exact failure mode (tool output, error, missing data) and maps it back to the scraper code path. Use when the user says "reproduce

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tightly-sequenced, highly executable repro workflow with strong validation checkpoints and clean handoff artifacts. Its only weakness is conciseness: several inline explanatory asides could be shortened or moved out of the command path without sacrificing actionability.

Suggestions

Trim the inline rationale blocks (e.g. the port-probing and uvx-vs-uv explanations) into a one-line 'why' so the executable commands stay front and center.

Consider moving the long 'notifications/initialized returns a harmless error' aside into a short callout or a troubleshooting reference rather than mid-phase prose.

Consolidate the two short prose paragraphs in Phase 5 (target selection, flaky re-run) into compact bullet lists to match the rest of the phase style.

DimensionReasoningScore

Conciseness

Mostly efficient and free of unrelated concept explanations, but inline rationale (the port-probing justification, the uvx-vs-uv note, the harmless-initialized-error aside) adds prose that could be trimmed without losing the actionable command set.

2 / 3

Actionability

Every phase ships executable bash — real curl initialize/tools/call payloads, a jq one-liner persisting call metadata, and a port-probe loop — copy-paste ready and parameterized for the issue.

3 / 3

Workflow Clarity

A clear 7-phase sequence with explicit validation checkpoints (workspace-clean check, server-bound wait loop, Mcp-Session-Id presence check, server-died detection) and a feedback/recovery path on each failure.

3 / 3

Progressive Disclosure

No external bundle files exist; the skill is self-contained and cleanly sectioned into phases, with handoff artifacts persisted to stable /tmp paths for the sibling /3-verify-pr-fix skill — one-level-deep navigation, no nested references.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and self-bounding — it states concrete actions, realistic user utterances, and an explicit what/when pair while carving out a clear niche and a non-overlap boundary with the sibling fix skill. It is written in the required third-person voice.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Reproduce a single LinkedIn-MCP issue locally', 'Captures the exact failure mode (tool output, error, missing data)', 'maps it back to the scraper code path' — rather than vague language.

3 / 3

Completeness

Explicitly answers both 'what' (reproduce, capture failure mode, map to code path) and 'when' via an explicit 'Use when the user says...' clause with concrete triggers.

3 / 3

Trigger Term Quality

Covers natural phrases a user would actually say — 'reproduce #N', 'investigate #N', 'try #N locally', 'verify the bug in #N' — plus an issue-URL paste trigger.

3 / 3

Distinctiveness Conflict Risk

A distinct niche (LinkedIn-MCP issue repro against a real session over the streamable-http server) with an explicit boundary against /3-verify-pr-fix makes wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
stickerdaniel/linkedin-mcp-server
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.