CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

76

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An exemplary short command-reference skill: concise, fully executable, and well organized with practical edge-case rules for auth and repository scoping. Nothing material is missing for its scope.

DimensionReasoningScore

Conciseness

The body is lean with zero concept explanations or padding — every line is either a working rule or an executable command, fully assuming Claude's competence.

5 / 5

Actionability

All commands are copy-paste ready (e.g. "gh pr view 123 --repo owner/repo", "gh run view <run-id> --repo owner/repo --log-failed") and cover the common cases for PRs, CI runs, issues, and API queries.

5 / 5

Workflow Clarity

This is a simple read-only single-action skill where each command is unambiguous; the Working rules section adds scoping guidance and an auth checkpoint ("If auth is missing, ask the user to handle `gh auth login`"), so the simple-skill exception applies.

5 / 5

Progressive Disclosure

At roughly 50 lines with no need for external references, the body is well organized into clear sections (When / Working rules / Common commands by area), satisfying the simple-skill criterion for progressive disclosure.

5 / 5

Total

20

/

20

Passed

Description

87%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.

A strong description in third-person voice that explicitly states both capabilities and use-when triggers with concrete natural phrases. Only minor gaps: the action verb is generic ("inspect") and a few common synonyms (GitHub Actions, checks) are absent.

DimensionReasoningScore

Specificity

"Inspect GitHub pull requests, issues, workflow runs, and API data" names several concrete capabilities with the gh CLI, but the single generic verb "inspect" leaves minor gaps versus the comprehensive multi-action coverage of the top anchor.

4 / 5

Completeness

It explicitly answers what ("Inspect GitHub pull requests, issues, workflow runs, and API data with the gh CLI") and when ("Use when the user wants repository facts from GitHub... especially for PR status, CI failures, issue lists, or structured JSON output") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"PR status, CI failures, issue lists, structured JSON output" are natural phrases users would say, but common synonyms like "GitHub Actions", "checks", and "pull request reviews" are missing from keyword coverage.

4 / 5

Distinctiveness Conflict Risk

The gh CLI niche with distinct triggers (PR status, CI failures, structured JSON) is clearly distinguishable from other skills with minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

100%

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