CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

77

1.32x
Quality

73%

Does it follow best practices?

Impact

81%

1.32x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/github-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, actionable, and includes the validation checkpoints required for destructive/batch GitHub operations. Main improvement is reducing duplication between per-workflow pitfalls and the consolidated Known Pitfalls section.

Suggestions

Remove or de-duplicate the 'Known Pitfalls' section since each pitfall already appears in its workflow's Pitfalls block, or keep only pitfalls not already covered.

Add one or two worked end-to-end examples (e.g., a full issue-creation or PR-merge walkthrough with sample parameter values) to push actionability toward copy-paste-ready.

Add brief error-recovery feedback loops (e.g., on 422 from CREATE_A_REFERENCE, fall back to UPDATE_A_REFERENCE) to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

Lean tool sequences with terse annotations and no padding of concepts Claude already knows; the standalone 'Known Pitfalls' section largely duplicates per-workflow pitfalls, a minor trim opportunity keeping it just below the lean anchor.

4 / 5

Actionability

Concrete tool slugs, explicit key parameters, and a quick-reference table give mostly executable guidance; falls short of fully copy-paste-ready worked examples but well above pseudocode.

4 / 5

Workflow Clarity

Numbered tool sequences tagged [Required]/[Optional]/[Alternative] plus explicit validation gates (verify ACTIVE connection, check mergeable status, require user confirmation before merge, check CI) satisfy the destructive/batch validation requirement, with only minor feedback-loop gaps.

4 / 5

Progressive Disclosure

No bundle files exist, but the single file is well-organized into six workflow sections, common patterns, and a quick-reference table with one clearly signaled external doc link; minor organization gaps since a skill this long could benefit from splitting reference material.

4 / 5

Total

16

/

20

Passed

Description

71%Weight 40%Scale 1-5

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 specific and domain-rich but omits an explicit 'when to use' trigger clause, which caps completeness. Distinctiveness is strong thanks to the Rube MCP/Composio framing.

Suggestions

Add a 'Use when...' clause stating natural trigger phrases (e.g., 'Use when managing GitHub repos, issues, PRs, branches, CI/CD, or permissions programmatically').

Include a few synonyms/variations users actually say (PRs, pull requests, GitHub Actions, workflows) to broaden trigger coverage.

Consider naming the underlying Composio GitHub toolkit less prominently so the trigger terms lead with user-facing language.

DimensionReasoningScore

Specificity

Enumerates concrete actions across multiple GitHub domains — 'repositories, issues, pull requests, branches, CI/CD, and permissions' plus 'review PRs, search code, and handle deployments' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

The 'what' is explicit (automate GitHub X via Rube MCP) but there is no 'Use when...' trigger clause, so per the guideline a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms (GitHub, issues, pull requests, branches, CI/CD, deployments, PRs) are well covered, but synonyms and extension-style variants are limited, so it sits above the midpoint but short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Tightly scoped to GitHub automation via Rube MCP (Composio), giving it a clear niche with only minor overlap risk against other general GitHub skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
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.