Bai Ready
- 2 installs
- Updated May 24, 2026
- black-atom-industries/ai
bai-ready is a Claude Code skill that lists Black Atom GitHub issues ready to work, filtering out blocked ones and sorting by priority.
About
bai-ready is a Claude Code skill that shows which Black Atom GitHub issues are ready to pick up. It fetches your assigned open issues via the gh CLI, filters out any labeled state:blocked, pulls priority from the GitHub project board, and sorts them Urgent first. Blocked issues are listed separately with what they are waiting on. A developer uses it to decide what to work on next without manually triaging the board.
- Lists your assigned open GitHub issues that are ready to work, filtering out anything labeled state:blocked
- Pulls priority from GitHub project data and sorts Urgent first
- Shows blocked issues separately with the 'Blocked by' items scanned from comments
Bai Ready by the numbers
- 2 all-time installs (skills.sh)
- Ranked #2,419 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
bai-ready capabilities & compatibility
- Capabilities
- issue triage · task prioritization · project management
- Works with
- github
- Use cases
- project management · planning
What bai-ready says it does
Show Black Atom issues ready to work (no blockers)
Show issues that are ready to pick up — not blocked by other issues.
An issue is "ready" if it does NOT have the `state:blocked` label
npx skills add https://github.com/black-atom-industries/ai --skill bai-readyAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| Last updated | May 24, 2026 |
| Repository | black-atom-industries/ai ↗ |
What it does
Show assigned GitHub issues that are ready to work, sorted by priority, with blocked ones listed separately.
Who is it for?
Developers on the Black Atom project deciding their next task from the issue board.
Skip if: Repos or projects outside the black-atom-industries owner and its Black Atom V1 project.
When should I use this skill?
You want to see which assigned issues are ready to pick up, not blocked by others.
What you get
A priority-sorted list of ready issues plus a separate list of blocked issues showing what each is waiting on.
- priority-sorted list of ready issues
- separate list of blocked issues with their blockers
By the numbers
- 4 priority levels: Urgent, High, Medium, Low
- GitHub project #7 (Black Atom V1)
Files
Black Atom Ready
Show issues that are ready to pick up — not blocked by other issues.
Arguments
Optional repo name filter ($ARGUMENTS in Claude Code, or /skill:bai-ready args in Pi).
Context
Repos: Discover dynamically via gh repo list black-atom-industries --json name --jq '.[].name' --limit 100 Project: Black Atom V1 (#7)
Load about:bai for GitHub project constants.
Process
1. Get all assigned open issues:
gh search issues --assignee=@me --owner=black-atom-industries --state=open --json repository,number,title,labels,url2. Filter out issues that have the state:blocked label
3. Get priority from project data:
gh project item-list 7 --owner black-atom-industries --format json4. Sort by priority (Urgent first)
5. For blocked issues, scan comments for "Blocked by" to show what they're waiting on:
gh issue view <number> --repo black-atom-industries/<repo> --json comments --jq '.comments[].body'Output Format
### Ready to Work
1. [core#50] Finalize naming conventions (Urgent)
Repo: core
https://github.com/black-atom-industries/core/issues/50
2. [livery#29] Set up frontend architecture (High)
Repo: livery | Milestone: v1.0.0
https://github.com/black-atom-industries/livery/issues/29
### Blocked (for reference)
- [core#53] Fine-tune all themes for V1
Blocked by: core#50, core#51
https://github.com/black-atom-industries/core/issues/53Notes
- An issue is "ready" if it does NOT have the
state:blockedlabel - Show blocked issues separately so you know what's waiting
- Prioritize by priority level (Urgent → High → Medium → Low)
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
How does bai-ready decide an issue is ready?
An issue is ready if it does NOT have the state:blocked label; blocked issues are shown separately.
How are issues ordered?
By priority level from the project data, Urgent first, then High, Medium, and Low.