科研 Skill
GitHub 深度研究助手
github-deep-research
深度分析 GitHub 仓库脉络
Skill 说明
对任一 GitHub 仓库做多轮深度研究,出含时间线 / 度量 / Mermaid 图的 MD 报告 | 输入:GitHub 仓库 URL | 输出:MD 报告(含时间线 / 度量 / Mermaid 架构图)
SKILL.md
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:
- Official docs/repos (highest weight)
- Technical blogs (Medium, Dev.to)
- News articles (verified outlets)
- Community discussions (Reddit, HN)
- Social media (lowest weight, for sentiment)
Research Rounds
Round 1 - GitHub API
Directly execute scripts/github_api.py without read_file():
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
- tree
- languages
- contributors
- commits
- issues
- prs
- releases
Round 2 - Discovery (3-5 web_search)
- Get overview and identify key terms
- Find official website/repo
- Identify main players/competitors
Round 3 - Deep Investigation (5-10 web_search + web_fetch)
- Technical architecture details
- Timeline of key events
- Community sentiment
- Use web_fetch on valuable URLs for full content
Round 4 - Deep Dive
- Analyze commit history for timeline
- Review issues/PRs for feature evolution
- Check contributor activity
Report Structure
Follow template in assets/report_template.md:
- Metadata Block - Date, confidence level, subject
- Executive Summary - 2-3 sentence overview with key metrics
- Chronological Timeline - Phased breakdown with dates
- Key Analysis Sections - Topic-specific deep dives
- Metrics & Comparisons - Tables, growth charts
- Strengths & Weaknesses - Balanced assessment
- Sources - Categorized references
- Confidence Assessment - Claims by confidence level
- Methodology - Research approach used
Mermaid Diagrams
Include diagrams where helpful:
Timeline (Gantt):
gantt
title Project Timeline
dateFormat YYYY-MM-DD
section Phase 1
Development :2025-01-01, 2025-03-01
section Phase 2
Launch :2025-03-01, 2025-04-01
Architecture (Flowchart):
flowchart TD
A[User] --> B[Coordinator]
B --> C[Planner]
C --> D[Research Team]
D --> E[Reporter]
Comparison (Pie/Bar):
pie title Market Share
"Project A" : 45
"Project B" : 30
"Others" : 25
Confidence Scoring
Assign confidence based on source quality:
| Confidence | Criteria |
|---|---|
| High (90%+) | Official docs, GitHub data, multiple corroborating sources |
| Medium (70-89%) | Single reliable source, recent articles |
| Low (50-69%) | Social media, unverified claims, outdated info |
Output
Save report as: research_{topic}_{YYYYMMDD}.md
Formatting Rules
- Chinese content: Use full-width punctuation(,。:;!?)
- Technical terms: Provide Wiki/doc URL on first mention
- Tables: Use for metrics, comparisons
- Code blocks: For technical examples
- Mermaid: For architecture, timelines, flows
Best Practices
- Start with official sources - Repo, docs, company blog
- Verify dates from commits/PRs - More reliable than articles
- Triangulate claims - 2+ independent sources
- Note conflicting info - Don't hide contradictions
- Distinguish fact vs opinion - Label speculation clearly
- CRITICAL: Always include inline citations - Use
[citation:Title](URL)format immediately after each claim from external sources - Extract URLs from search results - web_search returns {title, url, snippet} - always use the URL field
- Update as you go - Don't wait until end to synthesize
Citation Examples
Good - With inline citations:
The project gained 10,000 stars within 3 months of launch [citation:GitHub Stats](https://github.com/owner/repo).
The architecture uses LangGraph for workflow orchestration [citation:LangGraph Docs](https://langchain.com/langgraph).
Bad - Without citations:
The project gained 10,000 stars within 3 months of launch.
The architecture uses LangGraph for workflow orchestration.
相关科研 Skill
中药材分子鉴定用ITS2等DNA条形码鉴定药材基原物种,处理多基原与降解样品局限。适用于药材真伪鉴别研究,不替代法定检验。
中药网络药理学用TCMSP等数据库构建成分-靶点-通路网络并做富集分析,批判性讨论方法学局限。适用于中药机制假设生成与论文方法复核。
中医术语标准与知识图谱建立中医药术语与WHO/ICD-11标准的映射,设计本体并用Neo4j构建知识图谱。适用于数据整合与科研检索,不作临床决策系统。
方剂配伍规律挖掘对方剂做药名规范化、关联规则与网络聚类分析,发现候选核心药组。适用于用药规律挖掘,结果仅为待验证假设,不作处方依据。
证候与症状数据分析对症状量表数据做术语规范、潜在类别与因子分析,探索统计学证候模式。适用于证候分型研究,结果不用于个体辨证诊断。
泵用混合物热力学计算Calculates thermodynamic properties and mixture phase behavior for pump applications using the thermo Python library’s DIPPR/NIST correlations. Use for VLE or mixture property calculations.
常见问题
GitHub 深度研究助手能做什么?
对任一 GitHub 仓库做多轮深度研究,出含时间线 / 度量 / Mermaid 图的 MD 报告 | 输入:GitHub 仓库 URL | 输出:MD 报告(含时间线 / 度量 / Mermaid 架构图)。
如何安装GitHub 深度研究助手?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「GitHub 深度研究助手」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
GitHub 深度研究助手需要哪些权限?
该科研 Skill声明需要:本地文件、联网。安装前会再次列出,由你确认后才会生效。
GitHub 深度研究助手经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。