Openclaw Github Assistant 2.0.1

核心功能含列出仓库、查看详情、检查CI/CD状态、创建issue与仓库、搜索仓库、查看最近提交等。典型场景如查询个人Python仓库、检查主项目CI状态、提交bug工单等，通过自然语言指令触发，返回对应操作结果。需配置GitHub令牌和用户名，支持环境变量或配置文件设置，注意令牌安全与API速率限制。

gyzx

热度 69.61

最近更新 2026-05-11 17:32:05

分类：自动化依赖：第三方 API应用场景：DevOps / 任务管理

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add openclaw-github-assistant-2-0-1

Metadata

name: github
description: Query and manage GitHub repositories - list repos, check CI status, create issues, search repos, and view recent activity.
metadata: {"openclaw":{"emoji":"🐙","requires":{"env":["GITHUB_TOKEN","GITHUB_USERNAME"],"config":["github.token","github.username"]}}}

GitHub Integration Skill

Query and manage GitHub repositories directly from your AI assistant.

Capabilities

Capability	Description
`list_repos`	List your repositories with filters
`get_repo`	Get detailed info about a specific repo
`check_ci_status`	Check CI/CD pipeline status
`create_issue`	Create a new issue in a repo
`create_repo`	Create a new repository
`search_repos`	Search your repositories
`get_recent_activity`	Get recent commits

Usage

You: List my Python repos
Bot: [lists your Python repositories]

You: Check CI status on my main project
Bot: [shows CI/CD status]

You: Create an issue about the bug
Bot: [creates the issue]

Setup

1. Generate GitHub Personal Access Token

Go to https://github.com/settings/tokens
Click "Generate new token (classic)"
Name: openclaw-github-skill
Scopes: repo (required), read:user (optional)
Copy the token

2. Configure Credentials

Option A: Environment Variables (Recommended)

Set environment variables before starting OpenClaw:

export GITHUB_TOKEN="ghp_your_token_here"
export GITHUB_USERNAME="your_github_username"

Option B: OpenClaw Config

Add to ~/.openclaw/openclaw.json:

{
  "github": {
    "token": "ghp_your_token_here",
    "username": "your_username"
  }
}

3. Restart OpenClaw

openclaw gateway restart

Security Notes

⚠️ Protect Your Token:

Never commit your token to git or share it publicly
Use the minimal required scopes (repo for private repos, public_repo for public-only)
Rotate your token if you suspect it was compromised
Consider using a secrets manager for production use

⚠️ Best Practices:

Don't store tokens in shell profiles (~/.zshrc) on shared machines
For local development, environment variables are acceptable
For production, use your platform's secret/credential store

Rate Limits

Unauthenticated requests: 60/hour
Authenticated requests: 5,000/hour

Requirements

OpenClaw gateway running
GitHub Personal Access Token with appropriate scopes