GitHub Integration Skill#

Query and manage GitHub repositories directly from your AI assistant.

Capabilities#

CapabilityDescriptionlist_reposList your repositories with filtersget_repoGet detailed info about a specific repocheck_ci_statusCheck CI/CD pipeline statuscreate_issueCreate a new issue in a repocreate_repoCreate a new repositorysearch_reposSearch your repositoriesget_recent_activityGet recent commits

Usage#

text

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#

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

2. Configure Credentials#

Option A: Environment Variables (Recommended)

Set environment variables before starting OpenClaw:

bash

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

Option B: OpenClaw Config

Add to ~/.openclaw/openclaw.json:

json

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

3. Restart OpenClaw#

bash

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