據 AlphaMoat 統計,截至 2026-10,GitHub 累計下載 7,602 次、獲 34 個星標,按累計下載量在本次參與排名的 10,914 個 AI 技能中排名第 3,685 位,在「開發程式設計」分類(1,069 個)中排名第 299 位。
列表預設按累計下載量排序,也可按星標排序;詳情頁排名按累計下載量計算。
| 平台 | 累計下載 | 星標 | 評論 |
|---|---|---|---|
| ClawHub ↗ | 7602 | 32 | - |
| SkillHub ↗ | 5793 | 34 | — |
各平台的計數口徑不同,統計時間不一致。
透過 GitHub REST 和GraphQL API 與倉庫、議題、拉取請求、提交、分支、釋出和工作流進行互動。在需要時使用此技能。
2026-09 起統計方法調整:同名技能按作者分別統計,並覆蓋全部技能。圖中虛線為調整前的月份,與之後的資料不直接比較,也不計算跨越調整的增長。 該技能有同名的其他版本,調整前的資料歸屬當前下載量最大的這一個。
| 月份 | 累計下載 | 環比 | 星標 |
|---|---|---|---|
| 2026-10 | 7602 | — | 34 |
| 2026-09 | 7369 | — | 34 |
| 2026-08 | 7190 | +1.2% | 34 |
| 2026-07 | 7104 | +250.1% | 34 |
| 2026-06 | 2029 | +55.1% | 32 |
| 2026-05 | 1308 | — | 6 |
以下是作者釋出的原始檔案,按純文字顯示,本站未做修改或稽核;其中的連結不可點選,命令請核實後再執行。抓取於 2026-11-20。
--- name: github-repos description: Work with GitHub repositories, issues, pull requests, commits, branches, releases, and workflows via the GitHub REST and GraphQL APIs. Use this skill when users want to list repositories, inspect issues and PRs, manage branches and commits, create or update issues after confirmation, or trigger and inspect GitHub Actions workflows. --- # GitHub  Access GitHub via the GitHub API with OAuth authentication. Manage repositories, issues, pull requests, commits, branches, releases, and workflows.
This skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=github-repos) for hosted connection flows and credentials so you do not need to configure GitHub API access yourself.
### Setup in 3 Steps
| Step 1: Install | Step 2: Pair Account | Step 3: Connect GitHub |
|:---:|:---:|:---:|
|  |  | *App-specific connection GIF coming soon* |
| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect GitHub |
## How It Works
```
┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐
│ OpenClaw │────▶│ ClawLink │────▶│ GitHub API │
│ (User Chat) │ │ (OAuth) │ │ (REST/GraphQL) │
└─────────────────┘ └──────────────┘ └──────────────────┘
│ │ │
│ 1. Install Plugin │ │
│ 2. Pair Device │ │
│ 3. Connect GitHub │ │
│ │ 4. Secure Token │
│ │ 5. Proxy Requests │
│ │ │
▼ ▼ ▼
┌──────────┐ ┌──────────┐ ┌──────────┐
│ SKILL │ │ Dashboard│ │ GitHub │
│ File │ │ Auth │ │ Repos │
└──────────┘ └──────────┘ └──────────┘
```
## Install
Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.
```bash
openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart
```
Then tell the user: "OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for GitHub again."
## Quick Start
```bash
# List repositories for the authenticated user
clawlink_call_tool --tool "github_list_repositories_for_the_authenticated_user" --params '{}'
# Get a specific repository
clawlink_call_tool --tool "github_get_a_repository" --params '{"owner": "owner", "repo": "repo-name"}'
# List issues in a repository
clawlink_call_tool --tool "github_list_issues_for_a_repository" --params '{"owner": "owner", "repo": "repo-name", "state": "open"}'
```
## Authentication
All GitHub tool calls are authenticated automatically by ClawLink using the user's connected GitHub account.
**No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every GitHub API request on the user's behalf.
### Getting Connected
1. Install the ClawLink plugin (see Install above).
2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.
3. Open https://claw-link.dev/dashboard?add=github and connect GitHub.
4. Call `clawlink_list_integrations` to verify the connection is active.
## Connection Management
### List Connections
```bash
clawlink_list_integrations
```
**Response:** Returns all connected integrations. Look for `github` in the list.
### Verify Connection
```bash
clawlink_list_tools --integration github
```
**Response:** Returns the live tool catalog for GitHub.
### Reconnect
If GitHub tools are missing or the connection shows an error:
1. Direct the user to https://claw-link.dev/dashboard?add=github
2. After they confirm, call `clawlink_list_integrations` to verify
3. Then call `clawlink_list_tools --integration github`
## Security & Permissions
- Access is scoped to repositories and resources accessible to the connected GitHub account.
- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.
- Destructive actions (deleting issues, closing PRs, removing collaborators) are marked as high-impact and must be confirmed.
- Workflow triggers and deployments affect external systems — always confirm before executing.
## Tool Reference
### Repositories
| Tool | Description | Mode |
|------|-------------|------|
| `github_list_repositories_for_the_authenticated_user` | List all repos for the authenticated user | Read |
| `github_get_a_repository` | Get repository details | Read |
| `github_create_a_repository` | Create a new repository | Write |
| `github_update_a_repository` | Update repository settings | Write |
| `github_delete_a_repository` | Delete a repository | Write |
| `github_list_repository_collaborators` | List repo collaborators | Read |
### Issues
| Tool | Description | Mode |
|------|-------------|------|
| `github_list_issues_for_a_repository` | List issues with filtering | Read |
| `github_get_an_issue` | Get issue details | Read |
| `github_create_an_issue` | Create a new issue | Write |
| `github_update_an_issue` | Update issue fields (labels, assignee, state) | Write |
| `github_add_labels_to_an_issue` | Add labels to an issue | Write |
| `github_add_assignees_to_an_issue` | Add assignees to an issue | Write |
### Pull Requests
| Tool | Description | Mode |
|------|-------------|------|
| `github_list_pull_requests` | List PRs in a repository | Read |
| `github_get_a_pull_request` | Get PR details | Read |
| `github_create_a_pull_request` | Create a new PR | Write |
| `github_update_a_pull_request` | Update PR fields | Write |
### Commits & Branches
| Tool | Description | Mode |
|------|-------------|------|
| `github_list_commits` | List commits in a repository | Read |
| `github_get_a_commit` | Get commit details | Read |
| `github_list_branches` | List branches in a repository | Read |
| `github_create_a_branch` | Create a new branch | Write |
### Workflows
| Tool | Description | Mode |
|------|-------------|------|
| `github_list_repository_workflows` | List workflows in a repo | Read |
| `github_list_workflow_runs` | List workflow runs | Read |
| `github_get_a_workflow_run` | Get workflow run details | Read |
| `github_cancel_workflow_run` | Cancel an in-progress workflow run | Write |
### Releases
| Tool | Description | Mode |
|------|-------------|------|
| `github_list_releases` | List releases in a repository | Read |
| `github_get_a_release` | Get release details | Read |
| `github_create_a_release` | Create a new release | Write |
## Code Examples
### List open issues in a repository
```bash
clawlink_call_tool --tool "github_list_issues_for_a_repository" \
--params '{
"owner": "owner",
"repo": "repo-name",
"state": "open",
"sort": "created",
"direction": "desc"
}'
```
### Create a new issue
```bash
clawlink_call_tool --tool "github_create_an_issue" \
--params '{
"owner": "owner",
"repo": "repo-name",
"title": "Bug: Login fails on mobile",
"body": "Steps to reproduce: 1. Go to login 2. Enter credentials 3. Error shown",
"labels": ["bug", "high-priority"]
}'
```
### Add labels to an issue
```bash
clawlink_call_tool --tool "github_add_labels_to_an_issue" \
--params '{
"owner": "owner",
"repo": "repo-name",
"issue_number": 123,
"labels": ["needs-review", "bug"]
}'
```
### Create a pull request
```bash
clawlink_call_tool --tool "github_create_a_pull_request" \
--params '{
"owner": "owner",
"repo": "repo-name",
"title": "Fix login bug",
"head": "fix/login-bug",
"base": "main",
"body": "Fixes #123 - Login fails on mobile devices"
}'
```
## Discovery Workflow
1. Call `clawlink_list_integrations` to confirm GitHub is connected.
2. Call `clawlink_list_tools --integration github` to see the live catalog.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `github`.
5. If no GitHub tools appear, direct the user to https://claw-link.dev/dashboard?add=github.
## Execution Workflow
```
┌─────────────────────────────────────────────────────────────┐
│ READ OPERATIONS (Safe) │
│ list → get → search → describe → call │
│ │
│ Example: List issues → Get issue → Show details │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ WRITE OPERATIONS (Require Confirmation) │
│ list → get → describe → preview → confirm → call │
│ │
│ Example: Describe tool → Preview issue → User approves │
│ → Execute create │
└─────────────────────────────────────────────────────────────┘
```
1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.
2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.
3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.
4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.
5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.
6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.
## Notes
- GitHub API rate limits apply. The number of calls depends on the connected account type (free, pro, or enterprise).
- Some tools require specific OAuth scopes. If a tool fails with insufficient scope, verify the connection has the right permissions.
- Repository names must use `owner/repo` format for owner and repo parameters.
- Issues and PRs use different numbering systems within the same repository.
## Error Handling
| Status / Error | Meaning |
|----------------|---------|
| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration github`. |
| Missing connection | GitHub is not connected. Direct the user to https://claw-link.dev/dashboard?add=github. |
| `404 Not Found` | Repository, issue, or PR does not exist. Verify owner, repo, and number. |
| `403 Forbidden` | Rate limit exceeded or insufficient permissions. |
| `422 Unprocessable` | Invalid request body or missing required fields. Verify tool schema. |
| Write rejected | User did not confirm a write action. Always confirm before executing writes. |
### Troubleshooting: Tools Not Visible
1. Check that the ClawLink plugin is installed:
```bash
openclaw plugins list
```
2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.
3. If a fresh chat does not help, run:
```bash
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart
```
4. After restart, tell the user to send `/new` again and retry.
### Troubleshooting: Invalid Tool Call
1. Ensure the integration slug is exactly `github`.
2. Use `clawlink_describe_tool` to verify parameter names and types before calling.
3. For write operations, always call `clawlink_preview_tool` first.
## Resources
- [GitHub REST API Documentation](https://docs.github.com/en/rest)
- [GitHub GraphQL API](https://docs.github.com/en/graphql)
- [GitHub Actions Documentation](https://docs.github.com/en/actions)
- [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=github-repos)
- [ClawLink Docs](https://docs.claw-link.dev/openclaw)
- [ClawLink Verification](https://claw-link.dev/verify)
## Related Skills
- [GitLab Repos](https://clawhub.ai/hith3sh/gitlab-repos) — For GitLab project management
- [GitHub Triage](https://clawhub.ai/hith3sh/github-triage-workflow) — For GitHub issue triage workflows
---
**Powered by [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=github-repos)** — an integration hub for OpenClaw
【全棧能力】程式設計大神.Skill:面向複雜真實專案的高階全棧程式設計助手。不止生成程式碼,而是從一句目標接手陌生程式碼庫,拆解需求、補齊實現、追到根因、完成重構、聯調前後端,並把結果推進到能執行、能驗證、能交付。覆蓋 Web、後端、指令碼、iOS、安卓、鴻蒙 ArkUI、微信小程式及其他技術棧,支援中英文工程、疑難 Bug、跨模組任務和長任務續做;用構建、日誌、真實入口、裝置或介面證據說明結果。僅問概念時直接回答,要求落地時持續推進到驗收或明確阻塞。
程式設計專家 Pro:融合程式設計專家 2.0.3 工程專題與程式設計大神的鴻蒙 ArkTS/ArkUI、微信小程式和小遊戲開發資料。用於專案實現、根因除錯、審查、重構、測試、架構效能分析及多端開發驗證。支援自然語言和 @專題標識,按任務讀取包內知識;只問概念時直接回答。
程式設計專家.Skill P8級程式設計助手,25年實戰經驗技能Skill,全棧:Java/Php網站/軟體專案、API設計、Bug診斷、程式碼生成、程式碼審查、重構、測試用例、效能基準、技術選型、文件生成、任務拆解、Spec驅動、Karpathy規範、CMS二次開發、前端設計、MySQL/Mariadb、專案知識圖譜,以及工程紀律層(根因除錯硬閉環、階段導航、事故復盤/SLO、威脅建模/供應鏈安全、生產就緒/漸進式釋出、AI編碼治理、面向Agent程式碼可讀性、LLM應用安全)。支援 @標識 顯式呼叫跳過路由。
程式設計專家.Skill P8級程式設計助手,25年實戰經驗技能Skill,全棧:Java/Php網站/軟體專案、API設計、Bug診斷、程式碼生成、程式碼審查、重構、測試用例、效能基準、技術選型、文件生成、任務拆解、Spec驅動、Karpathy規範、CMS二次開發、前端設計、MySQL/Mariadb、專案知識圖譜,以及工程紀律層(根因除錯硬閉環、階段導航、事故復盤/SLO、威脅建模/供應鏈安全、生產就緒/漸進式釋出、AI編碼治理、面向Agent程式碼可讀性、LLM應用安全)。支援 @標識 顯式呼叫跳過路由。
程式設計專家 Pro:融合程式設計專家 2.0.3 工程專題與程式設計大神的鴻蒙 ArkTS/ArkUI、微信小程式和小遊戲開發資料。用於專案實現、根因除錯、審查、重構、測試、架構效能分析及多端開發驗證。支援自然語言和 @專題標識,按任務讀取包內知識;只問概念時直接回答。
程式設計專家 Pro:融合程式設計專家 2.0.3 工程專題與程式設計大神的鴻蒙 ArkTS/ArkUI、微信小程式和小遊戲開發資料。用於專案實現、根因除錯、審查、重構、測試、架構效能分析及多端開發驗證。支援自然語言和 @專題標識,按任務讀取包內知識;只問概念時直接回答。
程式設計專家.Skill P8級程式設計助手,25年實戰經驗技能Skill,全棧:Java/Php網站/軟體專案、API設計、Bug診斷、程式碼生成、程式碼審查、重構、測試用例、效能基準、技術選型、文件生成、任務拆解、Spec驅動、Karpathy規範、CMS二次開發、前端設計、MySQL/Mariadb、專案知識圖譜,以及工程紀律層(根因除錯硬閉環、階段導航、事故復盤/SLO、威脅建模/供應鏈安全、生產就緒/漸進式釋出、AI編碼治理、面向Agent程式碼可讀性、LLM應用安全)。支援 @標識 顯式呼叫跳過路由。
用 gh 命令列工具檢視 GitHub 上的 PR 檢查、工作流執行與 API 查詢的技能。
透過 Instagram Graph API 管理 Instagram 商業號和創作者賬號。釋出帖子和輪播,獲取媒體和洞察資料,稽核評論,傳送...
Facebook Pages 是一項透過 ClawLink 管理 OAuth 連線、訪問 Facebook Page 工具的技能說明。
透過託管 OAuth 整合 Google Sheets API,建立電子表格、讀寫單元格值、管理工作表、追加行、生成圖表並實現資料自動化。
整合 Google Drive API,採用託管式 OAuth,支援搜尋檔案、管理許可權、整理資料夾、上傳下載檔案以及處理共享變更等。
透過LinkedIn API管理LinkedIn形象,建立帖子和文章,管理評論,處理媒體上傳,搜尋廣告定向實體,並檢索...
資料月份:2026-10 · 下載/星標數聚合自公開技能註冊庫(ClawHub、SkillHub),按月更新。口徑說明見資料方法。