agentleFS
MicrosoftKnown publishermicrosoft/vscode-team-kit/github-inbox/skills/inbox-list-notifications/SKILL.md

inbox-list-notifications

Skill65 starsChanged 16 days agoMITView on GitHub

Fetch GitHub notifications using the gh CLI

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
  1. Very specific:

    Use gh api to fetch all unread GitHub notifications with automatic pagination.

    line 10
  2. Very specific:

    Use the --jq flag (NOT a pipe to jq) to filter output inline:

    line 14
  3. Very specific:

    NEVER: add 2>/dev/null or any redirects

    line 25
  4. Distinctive:

    NEVER: add other environment variable prefixes

    line 28
  5. Very specific:

    Participating only: Add --method GET -f participating=true

    line 34
  6. Very specific:

    Include read: Add --method GET -f all=true

    line 35
  7. Very specific:

    Specific repo: Use gh api /repos/{owner}/{repo}/notifications --paginate --jq '...'

    line 36
  8. Very specific:

    Since date: Add -f since=2024-01-01T00:00:00Z

    line 37

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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/null or any redirects
  • NEVER wrap the command in a script
  • ALWAYS prepend GH_PAGER=cat to gh api calls to avoid interactive pagers
  • NEVER add other environment variable prefixes
  • The --jq flag handles all JSON filtering — no external tools needed
  • The --paginate flag 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):

  1. security_alert (critical)
  2. assign (high)
  3. review_requested (high)
  4. mention (high)
  5. ci_activity (medium)
  6. comment (medium)
  7. team_mention (medium)
  8. state_change (medium)
  9. author (low)
  10. subscribed (low)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.