worklist

Reports project status and next unblocked work by running the worklist script.

1|Updated Nov 21, 2015
One-click install
npx skills add https://github.com/mark-brannan/dotfiles --skill worklist-mark-brannan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: worklist
Source: https://github.com/mark-brannan/dotfiles/tree/main/.claude/skills/worklist
Command: npx skills add https://github.com/mark-brannan/dotfiles --skill worklist-mark-brannan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It answers "what's next" and "what's outstanding" across a project's GitHub repos without manually checking PRs, issues, branches, and boards, by running one read-only script and reporting its output. ## Core Features & Use Cases - Status reporting: Runs ~/.local/bin/worklist [project] and relays bucketed output covering ready issues, blocked issues, PRs awaiting review, stranded branches, and board cards. - Milestone scoping: --milestone <title> filters Ready, Blocked, and Untriaged buckets to a specific milestone while leaving PR and board sections unscoped. - Fresh vs cached data: --fresh bypasses the cache when current state is needed; --json emits the same filtered data as structured records. - Use Case: When asked "what can we work on" or "what's stale", run the script, report the buckets verbatim, and stop without filing, labeling, or editing anything. ## Quick Start Ask the assistant to run the worklist skill to show the project's current status and next unblocked work.

Frequently Asked Questions about worklist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check what work is next on a GitHub project?▼

Run the worklist script with the project name to get bucketed output of ready issues, blocked issues, PRs awaiting review, and board cards. Add --fresh when you need current state instead of cached results.

How do I filter project status to a specific milestone?▼

Pass --milestone with the milestone title to scope the Ready, Blocked, and Untriaged buckets to open issues on that milestone. PR buckets, stranded branches, and board sections remain unscoped, and the filter applies at render time so one cache serves both views.

Does the worklist report modify issues or boards?▼

No, the skill is strictly read-only. It runs the script and reports output without filing, labeling, ticking, or editing anything, even for sweeps, reconciles, or stale checks.

Why does a worklist bucket show a failure line instead of results?▼

Failure lines indicate per-cause problems such as missing gh CLI, unauthenticated gh, a 403 on a repo, or network errors. A bucket missing for these reasons is not an empty bucket and should be reported as a failure.

What does an empty bucket mean in the worklist output?▼

An empty bucket prints "none", which means the check ran and found nothing there. It is a successful result, not a failure, and should be reported as such.