Home / jerseycheese / agent-skills · GitHub

prioritize-issues SKILL.md skillA

prioritize-issues from jerseycheese/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add jerseycheese/agent-skills/prioritize-issues@git:20261016.291aa03

Pins git:20261016.291aa03 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: jerseycheese/agent-skills
Path: skills/prioritize-issues/SKILL.md
Versions recorded: 4
Latest version: git:20261016.291aa03, committed Oct 16, 2026
First version recorded: Jun 28, 2026
Size: 10,853 bytes
Repository stars: 3
License: MIT

Scores all open GitHub issues by value, effort, age, and roadmap fit, and returns a ranked top 5 with specs for the top 3. Read-only. Use when picking the next issue or triaging a backlog. Trigger on: "what should I work on", "prioritize my issues", "triage my backlog", "what's worth doing next".

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Issue Prioritization

## 1. Discover the repo

If the user didn't specify a repo, infer it:

```bash
gh repo view --json nameWithOwner -q .nameWithOwner
```

## 2. Fetch all open issues

Pull the full backlog — not just recent issues:

```bash
gh issue list --state open --limit 200 --json number,title,labels,createdAt,body,milestone,comments,state
```

If the repo has more than 200 open issues, paginate. Also fetch any recent comments on the top candidates to catch context updates:

```bash
gh issue view [NUMBER] --json number,title,body,labels,comments,createdAt,milestone,state
```

### Milestones

An issue's `milestone` field gives you a name, not a status. Fetch the milestone list separately,
because the name alone can't tell you whether that milestone is active, shipped, or aspirational:

```bash
gh api repos/OWNER/REPO/milestones --jq '.[] | "\(.title): open=\(.open_issues) closed=\(.closed_issues) due=\(.due_on)"'
```

The active milestone is the open one with the nearest due date; if none carry due dates, it's the
one with issues closing against it recently. Write down the open/closed split for each — that
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add jerseycheese/agent-skills/prioritize-issues@sha256:67272ad9a2caac97

The line at the top of this page pins the label git:20261016.291aa03, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_isnajq64izzi7bm2.svg)](https://markdownregistry.com/a/art_isnajq64izzi7bm2)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 4 versions of this file, between Jun 28, 2026 and Oct 16, 2026, about one every 37 days.

version	committed	commit	size	audit
git:20261016.291aa03 latest	2026-10-16	291aa03	10,853 B	A	view · diff
git:20261016.04e815b	2026-10-16	04e815b	10,353 B	A	view · diff
git:20260913.b97f065	2026-09-13	b97f065	10,536 B	A	view · diff
git:20260628.9366aee	2026-06-28	9366aee	5,043 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (10853 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

jerseycheese/agent-skills · 3 stars · license MIT · pushed 2026-10-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_isnajq64izzi7bm2
GET https://markdownregistry.com/api/v1/resolve?ref=jerseycheese/agent-skills/prioritize-issues
GET https://markdownregistry.com/api/v1/blob/67272ad9a2caac9730eb406cfc49e90c769fc8398ef4a2bf20c7cb4c0d5d2f75

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from jerseycheese/agent-skills

abstraction-finder SKILL.md skill

jerseycheese/agent-skills · skills/abstraction-finder/SKILL.md · Finds recurring patterns worth extracting into shared code and proposes the smallest form for each (helper, util, base…