github

Fetch GitHub HTML pages and parse repository metadata with cheerio.

5|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/AgentComputerAI/torch --skill github-agentcomputerai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/AgentComputerAI/torch/tree/main/skills/sites/github
Command: npx skills add https://github.com/AgentComputerAI/torch --skill github-agentcomputerai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub's public HTML pages are fully server-rendered with no JS gating and no bot protection on unauthenticated GETs. A one-shot fetch + cheerio parse is all you need. Only reach for the REST API (api.github.com) when you hit the 60 req/hr unauthenticated limit or need structured fields (topics, license, default branch) not present on the HTML.

Core Features & Use Cases

  • HTML-only scraping of public GitHub pages using a simple fetch + cheerio workflow.
  • Metadata extraction: owner, repo, description, language, stars, forks, topics, and URLs from HTML.
  • Use Case: Quickly enumerate trending repositories or public project pages without API keys, then optionally fetch additional data via the REST API if needed.

Quick Start

Point the tool at a GitHub page (e.g., https://github.com/trending) and extract core repository metadata with a lightweight fetch + cheerio routine.

Frequently Asked Questions about github

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

FAQPage Schema
How do I scrape GitHub public pages without using the REST API?

To extract GitHub repository metadata, fetch the target public HTML page and use a cheerio routine to parse DOM elements, mapping fields like owner, name, description, and language directly from the HTML structure.

What GitHub repository metadata can I extract from public HTML?

GitHub public HTML scraping supports extracting owner, repo name, description, language, stars, forks, topics, and URLs, providing core repository metadata without requiring API keys or authentication tokens.

Does GitHub HTML scraping work for trending lists and user pages?

GitHub HTML scraping handles trending lists, repositories, and user pages effectively, as these public pages are server-rendered without JavaScript gating, allowing straightforward data extraction via fetch and cheerio.

When should I use the GitHub REST API instead of HTML scraping?

Switch to the GitHub REST API when you exceed the 60 requests per hour unauthenticated limit or require structured metadata fields like topics, license, and default branch that are not available on the rendered HTML pages.

Do I need authentication tokens for web scraping GitHub repositories?

Web scraping GitHub repositories via public HTML does not require authentication tokens for unauthenticated GET requests, but you will face a 60 requests per hour limit if you do not provide an API key.