| name | github-notification-triage |
| description | Triage GitHub notifications and report actions needed. |
| user-invocable | false |
| context | fork |
| allowed-tools | ["Bash","Read","Write"] |
| routing | {"triggers":["github notifications","triage notifications","check notifications","notification cleanup","github inbox"],"pairs_with":[],"complexity":"Simple","category":"github"} |
GitHub Notification Triage Skill
Fetch, classify, and report on GitHub notifications. The script does the heavy lifting — this skill orchestrates invocation and presents results.
Commands
python3 scripts/github-notification-triage.py
python3 scripts/github-notification-triage.py --mark-read
python3 scripts/github-notification-triage.py --save
python3 scripts/github-notification-triage.py --mark-read --save
Instructions
Step 1: Run the triage script
Run report-only by default:
python3 scripts/github-notification-triage.py
Step 2: Present the report
Display the script output directly to the user. The report classifies notifications into:
- Action required — PRs awaiting review, mentions, assigned issues
- Informational — CI results, bot comments, automated updates (safe to clear)
Step 3: Handle follow-up
If the user responds with any of the following, re-run with --mark-read:
- "clean them up"
- "mark read"
- "clear the noise"
- "yes" (in response to a prompt about clearing informational items)
python3 scripts/github-notification-triage.py --mark-read
Confirm how many notifications were marked read after the run completes.
Cron/scheduled mode
When invoked on a schedule (no interactive user), use both flags to auto-clear and persist the report:
python3 scripts/github-notification-triage.py --mark-read --save
Exit Codes
| Code | Meaning |
|---|
| 0 | Success |
| 1 | Error (auth failure, API error, script not found) |