# 1 Triage Issues

Triage backlog, scan open issues, rank what to tackle first, or which PRs are...

- Repository: https://github.com/stickerdaniel/linkedin-mcp-server (4081 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add stickerdaniel/linkedin-mcp-server --skill 1-triage-issues -g -a claude-code -y`
Codex: `npx skills add stickerdaniel/linkedin-mcp-server --skill 1-triage-issues -g -a codex -y`
Cursor: `npx skills add stickerdaniel/linkedin-mcp-server --skill 1-triage-issues -g -a cursor -y`
Gemini CLI: `npx skills add stickerdaniel/linkedin-mcp-server --skill 1-triage-issues -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add stickerdaniel/linkedin-mcp-server`

## Description

Triage backlog, scan open issues, rank what to tackle first, or which PRs are production-ready.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Triage open issues and PRs

Turn the live state of `stickerdaniel/linkedin-mcp-server` into a maintainer priority list. Read-only. No checkout, no labels, no comments, no closure, no reproduction.

Reproduction belongs in `/2-repro-issue`. PR verification belongs in `/3-verify-pr-fix`.

## Inputs

`$ARGUMENTS` is optional. If set, treat as a label name (`bug`, `enhancement`) or freetext filter. Otherwise scan everything open.

## 1. Gather

```bash
REPO=stickerdaniel/linkedin-mcp-server

# Issues  (gh calls the reactions field `reactionGroups`, not `reactions`)
gh issue list --repo $REPO --state open --limit 200 \
  --json number,title,labels,createdAt,updatedAt,author,comments,reactionGroups,body

# PRs
gh pr list --repo $REPO --state open --limit 100 \
  --json number,title,labels,createdAt,updatedAt,author,mergeable,mergeStateStatus,statusCheckRollup,additions,deletions,changedFiles,reviewDecision,isDraft,headRepositoryOwner

# Cross-link issues ↔ PRs via body references
gh search prs --repo $REPO --state open --json number,body,title --limit 100
```

Build a map `issue_number → [referencing_pr_numbers]` by scanning PR bodies for `Closes #`, `Fixes #`, `Resolves #`, plain `#N`.

If `$ARGUMENTS` is given, filter both lists before scoring.

Read each issue body and its comments, including linked canonical issues.

## 2. Packet admission

Before severity, age, reach, or contributor ranking, classify every open issue.

The rest: https://github.com/stickerdaniel/linkedin-mcp-server/blob/HEAD/.agents/skills/1-triage-issues/SKILL.md