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.
75
68%
Does it follow best practices?
Impact
81%
1.32xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/github-automation/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is strong on specificity and trigger terms, listing many concrete GitHub-related actions and natural keywords. Its main weakness is the absence of an explicit 'Use when...' clause, which limits completeness and makes it harder for Claude to know precisely when to select this skill over other GitHub-related tools. The mention of 'Rube MCP (Composio)' adds some distinctiveness but could be clearer about when this skill should be preferred.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to automate GitHub tasks, manage repos, create or review pull requests, or handle CI/CD pipelines via Composio.'
Clarify what distinguishes this from other GitHub-related skills (e.g., native git CLI or GitHub API skills) by specifying that this operates through the Rube MCP / Composio integration.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: managing repositories, issues, pull requests, branches, CI/CD, permissions, reviewing PRs, searching code, and handling deployments. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the listed capabilities. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'GitHub', 'repositories', 'issues', 'pull requests', 'PRs', 'branches', 'CI/CD', 'deployments', 'permissions', 'code', 'search code'. Good coverage of terms a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Mentions 'GitHub' and 'Rube MCP (Composio)' which helps distinguish it, but terms like 'code workflows', 'deployments', and 'CI/CD' could overlap with other DevOps or code management skills. The Composio/Rube MCP mention helps but could still conflict with a native GitHub CLI skill. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive GitHub automation skill with excellent workflow clarity, clear safety guardrails, and well-organized sections. Its main weaknesses are the lack of concrete executable examples (actual tool call invocations with sample data) and the monolithic structure that could benefit from splitting detailed reference material into separate files. The repetition between per-section pitfalls and the consolidated pitfalls section adds unnecessary tokens.
Suggestions
Add at least one concrete, complete tool invocation example per workflow (e.g., show an actual GITHUB_CREATE_AN_ISSUE call with realistic parameter values) to improve actionability.
Remove the consolidated 'Known Pitfalls' section since all pitfalls are already documented in their respective workflow sections, or vice versa, to reduce redundancy.
Consider splitting the detailed workflow sections into separate reference files (e.g., ISSUES.md, PULL_REQUESTS.md) and keeping SKILL.md as a concise overview with the quick reference table and links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is well-organized but quite lengthy (~250 lines). There's some repetition between the per-workflow 'Pitfalls' sections and the consolidated 'Known Pitfalls' section. The key parameters sections repeat information Claude could discover from tool schemas (which the skill itself says to fetch first). However, it avoids explaining basic concepts and stays focused on actionable details. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and clear sequences, which is good. However, there are no executable code examples or concrete invocation examples showing actual tool calls with sample parameters. Everything is described at the level of tool names and parameter lists rather than showing a complete example call with realistic values. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps, labeled as [Required]/[Optional]/[Alternative]/[Prerequisite]. Safety checkpoints are explicit (verify mergeable status before merge, require user confirmation for destructive ops, check CI before merging). The setup section has a clear 4-step verification flow. Feedback loops are present for merge operations. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a quick reference table, but it's a monolithic document with no references to supporting files. The detailed per-workflow sections (parameters, pitfalls) could be split into separate reference files. For a skill this long (~250 lines), having everything inline makes it a large context load. The external link to Composio docs is helpful but there are no bundle files for deeper reference. | 2 / 3 |
Total | 9 / 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 | |
- Repository
- davepoon/buildwithclaude
- Commit
74c7031
- 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.