github-deep-research
Conduct multi-round deep research on any GitHub Repo. Use when users request comprehensive analysis, timeline reconstruction, competitive analysis, or in-depth investigation of GitHub. Produces structured markdown reports with executive summaries, chronological timelines, metrics analysis, and Mermaid diagrams. Triggers on Github repository URL or open source projects.
npx skills add majiayu000/claude-skill-registry --skill github-deep-research --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# GitHub Deep Research Skill Multi-round research combining GitHub API, web_search, web_fetch to produce comprehensive markdown reports. ## Research Workflow - Round 1: GitHub API - Round 2: Discovery - Round 3: Deep Investigation - Round 4: Deep Dive ## Core Methodology ### Query Strategy **Broad to Narrow**: Start with GitHub API, then general queries, refine based on findings. ``` Round 1: GitHub API Round 2: "{topic} overview" Round 3: "{topic} architecture", "{topic} vs alternatives" Round 4: "{topic} issues", "{topic} roadmap", "site:github.com {topic}" ``` **Source Prioritization**: 1. Official docs/repos (highest weight) 2. Technical blogs (Medium, Dev.to) 3. News articles (verified outlets) 4. Community discussions (Reddit, HN) 5. Social media (lowest weight, for sentiment) ### Research Rounds **Round 1 - GitHub API** Directly execute `scripts/github_api.py` without `read_file()`: ```bash python /path/to/skill/scripts/github_api.py <owner> <repo> summary python /path/to/skill/scripts/github_api.py <owner> <repo> readme python /path/to/skill/scripts/github_api.py <owner> <repo> tree ``` **Available commands (the last argument of `github_api.py`):** - summary - info - readme
- Research Workflow
- Core Methodology
- Query Strategy
- Research Rounds
- Report Structure
- Mermaid Diagrams
- Confidence Scoring
- Output
- Formatting Rules
- Best Practices
python /path/to/skill/scripts/github_api.py <owner> <repo> summary python /path/to/skill/scripts/github_api.py <owner> <repo> readme python /path/to/skill/scripts/github_api.py <owner> <repo> tree
What does the github-deep-research skill do?
Conduct multi-round deep research on any GitHub Repo. Use when users request comprehensive analysis, timeline reconstruction, competitive analysis, or in-depth investigation of GitHub. Produces structured markdown reports with executive summaries, chronological timelines, metrics analysis, and Mermaid diagrams. Triggers on Github repository URL or open source projects.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill github-deep-research --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.