Hermes skill github pr monitor

Skill web3blind/hermes-skill-github-pr-monitor

Monitor newly created GitHub pull requests in configured public repositories or owner accounts. Use when you need a cron-friendly notification that reports only PRs not seen before.From its SKILL.md

Install

npx -y skills add web3blind/hermes-skill-github-pr-monitor

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.7 KB, 532 tokens by cl100k_base, as published. Nobody here has run it

github-pr-monitor

Cron-friendly wrapper around scripts/check-new-prs.js for monitoring newly created pull requests in public GitHub repositories.

The skill is intentionally generic: configure the owners/repositories in config.json created from config.example.json. Runtime state stays local in state.json and is ignored by git.

What it does

Reads configured GitHub owners or repositories from config.json.
Queries the public GitHub API for pull requests.
Reports only PRs that are not already present in state.json.
Stays silent when there are no new PRs.
On first normal run, bootstraps state without spamming old PRs.

Setup

cd skills/github-pr-monitor
cp config.example.json config.json
cp state.example.json state.json

Edit config.json and replace example owners with the GitHub accounts or organizations you want to monitor.

Run manually

node scripts/check-new-prs.js --dry-run
node scripts/check-new-prs.js

From a workspace root:

node skills/github-pr-monitor/scripts/check-new-prs.js --config skills/github-pr-monitor/config.json --state skills/github-pr-monitor/state.json --dry-run

Cron

Example daily script-only job:

hermes cron create --name github-pr-monitor-daily --schedule "0 17 * * *" --script github_pr_monitor.sh --no-agent

The wrapper script should run node .../scripts/check-new-prs.js with explicit --config and --state paths. Keep local state files out of git.

Output rules

Keep notifications short.
Do not translate PR titles or URLs.
If the script prints nothing, treat that as “no new PRs”.
If GitHub is temporarily unavailable or rate-limited, report the error without inventing PR status.

Pitfalls

state.json is a deduplication baseline, not a source of current PR truth. If a user asks whether a PR is still open, query GitHub live.
Public API rate limits are lower without a token. If needed, set GITHUB_TOKEN locally, but never commit it.
Do not commit config.json if it contains private repositories, internal owner names, or delivery targets.

Verification

Run with --dry-run; it should print candidate output without changing state.
Run normally once; it should create/update state.json.
Run normally a second time; stdout should be empty if no new PR appeared.

What ships with it: 6 files

14.1 KB alongside SKILL.md, 1 of them executable

scripts/

check-new-prs.jsruns12.9 KB