inbox-list-notifications
Skill65 starsChanged 16 days agoMITView on GitHub
Fetch GitHub notifications using the gh CLI
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- manage-bansSkill
- build-healthSkill
- setup-component-explorer-fullSkill
- setup-component-explorer-lightSkill
- setup-component-explorerSkill
- use-component-explorerSkill
- debugSkill
- inbox-add-reactionSkill
- inbox-dismiss-notificationSkill
- inbox-get-notification-detailsSkill
- inbox-install-gh-cliSkill
- inbox-manage-subscriptionSkill
- inbox-mark-all-readSkill
- inbox-memorySkill
- inbox-open-notificationSkill
- inbox-search-issuesSkill
- inbox-setupSkill
- council-planSkill
- council-reviewSkill
- monitor-prSkill
- my-issuesSkill
- my-work-setupSkill
- my-work-uiSkill
- generate-presentationSkill
- generate-videoSkill
- review-areasSkill
- review-planSkill
- session-timelineSkill
- generate-test-videoSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 1 is distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use gh api to fetch all unread GitHub notifications with automatic pagination.
- Very specific: line 14
Use the --jq flag (NOT a pipe to jq) to filter output inline:
- Very specific: line 25
NEVER: add 2>/dev/null or any redirects
- Distinctive: line 28
NEVER: add other environment variable prefixes
- Very specific: line 34
Participating only: Add --method GET -f participating=true
- Very specific: line 35
Include read: Add --method GET -f all=true
- Very specific: line 36
Specific repo: Use gh api /repos/{owner}/{repo}/notifications --paginate --jq '...'
- Very specific: line 37
Since date: Add -f since=2024-01-01T00:00:00Z
≈ “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 GitHub Notifications
Use gh api to fetch all unread GitHub notifications with automatic pagination.
Command
Use the --jq flag (NOT a pipe to jq) to filter output inline:
gh api /notifications --paginate --jq '.[] | {id, reason, unread, updated_at, repo: .repository.full_name, title: .subject.title, type: .subject.type, url: .subject.url}'This is the ONLY command you should run. Do NOT modify it. Do NOT add anything to it.
Rules
- NEVER pipe to
jq,python,python3, or any other program - NEVER add
2>/dev/nullor any redirects - NEVER wrap the command in a script
- ALWAYS prepend
GH_PAGER=cattogh apicalls to avoid interactive pagers - NEVER add other environment variable prefixes
- The
--jqflag handles all JSON filtering — no external tools needed - The
--paginateflag handles pagination — no manual page loops needed
Filters
- Participating only: Add
--method GET -f participating=true - Include read: Add
--method GET -f all=true - Specific repo: Use
gh api /repos/{owner}/{repo}/notifications --paginate --jq '...' - Since date: Add
-f since=2024-01-01T00:00:00Z
Constructing HTML URLs
The url field is an API URL like https://api.github.com/repos/owner/repo/pulls/123. Convert to a clickable URL:
- For pulls:
https://github.com/{repo}/pull/{number} - For issues:
https://github.com/{repo}/issues/{number}
Extract the number from the API URL's last path segment.
Priority
Sort notifications by reason priority (highest first):
security_alert(critical)assign(high)review_requested(high)mention(high)ci_activity(medium)comment(medium)team_mention(medium)state_change(medium)author(low)subscribed(low)
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.

