Name: github
Rating: 61.6 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

github

Use the `gh` CLI for issues, pull requests, Actions runs, and GitHub API queries.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/github/SKILL.md

The canonical home for this skill is github in administrakt0r/AI-Agents-Safe-Coding-Skills

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 highly actionable with copy-paste-ready gh commands and a clear debugging workflow, organized into clean sections. Its main weakness is redundancy — the debugging sequence repeats commands already shown — which lightly hurts conciseness and organization.

Suggestions

Consolidate the duplicated commands: keep the 'Debugging a CI Failure' sequence as the canonical numbered workflow and prune the standalone command list in 'Pull Requests' to avoid repeating the same four commands.

Add a brief 'next step' after fetching failure logs (e.g. how to act on the error) to close the workflow with a recovery/feedback loop.

Tighten the JSON Output intro ('Most commands support --json... You can use --jq to filter') into a single clause to save tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence, but the 'Debugging a CI Failure' section re-lists the same four commands already shown in 'Pull Requests', which is redundancy that could be tightened — fitting the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (e.g. `gh pr checks 55 --repo owner/repo`, `gh api repos/owner/repo/pulls/55 --jq '...'`) with concrete examples covering the common cases, matching the top anchor.	5 / 5
Workflow Clarity	The 'Debugging a CI Failure' workflow is a clear 4-step sequence with a labeled purpose per step; it is a read-only investigation so the destructive/batch validation cap does not apply, but there is no explicit recovery loop once logs are obtained, keeping it just below 5.	4 / 5
Progressive Disclosure	Self-contained CLI reference with well-organized sections (When to Use, Pull Requests, Debugging, API, JSON Output) and no need for external bundle files; minor organization gaps from the duplicated command listing keep it just below 5.	4 / 5
	Total	16 / 20 Passed

Description

70%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 well-scoped to the gh CLI with strong distinctiveness, but it lacks an explicit 'Use when...' trigger clause, which caps completeness at 3. Trigger-term coverage is good yet misses common synonyms like 'CI' and 'workflows'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about GitHub issues, pull requests, CI/Actions failures, or needs gh api queries.'

Include common synonyms users say — 'CI', 'workflows', 'GitHub Actions' — alongside 'Actions runs' to broaden trigger coverage.

Lead with concrete verbs (e.g. 'View, list, and inspect GitHub issues, PRs, and Actions runs') to strengthen the action framing.

Dimension	Reasoning	Score
Specificity	Names the tool (`gh` CLI) and several concrete task areas — 'issues, pull requests, Actions runs, and GitHub API queries' — with only minor coverage gaps, fitting the 'lists several specific actions' anchor rather than the 1-2 actions of a 3.	4 / 5
Completeness	The 'what' is clear (use gh CLI for those tasks) but there is no explicit 'Use when...' trigger clause, so per the boundary guidance completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural terms users say ('issues', 'pull requests', 'GitHub API'), but misses common synonyms like 'CI', 'workflows', or 'GitHub Actions', so it lands just below the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	Scoped specifically to GitHub's `gh` CLI for issues/PRs/Actions/API — a clear niche with distinct triggers and minimal overlap risk, since plain git does not cover these.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/github/SKILL.md
Commit: 57c135b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.