菜单
Monitor GitHub repositories for new issues, PRs, comments, and reviews on a schedule. Ready-to-use poller following the pollers.json contract. Install from ClawHub or copy into your agent's skills/ folder.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
How to choose between markdown, HTML messages, and UI plugins in the local web chat — and how to render each well. Use whenever you are about to call `send_message` to a web-chat channel, especially when the content has structure (rows, columns, statuses, a state machine, multiple linked things) or when the right answer is "let me show you", not "let me tell you". Do not use for Discord channels — HTML is rejected there.
Create and manage runtime command hooks declared in skills/*/hooks.json. Use when the user asks to intercept tool calls, augment prompts, audit or mutate tool arguments/results, add startup/shutdown scripts, or debug hook behavior.
Index of recurring problem shapes — environmental awareness (world-scanning, OS event hooks, browser automation), communication (messaging, multi-agent handoff, async waits), coordination between parallel things (avoiding collisions, oscillation, double-work), and self-correction (circuit-breaker, try-harder). Use when designing a non-trivial workflow, when the same shape just happened twice, or when the answer to "what should I do here?" isn't obvious. Don't read on every turn.
Structured root cause analysis for arriving at a concrete action. Use when something went wrong, a pattern keeps recurring, behavior has drifted, or you catch yourself resolving to "do better" / "remember to X" without a concrete artifact. Five-whys forces behavioral resolutions into file edits, config changes, memory block updates, or scheduled jobs — the action item must produce a diff someone else can verify. Do not use for simple debugging with an obvious cause.
Diagnose agent behavior using event logs, journal history, and scheduler state. Use when you need to understand why something went wrong, review your own patterns, audit scheduled jobs, or debug communication issues. Do not use for one-off messaging or memory management (use the memory skill instead).
Guide for the first days with a new human. Use when: the `init` memory block exists (pointing you here), you have no persona/communication blocks yet, or a human explicitly asks about setup. This skill is about having good conversations — not filling out forms.
| name | github-poller |
| description | Monitor GitHub repositories for new issues, PRs, comments, and reviews on a schedule. Ready-to-use poller following the pollers.json contract. Install from ClawHub or copy into your agent's skills/ folder. |
Monitors GitHub repositories for new activity. Emits events to the agent only when there's something actionable.
Install from ClawHub:
npx clawhub install github-poller
Or copy this skill directory into your agent's skills/ folder.
After installation, call reload_pollers to register the poller with the scheduler.
The poller reads credentials from the agent's environment (.env file or system env):
| Variable | Required | Description |
|---|---|---|
GITHUB_TOKEN | yes | GitHub personal access token or gh CLI token |
GITHUB_REPOS | yes | Comma-separated list of repos to monitor (e.g., owner/repo1,owner/repo2) |
Note: The gh CLI auth token works if gh is installed and authenticated. The poller tries gh auth token as a fallback if GITHUB_TOKEN isn't set.
The skill ships with a default pollers.json that polls every 15 minutes:
{
"pollers": [
{
"name": "github-activity",
"command": "python poller.py",
"cron": "*/15 * * * *"
}
]
}
Adjust the cron schedule as needed. For active repos, */5 * * * * works but watch API rate limits.
After installation, call reload_pollers to register the poller with the scheduler.
The poller emits events for:
Each event includes the repo, author, title/body, and URLs needed to act.
Requires either:
gh CLI installed and authenticated, ORGITHUB_TOKEN environment variable with repo read accessNo additional Python packages needed — uses subprocess to call gh API.