agentleFS
Sign inStart free
notquenotque/vexjoy-agent/skills/integrations/github/SKILL.md

github

Skill448 starsChanged 4 days agoMITView on GitHub

GitHub: notification triage, profile rule extraction.

166 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use taskflow-inbox-triage, BlueBubbles and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AtomicBot-aiSkill

    taskflow-inbox-triage

    Also in 6 projects that use this

  • jiulingyunSkill

    BlueBubbles

    为Clawdbot构建或更新BlueBubbles外部通道插件（扩展包，REST发送/探测，webhook入站）。

    Also in 20 projects that use this

  • hkyutongSkill

    node-connect

    Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

    Also in 18 projects that use this

  • molt-botSkill

    discord-e2e

    Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and Gateway evidence from manual user interactions.

    Also in 10 projects that use this

  • molt-botSkill

    openclaw-repair-sweep

    Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

    Also in 10 projects that use this

  • clawdbotSkill

    openclaw-performance

    Performance work in OpenClaw: a slow or heavy flow (latency, CPU, memory, SQL, RPC, renders), writing or reviewing a perf PR, or adding a cache. Count the work, delete waste first, cache last.

    Also in 7 projects that use this

  • +2 more from molt-bot

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 150 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the user says "clean them up", "mark read", "clear the noise", or "yes" to clearing informational items, re-run with --mark-read.

    line 67
  2. Distinctive:

    When triaging a queue of issues or PRs (not just notifications), produce one card per item.

    line 79
  3. Distinctive:

    When in doubt, label Needs-owner and state the decision the owner must make.

    line 120
  4. Distinctive:

    Before any local work on an item (checkout, tests, repro):

    line 124
  5. Very specific:

    If dirty, mark the card Needs-owner with blocker "dirty working tree in <repo>" and continue triaging from API data only.

    line 128

“Common” is measured: kept by at least 6 in 10 of the 150 edited versions of this file we could read. “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

GitHub Skill

GitHub notification triage and issue/PR queue classification.

Mode Selection

RequestMode
Notifications, inbox, cleanupNotification Triage
Issue or PR queue, review itemsQueue Triage

Notification Triage

Fetch, classify, and report GitHub notifications via the triage script.

Commands

# Report-only (default)
python3 scripts/github-notification-triage.py

# Mark informational notifications as read
python3 scripts/github-notification-triage.py --mark-read

# Save report to ~/.claude/reports/notifications/
python3 scripts/github-notification-triage.py --save

# Cron/scheduled: auto-clear noise and save
python3 scripts/github-notification-triage.py --mark-read --save

Steps

  1. Run report-only: python3 scripts/github-notification-triage.py.
  2. Display the output. The report classifies notifications as:
    • Action required -- PRs awaiting review, mentions, assigned issues.
    • Informational -- CI results, bot comments, automated updates.
  3. If the user says "clean them up", "mark read", "clear the noise", or "yes" to clearing informational items, re-run with --mark-read. Confirm how many were marked read.

Scheduled (no interactive user): run with --mark-read --save.

Exit codes: 0 = success, 1 = error (auth, API, script not found).

Queue Triage

When triaging a queue of issues or PRs (not just notifications), produce one card per item.

Card Format

Open each card with the item's full GitHub URL on its own line, then these fields in order:

FieldContent
WhatOne sentence: what the issue/PR asks or changes.
WhyMotivation or problem it addresses.
Author trustMaintainer, known contributor, first-timer, or bot. Cite prior merged PRs.
FitMatch to project scope and conventions.
RiskBlast radius: files touched, API/behavior changes, security or data paths.
Proof stateCI status, tests added, repro steps, screenshots. "Unverified" when none.
BlockerSingle thing stopping progress, or "None".
Next actionOne concrete step with named actor. Label Autonomous or Needs-owner.

Example:

https://github.com/owner/repo/pull/123
What: Adds retry with backoff to the webhook sender.
Why: Webhooks drop on transient 5xx from receivers.
Author trust: Known contributor, 4 merged PRs.
Fit: Matches existing client retry pattern in net/client.go.
Risk: Low — one module, behavior gated behind config flag.
Proof state: CI green; unit tests cover backoff schedule.
Blocker: None.
Next action: Autonomous — review and merge.

Autonomous vs Needs-owner

  • Autonomous -- the agent can complete the action alone: reply with a question, label, close an obvious duplicate, merge a green PR within granted authority, rebase.
  • Needs-owner -- requires owner judgment: scope decisions, breaking changes, security-sensitive merges, releases, money, or access.

When in doubt, label Needs-owner and state the decision the owner must make.

Clean-Checkout Gate

Before any local work on an item (checkout, tests, repro):

  1. Run git status --short.
  2. Proceed only when output is empty.
  3. If dirty, mark the card Needs-owner with blocker "dirty working tree in <repo>" and continue triaging from API data only.

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