webjs-list-todos
Skill28 starsChanged 36 days agoMITView on GitHub
Use this skill when the user asks what work is open or pending on the webjsdev/webjs project board. Trigger phrases include "what are the current todo items", "what's pending", "list todos", "what's open", "what should I work on", "show me the open issues", "any open work for webjs", "what's in progress", "what's on the board", or any natural-language query about open items on the webjs project at https://github.com/orgs/webjsdev/projects/1. The skill calls `gh project item-list` and returns a bucketed view (Todo / In progress / Done) so the user sees the current state straight from the source of truth.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- gallery/AGENTS.mdAGENTS.md
- website/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- website/CLAUDE.mdCLAUDE.md
- webjsSkill
- pr-reviewSkill
- use-railwaySkill
- webjs-blog-writeSkill
- webjs-doc-syncSkill
- webjs-file-issueSkill
- webjs-instagram-postSkill
- webjs-ready-for-devSkill
- webjs-research-recordSkill
- webjs-scaffold-syncSkill
- webjs-start-workSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
Call it ONCE per invocation and reuse the result: Never in a loop, and never a second time to answer a follow-up about one card.
- Very specific: line 39
Do not re-run it to check one issue: If the user asks about a specific number after this ran, use the single-node lookup in …
- Distinctive: line 63
If everything is in Done or the board is empty, say so explicitly.
- Very specific: line 67
Does not move cards, file new issues, or open PRs.
- Distinctive: line 68
Does not show closed issues outside the project board.
- Very specific: line 69
Does not consult ~/.claude/projects/.../memory/ or any internal task tracker.
- Very specific: line 73
If gh returns an auth error: surface it directly to the user and suggest gh auth refresh -s project.
- Distinctive: line 74
If the project list is empty: report "Project board is empty" instead of fabricating items.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
List open work on the webjs project board
The webjsdev/webjs project tracks work on the GitHub Project at https://github.com/orgs/webjsdev/projects/1. This skill returns a current snapshot bucketed by Status, queried straight from GitHub. Do NOT consult internal task trackers or memory for this question.
Steps
Fetch the board state.
gh project item-list 1 --owner webjsdev --format json --limit 20000This is the ONE place a whole-board dump is legitimate, because this skill renders every card. Everywhere else, reach a single card from its issue node instead; see
.claude/gh-budget.md.The dump is expensive even so. It paginates the entire board (past 500 items) at 100 per page, and the GraphQL budget is scored in points rather than requests, so it is worth several hundred points of the hourly 5000. Two rules follow, and neither is optional:
- Call it ONCE per invocation and reuse the result. Never in a loop, and never a second time to answer a follow-up about one card.
- Do not re-run it to check one issue. If the user asks about a specific
number after this ran, use the single-node lookup in
.claude/gh-budget.md.
--limit 20000is load-bearing, not defensive: the default page is 30, so without it the board silently truncates and buckets come back wrong.- Bucket by Status (Todo, In progress, Done) and pretty-print each bucket with issue numbers and titles. If the user explicitly asked for only one bucket (e.g. "what's in progress"), filter accordingly.
- Default presentation. Show Todo and In progress always. Show Done only if the user asks for it, or if both Todo and In progress are empty.
- For each item, show:
#<number> <title>. Wrap in markdown so the user can click through.
Example output shape
Todo:
#112 Elide browser download of display-only component modules
#113 Ship pre-built dist/ alongside src/ for @webjsdev/core
#114 Rate-limit defaultKey trusts unverified X-Forwarded-For
In progress:
(none)If everything is in Done or the board is empty, say so explicitly.
What this skill does NOT do
- Does not move cards, file new issues, or open PRs. Those are sibling skills (
webjs-start-work,webjs-file-issue). - Does not show closed issues outside the project board.
- Does not consult
~/.claude/projects/.../memory/or any internal task tracker.
Failure handling
- If
ghreturns an auth error: surface it directly to the user and suggestgh auth refresh -s project. - If the project list is empty: report "Project board is empty" instead of fabricating items.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

