Agent skill

GitHub Automation

by sickn33 in sickn33/agentic-awesome-skills

Operate GitHub issues, pull requests, branches, checks, workflows, and permissions through Rube MCP.

MITAuto-check passedDevelopment

Install GitHub Automation

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill github-automation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills github-automation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/github-automation .claude/skills/github-automation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
github-automation
GitHub stars
47k
Used in
1 other repo
Token cost
~1.3k tokens
SKILL.md length
700 words
Files
1
Skills in repo
1,394
Repo updated
First seen
Licence
MIT

At a glance

Operate GitHub issues, pull requests, branches, checks, workflows, and permissions through Rube MCP.

  • Works in 4 steps: Confirm RUBE_SEARCH_TOOLS is available. → Search for the current GitHub tool… → Use RUBE_MANAGE_CONNECTIONS with toolkit… → …
  • GitHub work must be queried
  • SKILL.md covers When to Use, Setup, Repository Policy Gate and Workflows, plus 3 more sections
  • Calls npm

What it does

GitHub Automation is an agent skill from sickn33/agentic-awesome-skills. Operate GitHub issues, pull requests, branches, checks, workflows, and permissions through Rube MCP. Use when GitHub work must be queried or changed programmatically with repository-policy safeguards.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering App automation through connectors and Pull requests. It works with GitHub. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • GitHub work must be queried
  • Changed programmatically with repository-policy safeguards

Example prompts

  • “/github-automation”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Confirm RUBE_SEARCH_TOOLS is available.
  2. Search for the current GitHub tool schemas before composing calls.
  3. Use RUBE_MANAGE_CONNECTIONS with toolkit github and complete OAuth only if the connection is not active.
  4. Resolve the exact owner/repo; do not rely on a similarly named repository.

What it can do on your machine

Read from SKILL.md and the folder at commit 1e53ce2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitHub Automation loads about 1.3k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 700 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit 1e53ce2, republished under its MIT licence (© sickn33). 700 words, ~1,338 tokens.

Download SKILL.mdSave it as .claude/skills/github-automation/SKILL.md (or your agent's skills folder).
name
github-automation
description
Operate GitHub issues, pull requests, branches, checks, workflows, and permissions through Rube MCP. Use when GitHub work must be queried or changed programmatically with repository-policy safeguards.
risk
critical
source
community
date_added
2026-02-27

GitHub Automation via Rube MCP

Use Composio's GitHub toolkit through Rube MCP while preserving repository policy, exact revision identity, and branch protection.

When to Use

Use for programmatic GitHub issue, pull-request, branch, Actions, deployment, collaborator, or protection tasks when Rube MCP is available. Prefer the native gh workflow or a repository-specific maintainer command when local repository policy requires it.

Setup

  1. Confirm RUBE_SEARCH_TOOLS is available.
  2. Search for the current GitHub tool schemas before composing calls.
  3. Use RUBE_MANAGE_CONNECTIONS with toolkit github and complete OAuth only if the connection is not active.
  4. Resolve the exact owner/repo; do not rely on a similarly named repository.

Never request, print, or persist GitHub credentials in prompts or artifacts.

Repository Policy Gate

Before mutation, read AGENTS.md, contribution and maintainer docs, then inspect the default branch and effective protection. Repository-native commands and required checks take precedence over generic Rube operations.

If a repository provides a guarded merge or release command, use it instead of the generic merge tool. In agentic-awesome-skills, use antigravity-maintainer-batch-release and npm run merge:batch so exact-SHA review, fresh check-suite binding, and protected main are enforced.

Workflows

Issues
  1. List or search existing issues before creating a duplicate.
  2. Distinguish issues from pull requests in mixed results.
  3. Read the current item, comments, labels, and linked PRs before changing state.
  4. Create, comment, label, assign, or close only within the user's requested scope.
  5. Re-read the item and verify the resulting state.

Paginate until the requested result set is complete. Treat silent omission of labels or assignees as a permissions failure, not success.

Pull requests
  1. Resolve the PR and capture its number, base, full head SHA, draft state, author, fork identity, and mergeability.
  2. Inspect changed files, reviews, conversations, and required check runs.
  3. Bind every review or approval decision to the current full head SHA.
  4. Create or update the PR body truthfully; never mark pending tests or reviews as completed.
  5. Immediately before merge, re-read base/head identity, branch protection, mergeability, required checks, and repository policy.
  6. Use the repository's guarded merge path. Call a generic merge tool only when policy permits it and the user authorized the merge.
  7. Verify the PR reports MERGED and confirm the target branch contains the intended commit.

Do not treat a successful API call that enables auto-merge or queues work as an immediate merge.

Show full SKILL.md (310 more words)Show less
Branches and references
  1. Resolve the source commit SHA and target ref explicitly.
  2. Create topic branches rather than updating protected/default branches directly.
  3. Reject non-fast-forward or force updates unless the user explicitly authorizes them and repository policy permits them.
  4. Confirm the remote ref after mutation.

Deletion, force-push, default-branch changes, and protection changes are destructive or high-impact actions requiring explicit authorization.

Actions and deployments
  1. Resolve the workflow by trusted ID or path and confirm workflow_dispatch support before dispatch.
  2. Bind run inspection to the intended event, ref, and head SHA.
  3. Distinguish queued, in_progress, action_required, completed, and skipped states.
  4. Read failed job logs before proposing source changes.
  5. Wait for terminal success and verify the deployed or published surface separately.

Do not approve fork workflow runs by raw run ID when the repository provides a guarded approval command.

Permissions and protection
  1. Read collaborators, role, branch protection, and applicable rulesets before proposing changes.
  2. Treat a 404 protection response as “not configured” only after confirming repository and branch identity.
  3. Show the exact before/after policy and impact before any protection or permission mutation.
  4. Re-read effective state after the change.

Failure Rules

  • Re-resolve tool schemas when Rube reports missing or changed parameters.
  • Stop on repository ambiguity, stale head/base SHA, missing permissions, incomplete pagination, or inconclusive protection state.
  • Never bypass required checks, reviews, merge queues, maintainer commands, or server-side branch protection.
  • Do not claim a merge, workflow, deployment, or permission change succeeded without reading the resulting remote state.

Example

User request:

Operate GitHub issues, pull requests, branches, checks, workflows, and permissions through Rube MCP.

Limitations

  • Available Rube tool names and schemas can change; discover them at runtime.
  • GitHub permissions, organization policy, and external checks can block otherwise valid operations.
  • This skill does not authorize repository deletion, force pushes, protection changes, merges, deployments, or releases beyond explicit user intent.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/github-automation of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit 1e53ce2

Used in 1 other repository

We found 7 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

GitHub Automation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GitHub Automation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub Automation this skillsickn33/agentic-awesome-skills47k1 repos~1.3kAutomated safety check: PassMIT
GitHub Automationdavila7/claude-code-templates32k5 repos~2.8kAutomated safety check: PassMIT
Review PRwarpdotdev-demos/cloud-factory-demo320—~1.5kAutomated safety check: PassMIT
Project Pull Requestswimmwatch/cloakbrowser-mcp161—~1kAutomated safety check: PassMIT
PR Monitorespennilsen/pi122—~935Automated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0

Similar skills

  • GitHub Automation

    davila7/claude-code-templates

    Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio).

    32k GitHub starsUsed in 5 repos~2.8k tokens
    Productivity & AutomationAuto-check passed
  • Review PR

    warpdotdev-demos/cloud-factory-demo

    Review a PR from local annotated-diff artifacts and write validated review.json for the workflow to publish.

    320 GitHub stars~1.5k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Project Pull Request

    swimmwatch/cloakbrowser-mcp

    Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work.

    161 GitHub stars~1k tokensUpdated 5 days ago
    DevelopmentAuto-check passed
  • PR Monitor

    espennilsen/pi

    Monitor open GitHub PRs across all repos in ~/Dev. An agent skill from espennilsen/pi.

    122 GitHub stars~935 tokensUpdated 15 days ago
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,394 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Questions about GitHub Automation

What does GitHub Automation do?

Operate GitHub issues, pull requests, branches, checks, workflows, and permissions through Rube MCP. GitHub Automation is an agent skill from sickn33/agentic-awesome-skills. Operate GitHub issues, pull requests, branches, checks, workflows, and permissions through Rube MCP.

When should I use GitHub Automation?

GitHub Automation fits situations like: GitHub work must be queried; changed programmatically with repository-policy safeguards.

How do I install GitHub Automation in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill github-automation -a claude-code`. Or copy the skill folder (skills/github-automation in sickn33/agentic-awesome-skills) into .claude/skills/github-automation in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Automation in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill github-automation -a codex`. Or copy the skill folder (skills/github-automation in sickn33/agentic-awesome-skills) into .agents/skills/github-automation in your project. Codex loads it when a task matches its description.

Can I use GitHub Automation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill github-automation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-automation, .gemini/skills/github-automation, .github/skills/github-automation and .opencode/skills/github-automation in your project.

What does GitHub Automation need to run?

Going by SKILL.md and its folder, GitHub Automation needs the command-line tools its instructions call (npm).

Does GitHub Automation access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is GitHub Automation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does GitHub Automation use?

GitHub Automation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub Automation use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to GitHub Automation?

Skills that share tags, products or a category with GitHub Automation: GitHub Automation (davila7/claude-code-templates, 32k stars), Review PR (warpdotdev-demos/cloud-factory-demo, 320 stars), Project Pull Request (swimmwatch/cloakbrowser-mcp, 161 stars) and PR Monitor (espennilsen/pi, 122 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Automation?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.