Provides a typed pagination wrapper for the GitHub REST API using Octokit.js and the @octokit/plugin-paginate-rest plugin. Handles Link header parsing, rate limit detection via X-RateLimit-Remaining, and automatic retry with exponential backoff. Supports listing issues, pull requests, commits, and workflow runs with async iterator patterns.
Scanned 6/8/2026
Install via CLI
openskills install agentskillexchange/skills---
name: "GitHub REST API Paginator Library"
slug: "github-rest-api-paginator-library"
description: "Provides a typed pagination wrapper for the GitHub REST API using Octokit.js and the @octokit/plugin-paginate-rest plugin. Handles Link header parsing, rate limit detection via X-RateLimit-Remaining, and automatic retry with exponential backoff. Supports listing issues, pull requests, commits, and workflow runs with async iterator patterns."
github_stars: 58
verification: "security_reviewed"
source: "https://github.com/octokit/plugin-paginate-rest.js"
author: "Octokit"
category: "Library & API Reference"
framework: "Codex"
tool_ecosystem:
github_repo: "octokit/plugin-paginate-rest.js"
github_stars: 58
npm_package: "@octokit/plugin-paginate-rest"
npm_weekly_downloads: 26656585
---
# GitHub REST API Paginator Library
Provides a typed pagination wrapper for the GitHub REST API using Octokit.js and the @octokit/plugin-paginate-rest plugin. Handles Link header parsing, rate limit detection via X-RateLimit-Remaining, and automatic retry with exponential backoff. Supports listing issues, pull requests, commits, and workflow runs with async iterator patterns.
## Installation
Requirements and caveats from upstream:
- Node
- If your target runtime environments supports async iterators (such as most modern browsers and Node 10+), you can iterate through each response
- The compose* methods work just like their octokit.* counterparts described above, with the differenct that both methods require an octokit instance to be passed as first argument
Basic usage or getting-started notes:
- <table>
- <tbody valign=top align=left>
- <tr><th>
- Source: https://github.com/octokit/plugin-paginate-rest.js
- Extracted from upstream docs: https://raw.githubusercontent.com/octokit/plugin-paginate-rest.js/HEAD/README.md
## Documentation
- https://github.com/octokit/plugin-paginate-rest.js#readme
## Source
- [Agent Skill Exchange](https://agentskillexchange.com/skills/github-rest-api-paginator-library/)
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.