github-gh-cli

Inspect GitHub pull requests, issues, workflow runs, and API data with the gh CLI. Use when the user wants repository facts from GitHub without opening the browser, especially for PR status, CI failures, issue lists, or structured JSON output.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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 concise and actionable with well-organized command sections and clear working rules. It scores high across the board, with only minor gaps around explicit validation steps and placeholder substitution guidance.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding; assumes Claude knows gh and GitHub concepts, presenting only commands and brief working rules that each earn their place.	5 / 5
Actionability	Provides concrete, copy-paste-ready commands grouped by task, but some placeholders ('owner/repo', '<run-id>') leave minor gaps for real execution.	4 / 5
Workflow Clarity	Commands are clearly grouped and working rules sequence decisions (prefer --json, pass --repo, ask user for auth); validation checkpoints are implicit rather than explicit.	4 / 5
Progressive Disclosure	Well-organized single-file skill under 50 lines with clear section headers and no bundle files needed; structure supports easy navigation for a simple skill.	5 / 5
	Total	18 / 20 Passed

Description

95%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 strong: it names the tool and concrete capabilities, provides explicit 'Use when' triggers with natural user phrasing, and occupies a distinct niche. Minor room to enumerate API/query actions more granularly.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Inspect GitHub pull requests, issues, workflow runs, and API data') bound to a specific tool, though API/JSON-query actions are bundled rather than enumerated individually.	4 / 5
Completeness	Clearly states what ('Inspect GitHub pull requests, issues, workflow runs, and API data with the gh CLI') and when ('Use when the user wants repository facts... especially for PR status, CI failures...') with concrete triggers.	5 / 5
Trigger Term Quality	Comprehensive natural terms users would say ('PR status', 'CI failures', 'issue lists', 'structured JSON output') plus an explicit 'Use when' clause with synonyms covered.	5 / 5
Distinctiveness Conflict Risk	Scoped to a clear niche (GitHub data via gh CLI) with distinct triggers, minimizing overlap with unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: huangruiteng/CS-Notes
Path: .codex/skills/github-gh-cli/SKILL.md
Commit: 43eb317

Reviewed: 7 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.