CtrlK
BlogDocsLog inGet started
Tessl Logo

1-triage-issues

Scan all open issues and PRs in stickerdaniel/linkedin-mcp-server and rank them by urgency (severity, user impact, age, references), implementation quality (for PRs — mergeability, CI, diff scope, locale-independence, test coverage), and contributor track record (prior merged PRs, review quality, response cadence). Use when the user asks "what should I tackle first as core maintainer", "which PRs are production-ready", "triage backlog", "scan open issues", or any maintainer-prioritisation question about this repo. Outputs a ranked list with rationale per item, not a fix.

78

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A tight, actionable maintainer-triage playbook: executable gh commands, explicit scoring scales, locale/test/scope validation gates, and a copy-paste report template. It stays read-only and cites evidence inline as its non-negotiables demand.

DimensionReasoningScore

Conciseness

No filler or concept explanations Claude already knows; every token is task-specific — exact gh commands, the locale grep pattern, and defined 1–5 scoring scales — matching 'Imperative, no fluff.'

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands (gh issue/pr list with --json fields, gh pr diff --name-only, gh search prs --state merged) plus concrete scoring rubrics and a filled-in report template.

3 / 3

Workflow Clarity

A clear four-phase sequence (Gather → Score issues → Score PRs → Rank) with explicit audit checkpoints and a hard gate: 'Never recommend merge as-is for a PR that hasn't passed the locale/test/scope checks.'

3 / 3

Progressive Disclosure

Self-contained single file with no bundle references and no nested lookups; content is cleanly split into Inputs, Phases 1–4, and Non-negotiables, so navigation is trivial.

3 / 3

Total

12

/

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.

A precise, third-person description that names concrete capabilities, supplies natural trigger phrases, and explicitly separates 'what' from 'when'. It is well-tailored to a single repo and unlikely to fire for the wrong skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and sub-signals — 'rank them by urgency (severity, user impact, age, references), implementation quality… contributor track record (prior merged PRs, review quality, response cadence)' — rather than vague language.

3 / 3

Completeness

Clearly answers both what ('Scan all open issues and PRs… Outputs a ranked list with rationale per item, not a fix') and when via an explicit 'Use when the user asks…' clause.

3 / 3

Trigger Term Quality

Includes natural user utterances verbatim — "what should I tackle first as core maintainer", "which PRs are production-ready", "triage backlog", "scan open issues" — giving good coverage of phrases a maintainer would actually say.

3 / 3

Distinctiveness Conflict Risk

Scoped to a single repo ('stickerdaniel/linkedin-mcp-server') and a specific maintainer-prioritisation niche, giving it a clear, conflict-resistant trigger surface.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

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.