CtrlK
BlogDocsLog inGet started
Tessl Logo

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

68

Quality

85%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

62%

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

The skill is highly actionable with excellent workflow examples that include verification steps, but it suffers significantly from verbosity. It essentially duplicates gh CLI documentation that Claude already knows, inflating the token cost substantially. The progressive disclosure structure is partially implemented with references to supporting files, but too much reference-level content remains inline.

Suggestions

Move the entire 'Commands (Direct gh Usage)' section to a reference file (e.g., references/gh-commands.md) and replace with a brief note that gh commands are available for all action operations, with a link to the reference.

Remove the Configuration, Troubleshooting, Official Documentation, and Summary sections entirely — Claude knows how to use gh --help, check auth status, and find documentation. The Summary restates the skill's own content.

Consolidate the Advanced Usage section into the reference files or trim to only the gh api examples, which are the most non-obvious content.

DimensionReasoningScore

Conciseness

The skill is very verbose, essentially duplicating the gh CLI's own help documentation. The direct gh usage sections (Issues, PRs, Workflows, Repositories, Search) largely repeat what the wrapper script section already covers, and Claude already knows gh CLI commands. The Configuration, Troubleshooting, Official Documentation, and Summary sections add significant token bloat with information Claude can easily infer or look up. The summary at the end restates what was already said.

1 / 3

Actionability

The skill provides fully executable, copy-paste ready commands throughout. Both the wrapper script usage and direct gh commands are concrete with specific examples, flags, and real command patterns including jq processing and JSON output.

3 / 3

Workflow Clarity

The Examples section provides clear multi-step workflows (Daily PR Review, Create Issue and Link PR, Monitor CI Pipeline) with explicit verification steps after actions (e.g., 'Verify approval was recorded', 'Verify PR was created and linked', 'Verify rerun started'). The read/write distinction between wrapper script and direct gh is clearly articulated.

3 / 3

Progressive Disclosure

References to permissions.md and common-workflows.md are well-signaled and one level deep, which is good. However, the main SKILL.md contains far too much inline content that could be split into reference files (the entire direct gh usage section is essentially a command reference). The bundle files aren't provided, so we can't verify the referenced files exist.

2 / 3

Total

9

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly communicates what the skill does (GitHub operations via gh CLI), when to use it (with an explicit 'Use when' clause), and includes natural trigger terms users would actually say. It follows third-person voice, is concise, and is well-differentiated from other potential skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: create/manage issues, pull requests, workflows, repositories, and specifies the tool (gh CLI).

3 / 3

Completeness

Clearly answers both 'what' (create and manage GitHub issues, PRs, workflows, repos using gh CLI) and 'when' (explicit 'Use when' clause with specific trigger scenarios).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'open a PR', 'merge a pull request', 'check repo actions', 'list issues', 'create a branch', 'manage GitHub projects' — these are all phrases users naturally use.

3 / 3

Distinctiveness Conflict Risk

Clearly scoped to GitHub operations via the gh CLI, with distinct triggers like 'PR', 'pull request', 'repo actions', 'GitHub projects' that are unlikely to conflict with non-GitHub skills.

3 / 3

Total

12

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents