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.
89
Quality
91%
Does it follow best practices?
Impact
81%
1.32xAverage score across 3 eval scenarios
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent specificity and trigger term coverage for GitHub-related tasks. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others. The description correctly uses third person voice throughout.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about GitHub automation, managing repositories, creating/reviewing pull requests, or setting up CI/CD pipelines.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions', 'Manage code workflows, review PRs, search code, and handle deployments programmatically'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific GitHub automation capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied through the capabilities listed. | 2 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'GitHub', 'repositories', 'issues', 'pull requests', 'PRs', 'branches', 'CI/CD', 'deployments', 'code'. Good coverage of terms developers naturally use when working with GitHub. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly distinguishable with specific GitHub focus and mentions 'Rube MCP (Composio)' as the implementation. The combination of GitHub-specific terms and the tooling reference creates a distinct niche unlikely to conflict with generic code or document skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill document that efficiently covers GitHub automation via Rube MCP. It provides comprehensive, actionable guidance with clear tool sequences, explicit validation steps, and well-documented pitfalls. The structure balances breadth of coverage with concise, scannable formatting including the helpful Quick Reference table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, avoiding explanations of concepts Claude already knows. Every section provides actionable information without padding or unnecessary context about what GitHub is or how APIs work. | 3 / 3 |
Actionability | Provides concrete tool names, specific parameter lists, and exact sequences for each workflow. The Quick Reference table and detailed parameter specifications make this immediately actionable without ambiguity. | 3 / 3 |
Workflow Clarity | Each workflow has clear numbered sequences with explicit validation checkpoints (e.g., 'verify mergeable status before merge', 'confirm connection status shows ACTIVE'). Safety section explicitly requires user confirmation for destructive operations and CI checks before merging. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from setup to core workflows to common patterns. External reference to Composio docs is one level deep and clearly signaled. Content is appropriately structured without being monolithic. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.