github-automation
Automate GitHub Workflows with Rube MCP
GitHub maintenance requires many separate searches, checks, and updates. This skill coordinates repository workflows through Rube MCP with practical safeguards and validation guidance.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "github-automation" from https://skillstore.io/skills/sickn33-github-automation.md and its manifest at https://skillstore.io/api/skills/sickn33-github-automation/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "github-automation". List open issues in acme/widgets and exclude pull requests.
Expected outcome:
Found 12 open issues. Three are unlabeled, two have no assignee, and the oldest has been open for 46 days.
Using "github-automation". Review pull request 42 in acme/widgets.
Expected outcome:
Pull request 42 is mergeable. One CI check is failing, so merging is not recommended.
Using "github-automation". Audit protection for the main branch in acme/widgets.
Expected outcome:
The main branch requires two approvals and passing checks. Administrator enforcement is disabled. No changes were applied.
Security Audit
High RiskAll 116 external-command alerts are false positives caused by Markdown inline code, not shell execution. The Rube endpoint is a real third-party network dependency that delegates GitHub access through OAuth. Workflow dispatch and access-control changes lack explicit confirmation requirements, although merge and deletion are guarded.
Confirmed security concerns (2)
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (50)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-github-automation/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-github-automation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-github-automation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-github-automation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-github-automation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). github-automation security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-github-automation/audits/5BibTeX citation
@techreport{sickn33-sickn33-github-automation-2026,
author = {sickn33},
title = {github-automation security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-github-automation/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "github-automation security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-github-automation/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-github-automation:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Maintain pull request queues
Inspect changed files, mergeability, and CI status before preparing a merge decision.
Organize issue backlogs
Find, create, label, assign, and comment on repository issues with clear repository context.
Review repository operations
Inspect workflows, deployments, collaborators, permissions, and branch protection before proposing controlled changes.
Try These Prompts
List open issues in [owner/repo], separate pull requests, and summarize title, labels, assignee, and age. Do not modify anything.
Prepare an issue in [owner/repo] titled [title] with [body]. Show the proposal and ask before creating it.
Review pull request [number] in [owner/repo], inspect changed files and CI status, then recommend whether it is ready to merge.
Audit [owner/repo] branch protection and collaborator permissions, propose changes, and require approval before every access or protection update.
Best Practices
- Call RUBE_SEARCH_TOOLS before workflows so each action uses the current tool schema.
- Verify the repository, branch, identifiers, permissions, pagination, and current state before acting.
- Require explicit approval before merges, workflow dispatches, repository updates, collaborator changes, or branch protection changes.
Avoid
- Do not merge, delete, or alter access controls from an ambiguous request.
- Do not treat one result page as a complete repository inventory.
- Do not share OAuth links, repository content, or credentials with unrelated services.