github-activity-poll

Polls GitHub repository public event feeds using conditional HTTP requests.

3|2|Updated May 12, 2026
One-click install
npx skills add https://github.com/kriscendobot/garden --skill github-activity-poll
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-activity-poll
Source: https://github.com/kriscendobot/garden/tree/main/skills/github-activity-poll
Command: npx skills add https://github.com/kriscendobot/garden --skill github-activity-poll

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inefficiently polling GitHub repositories for updates, which often leads to hitting API rate limits and wasting bandwidth.

Core Features & Use Cases

  • Conditional Polling: Uses ETag and Last-Modified headers to perform 304 Not Modified checks, preserving your API rate limit.
  • Event Tracking: Automatically tracks the latest event IDs to ensure no activity is missed or processed twice.
  • Use Case: Ideal for building automated watchers or triagers that need to react to new PRs, issues, or pushes in real-time without exceeding GitHub's REST API constraints.

Quick Start

Use the github-activity-poll skill to monitor the anthropics/claude-code repository for new public events and save the state to the activity-poll directory.

Frequently Asked Questions about github-activity-poll

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor GitHub repository activity without hitting API rate limits?

To monitor GitHub repository activity without hitting API rate limits, use conditional polling with ETag and Last-Modified headers. This performs 304 Not Modified checks to preserve your API rate limit while reliably tracking new public events.

What is conditional polling for GitHub public event feeds?

Conditional polling for GitHub public event feeds is a stateful mechanism that tracks ETag and Last-Modified headers to detect repository changes. It automatically tracks the latest event IDs to ensure no activity is missed or processed twice.

How do I build an automated watcher to react to new PRs and issues on GitHub?

To build an automated watcher for new PRs and issues, implement a stateful polling mechanism that deduplicates event processing by tracking event IDs. This allows automated triagers to react to new pushes and updates in real-time.

Does GitHub API conditional polling prevent duplicate event processing?

Yes, GitHub API conditional polling prevents duplicate event processing by automatically tracking the latest event IDs. This ensures no repository activity is missed or processed twice across polling intervals.

Why does my GitHub monitoring script keep exceeding the REST API constraints?

Your GitHub monitoring script exceeds REST API constraints because it inefficiently polls repositories without conditional HTTP requests. Using ETag and Last-Modified headers minimizes API rate limit consumption and prevents this issue.