GitHub#

Access GitHub via the GitHub API with OAuth authentication. Manage repositories, issues, pull requests, commits, branches, releases, and workflows.

This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure GitHub API access yourself.

Setup in 3 Steps#

Step 1: InstallStep 2: Pair AccountStep 3: Connect GitHub_App-specific connection GIF coming soon_Run the install command in OpenClawSign in and approve the deviceOpen the dashboard and connect GitHub

How It Works#

text

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   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#

ToolDescriptionModegithub_list_repositories_for_the_authenticated_userList all repos for the authenticated userReadgithub_get_a_repositoryGet repository detailsReadgithub_create_a_repositoryCreate a new repositoryWritegithub_update_a_repositoryUpdate repository settingsWritegithub_delete_a_repositoryDelete a repositoryWritegithub_list_repository_collaboratorsList repo collaboratorsRead

Issues#

ToolDescriptionModegithub_list_issues_for_a_repositoryList issues with filteringReadgithub_get_an_issueGet issue detailsReadgithub_create_an_issueCreate a new issueWritegithub_update_an_issueUpdate issue fields (labels, assignee, state)Writegithub_add_labels_to_an_issueAdd labels to an issueWritegithub_add_assignees_to_an_issueAdd assignees to an issueWrite

Pull Requests#

ToolDescriptionModegithub_list_pull_requestsList PRs in a repositoryReadgithub_get_a_pull_requestGet PR detailsReadgithub_create_a_pull_requestCreate a new PRWritegithub_update_a_pull_requestUpdate PR fieldsWrite

Commits & Branches#

ToolDescriptionModegithub_list_commitsList commits in a repositoryReadgithub_get_a_commitGet commit detailsReadgithub_list_branchesList branches in a repositoryReadgithub_create_a_branchCreate a new branchWrite

Workflows#

ToolDescriptionModegithub_list_repository_workflowsList workflows in a repoReadgithub_list_workflow_runsList workflow runsReadgithub_get_a_workflow_runGet workflow run detailsReadgithub_cancel_workflow_runCancel an in-progress workflow runWrite

Releases#

ToolDescriptionModegithub_list_releasesList releases in a repositoryReadgithub_get_a_releaseGet release detailsReadgithub_create_a_releaseCreate a new releaseWrite

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#

text

┌─────────────────────────────────────────────────────────────┐
│  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 / ErrorMeaningTool not foundThe tool name does not exist in the current catalog. Verify with clawlink_list_tools --integration github.Missing connectionGitHub is not connected. Direct the user to https://claw-link.dev/dashboard?add=github.404 Not FoundRepository, issue, or PR does not exist. Verify owner, repo, and number.403 ForbiddenRate limit exceeded or insufficient permissions.422 UnprocessableInvalid request body or missing required fields. Verify tool schema.Write rejectedUser 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
• GitHub GraphQL API
• GitHub Actions Documentation
• ClawLink
• ClawLink Docs
• ClawLink Verification

Related Skills#

• GitLab Repos — For GitLab project management
• GitHub Triage — For GitHub issue triage workflows

---

Powered by ClawLink — an integration hub for OpenClaw