Tessl • The management layer for AI agent skills

SkillPublic

github

Create and manage GitHub issues, pull requests, workflows, and repositories using the gh CLI. Use when asked to open a PR, merge a pull request, check repo actions, list issues, create a branch, or manage GitHub projects.

Quality

83%

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

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.

A well-structured, highly actionable reference with real one-level-deep bundle references and verification checkpoints in its worked examples. Its main cost is token budget: substantial sections duplicate gh CLI help and manual content Claude already knows, which inflates the SKILL.md without adding skill-specific value.

Suggestions

Cut the 'Commands (Direct gh Usage)' section down to the skill-specific read/write split and point to references or 'gh <command> --help' for the bulk command listing Claude already knows.

Drop or shrink the 'Configuration', 'Aliases', 'Troubleshooting', and 'Summary' sections, which restate gh's own documentation and repeat the intro.

Add brief error-recovery guidance to the worked examples (e.g. what to check and retry when 'prs checks 456' shows a failed CI run) to close the feedback-loop gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly free of concept-explanation padding, but large sections ('Commands (Direct gh Usage)', 'Configuration', 'Troubleshooting', the closing 'Summary') restate gh's own help output and manual content that Claude already knows and that is linked via 'Full reference' URLs anyway, so it could be tightened considerably.	3 / 5
Actionability	Commands are copy-paste ready throughout, with concrete executable examples covering common cases: the wrapper invocations ('$SKILL_DIR/scripts/github.py prs checks 456 --repo OWNER/REPO'), full-flag action commands ('gh issue create --title "Bug: Login fails" --body "Description" --label bug'), and parameterized API/jq examples.	5 / 5
Workflow Clarity	The worked examples sequence multi-step processes with explicit verification checkpoints ('# Verify approval was recorded', '# Verify PR was created and linked', '# Verify rerun started'), but there are no error-recovery feedback loops (what to do when a check or verification fails), leaving minor validation gaps.	4 / 5
Progressive Disclosure	Good structure overall: the body is an overview with clearly signaled, real, one-level-deep references ('See [permissions.md](references/permissions.md) for read/write classification of each command', 'See [common-workflows.md](references/common-workflows.md) for more examples') and a single script. The inlined direct-gh command reference duplicates manual content that could live in a reference file, a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

83%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 with an explicit 'Use when...' trigger clause, natural trigger phrases, and a clearly stated capability set anchored to the gh CLI. Its main weaknesses are generic 'create and manage' verbs in the capability statement and a couple of trigger terms that overlap with a general git skill.

Suggestions

Replace the generic 'Create and manage' verbs with the specific actions the skill supports, e.g. 'Create, view, merge, and close GitHub issues and pull requests, trigger and monitor Actions workflows, and manage repositories'.

Add missing natural trigger phrases such as 'review a PR', 'check CI status', or 'GitHub Actions' to broaden keyword coverage.

Reconsider 'create a branch' as a trigger term since it more naturally belongs to a generic git skill and raises conflict risk.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete objects — 'Create and manage GitHub issues, pull requests, workflows, and repositories using the gh CLI' — but the verbs stay at the generic 'create and manage' level rather than enumerating specific actions like merge, close, comment, or review, so it lists several targets with minor gaps rather than comprehensive concrete actions.	4 / 5
Completeness	It explicitly answers both parts: the 'what' ('Create and manage GitHub issues, pull requests, workflows, and repositories using the gh CLI') and the 'when' with concrete trigger phrases ('Use when asked to open a PR, merge a pull request, ...'), matching the anchor for clearly and explicitly answering both with concrete triggers.	5 / 5
Trigger Term Quality	'Use when asked to open a PR, merge a pull request, check repo actions, list issues, create a branch, or manage GitHub projects' provides good natural-phrase coverage users would actually say, though common variations like 'review a PR', 'close an issue', 'GitHub Actions', or 'CI status' are missing.	4 / 5
Distinctiveness Conflict Risk	'GitHub' plus the named 'gh CLI' gives a clear niche with distinct triggers, but 'create a branch' is a trigger that overlaps with a closely related generic git skill, constituting minor overlap risk rather than minimal.	4 / 5
	Total	17 / 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: odyssey4me/agent-skills
Path: skills/github/SKILL.md
Revision: ac74f8c

Reviewed: 8 days ago

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.

github

Table of Contents

Is this your skill?