agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/vscode-team-kit/github-inbox/skills/inbox-get-notification-details/SKILL.md

inbox-get-notification-details

Skill65 starsChanged 16 days agoMITView on GitHub

Get details of a specific GitHub notification thread

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    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 details of a specific notification thread or issue/PR comments.

    line 10
  2. Very specific:

    Run each gh api command as a separate terminal invocation — NEVER chain with &&

    line 34
  3. Very specific:

    Use --jq for filtering — it is built into gh

    line 35

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

Get Notification Details

Use gh api to fetch details of a specific notification thread or issue/PR comments.

Notification thread details

gh api /notifications/threads/{thread_id}

Issue comments (latest)

gh api repos/{owner}/{repo}/issues/{number}/comments --jq '.[-1] | {user: .user.login, body: .body}'

PR comments (latest)

gh api repos/{owner}/{repo}/pulls/{number}/comments --jq '.[-1] | {user: .user.login, body: .body}'

Replace {thread_id}, {owner}, {repo}, {number} with actual values.

Rules

  • Run each gh api command as a separate terminal invocation — NEVER chain with &&
  • Use --jq for filtering — it is built into gh

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.

Check your setup, free