Agent skill

ln-911-github-triager

Produces prioritized triage report from open GitHub issues, PRs, and discussions. Use when reviewing community backlog.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill ln-911-github-triager --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Allowed tools: BashRead
Path: skills/analysis/ln-911-github-triager/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

> **Paths:** File paths (`references/`, `../ln-*`) are relative to this skill directory. # ln-911-github-triager **Type:** L3 Worker (standalone) **Category:** 9XX Community Engagement **Invocation:** Standalone or as part of a broader community triage workflow Scans all open issues, PRs, and discussions in the current repository. Categorizes by urgency. Produces an actionable triage report. --- ## Arguments `$ARGUMENTS` controls scope and staleness threshold: | Token | Effect | Default | |-------|--------|---------| | `issues` | Scan issues only | All three | | `prs` | Scan PRs only | All three | | `discussions` | Scan discussions only | All three | | Number (e.g., `14`) | Staleness threshold in days | 7 | | `issues 30` | Combine: scope + threshold | -- | | `summary` | Compact output for coordinator: skip Phase 4 preview, return red flags + priority counts + metrics only | Full interactive report | Parse `$ARGUMENTS`: extract scope tokens (`issues`, `prs`, `discussions`), numeric threshold, and `summary` flag. If no scope tokens, scan all three. If no number, default to 7 days. --- ## Phase 0: GitHub Discovery **MANDATORY READ:** Load `references/community_github_discovery.md` Exe

What's inside
Steps it walks through
  1. Arguments
  2. Phase 0: GitHub Discovery
  3. Phase 1: Fetch Data
  4. 1a. Issues
  5. 1b. Pull Requests
  6. 1c. Discussions (GraphQL)
  7. Phase 2: Classify Each Item
  8. Priority Matrix
  9. Maintainer Detection
  10. Staleness Calculation
  11. Label Urgency Signals
  12. Phase 3: Engagement Metrics
  13. Phase 4: Preview Table
  14. Phase 5: Compose Report
Ships with 1 file
  • metadata.json
Commands it runs
gh issue list --repo {owner}/{repo} --state open --limit 100 --json number,title,labels,createdAt,updatedAt,author,comments,assignees
gh api graphql -f query='
nodes {
number
title
category { name }
createdAt
updatedAt
author { login }
answerChosenAt
More from claude-skill-registry
All skills →
About this skill
What does the ln-911-github-triager skill do?

Produces prioritized triage report from open GitHub issues, PRs, and discussions. Use when reviewing community backlog.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill ln-911-github-triager --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going