oo-github

name	oo-github
description	GitHub (github.com). Use this skill for ANY GitHub request — reading, creating, updating, and deleting data. Whenever a task involves GitHub, use this skill instead of calling the API directly.
allowed-tools	["Bash(oo *)"]
metadata	{"title":"GitHub","author":"OOMOL","version":"1.0.5","services":["github"],"icon":"https://static.oomol.com/logo/third-party/github.png"}

GitHub

Operate GitHub through your OOMOL-connected account. This skill calls the github connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected GitHub. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "github" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "github" --action "<action_name>" --data '<json>' --json

• --data takes a JSON object string or @path/to/file.json; omit it to send {}.
• The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

• add_issue_assignees — Add assignees to a GitHub issue. [write]
• add_issue_labels — Add labels to a GitHub issue. [write]
• add_repository_collaborator — Add a collaborator to a GitHub repository or update their permission. [write]
• cancel_workflow_run — Cancel a GitHub Actions workflow run. [write]
• check_pull_request_merged — Check whether a GitHub pull request has been merged.
• check_repository_starred — Check whether the authenticated user has starred a GitHub repository.
• clear_issue_labels — Remove all labels from a GitHub issue. [destructive]
• compare_commits — Compare two commit references in a GitHub repository.
• create_commit_comment — Create a comment on a commit in a GitHub repository. [write]
• create_commit_status — Create a commit status for a GitHub commit SHA. [write]
• create_issue — Create an issue in a GitHub repository. [write]
• create_issue_comment — Create a comment on a GitHub issue. [write]
• create_issue_comment_reaction — Add a reaction to a GitHub issue comment. [write]
• create_issue_reaction — Add a reaction to a GitHub issue. [write]
• create_label — Create a label in a GitHub repository. [write]
• create_milestone — Create a milestone in a GitHub repository. [write]
• create_or_update_file — Create or update a repository file through the GitHub contents API. Writing under .github/workflows may require GitHub workflow scope. [write]
• create_pull_request — Create a pull request in a GitHub repository. [write]
• create_pull_request_review — Create a review for a GitHub pull request, optionally with inline comments. [write]
• create_pull_request_review_comment — Create a review comment on a GitHub pull request diff. [write]
• create_ref — Create a Git reference in a GitHub repository. [write]
• create_release — Create a release in a GitHub repository. [write]
• create_repository — Create a repository for the authenticated GitHub user. [write]
• delete_file — Delete a repository file through the GitHub contents API. Deleting under .github/workflows may require GitHub workflow scope. [destructive]

Safety

• Untagged actions are reads (get / list / search) — safe to run directly.
• Actions tagged [write] change GitHub state — confirm the exact payload and effect with the user before running.
• Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

• oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  

  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  

• Not signed in / authentication error — sign in to your OOMOL account once:

  oo auth login
  

• scope_missing / credential_expired / app_not_ready / app_not_found — GitHub is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:

  https://console.oomol.com/app-connections?provider=github
  

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

• GitHub homepage: https://github.com