devopsby openakita
GitHub Automation via Rube MCP
openakita/skills@github-automation
Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.
What it changes
Passed 8 of 14 test cases with the skill, and 7 of 14 without it.
Without skill50%
With skill54%
Checks it passed that the model alone missed
- uses GITHUB_SEARCH_COMMITS_BY_AUTHOR
- requires search text keywords alongside search qualifiers
- calls RUBE_SEARCH_TOOLS first to discover current tool schemas
and 1 more in the full report
2 fixed11 passed either way10 still failing1 broke
- Pass-rate lift
- +4 pp
- Tokens
- +206%
- Agent turns
- 0%
- Response time
- -24%
Model gemini-3.6-flashMeasured 8/13/2026v113 of 24 cases passed with skill · 14 comparable
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
PromptI need to search for commits authored by `octocat` in `my-org/core` from last week. What parameter requirement applies when searching commits?
What was checked, without and with the skill| Checked | Without skill | With skill |
|---|
| uses GITHUB_SEARCH_COMMITS_BY_AUTHOR | Missed | Passed |
|---|
| requires search text keywords alongside search qualifiers | Missed | Passed |
|---|
What's inside
The instructions your model reads when the skill loads.
SKILL.md220 linessingle file
GitHub Automation via Rube MCP
Automate GitHub repository management, issue tracking, pull request workflows, branch operations, and CI/CD through Composio's GitHub toolkit.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active GitHub connection via
RUBE_MANAGE_CONNECTIONS with toolkit github
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit github
- If connection is not ACTIVE, follow the returned auth link to complete GitHub OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Create and Manage Issues
When to use: User wants to create, list, or manage GitHub issues
Tool sequence:
GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER - Find target repo if unknown [Prerequisite]GITHUB_LIST_REPOSITORY_ISSUES - List existing issues (includes PRs) [Required]GITHUB_CREATE_AN_ISSUE - Create a new issue [Required]GITHUB_CREATE_AN_ISSUE_COMMENT - Add comments to an issue [Optional]GITHUB_SEARCH_ISSUES_AND_PULL_REQUESTS - Search across repos by keyword [Optional]
Key parameters:
owner: Repository owner (username or org), case-insensitiverepo: Repository name without .git extensiontitle: Issue title (required for creation)body: Issue description (supports Markdown)labels: Array of label namesassignees: Array of GitHub usernames
Track record
Benchmark
8 / 14
test cases passed, vs 7 / 14 without
Adoption
- Users
- 0
- Times used
- 0
Safety and source details
SkillSafety
✓ 3 of 3 passed✓Code scan15 of 15 checks clean
0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026
View 15 scanner checks
live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing
✓IntentSafe
LLM judge · does the skill do what it claims
✓ContentClean
LLM judge · policy & harmful-content review
Source
ImportedLicense MITImported 8/3/2026Version v1