agentleFS
lordmaculordmacu/nexo-rs/skills/github/SKILL.md

GitHub

Skill8 starsChanged 7 months agoApache-2.0View on GitHub

Read pull requests, issues and CI checks via GitHub REST API.

  • Reads credentials

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

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

  • 0

    Common

    Most of the 151 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    Use this skill for repository operations: pull requests, issues, CI checks.

    line 12
  2. Very specific:

    No arguments. Returns whether GITHUB_TOKEN is set and, if so, the authenticated user.

    line 32
  3. Very specific:

    Start with status if uncertain about auth (verifies token + lists default repo).

    line 64
  4. Very specific:

    If error code is -32011 (unauthorized) → GITHUB_TOKEN is missing or invalid.

    line 65
  5. Very specific:

    If -32013 (rate limited) → wait until the reset_at epoch in the message.

    line 66
  6. Very specific:

    Prefer pr_checks over pr_view when the user asks "what is failing in PR X".

    line 68

“Common” is measured: kept by at least 6 in 10 of the 151 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

Use this skill for repository operations: pull requests, issues, CI checks. Backed by the github extension which calls the GitHub REST API directly with a Personal Access Token. No gh CLI dependency.

Use when

  • "List open PRs in <repo>"
  • "Show details of PR 123"
  • "Check CI status of PR 7"
  • "List open issues"

Do not use when

  • Cloning, committing, or pushing code → use git directly
  • Creating PRs / issues (write operations) → not exposed in this version
  • Searching across many repos → REST search is not exposed; ask the user to use the GitHub UI

Tools

status

No arguments. Returns whether GITHUB_TOKEN is set and, if so, the authenticated user.

pr_list

  • repo (string) — owner/repo. Falls back to GITHUB_DEFAULT_REPO.
  • state (string, optional) — open|closed|all. Default open.
  • limit (integer, optional) — 1–100, default 20.

Returns {repo, state, limit, count, pulls: [{number, title, state, draft, user, head_sha, base_ref, html_url, created_at, updated_at}]}.

pr_view

  • repo (string, optional)
  • number (integer, required)

Returns the raw GitHub PR object.

pr_checks

  • repo (string, optional)
  • number (integer, required)

Two-step: fetches the PR to get the head SHA, then fetches check-runs. Returns {repo, number, head_sha, checks: {total_count, check_runs: [...]}}.

issue_list

  • repo (string, optional)
  • state (string, optional)
  • limit (integer, optional, 1–100)

Returns issues with PRs filtered out (pull_request field absent).

Execution guidance

  • Start with status if uncertain about auth (verifies token + lists default repo).
  • If error code is -32011 (unauthorized) → GITHUB_TOKEN is missing or invalid; ask the operator.
  • If -32013 (rate limited) → wait until the reset_at epoch in the message.
  • Pass explicit repo only when different from GITHUB_DEFAULT_REPO.
  • Prefer pr_checks over pr_view when the user asks "what is failing in PR X".

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.