CtrlK
BlogDocsLog inGet started
Tessl Logo

github-pr-workflow

Working with GitHub Pull Requests using the gh CLI. Use for fetching PR details, review comments, CI status, and understanding the difference between PR-level comments vs inline code review comments.

90

1.06x
Quality

89%

Does it follow best practices?

Impact

85%

1.06x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

79%

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

This is a well-crafted skill that efficiently communicates the critical distinction between PR comment types and provides actionable commands. Its main weaknesses are the truncated workflow section and the reference to a `gh-pr-info` script without a corresponding bundle file to back it up. The command reference and API endpoints sections are excellent and immediately useful.

Suggestions

Complete the truncated 'Workflow: Addressing Review Comments' section with all steps including validation (e.g., re-running checks, verifying comment resolution).

Include the `gh-pr-info` script as a bundle file or provide its implementation inline so the skill is self-contained and the reference is resolvable.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It doesn't explain what GitHub PRs are or how git works. Every section provides information Claude wouldn't inherently know—especially the critical distinction between PR-level and inline review comments, and the custom script usage. No wasted tokens.

3 / 3

Actionability

Provides fully executable commands throughout—specific gh CLI commands, API endpoint patterns, and a custom script with clear argument syntax. The commands are copy-paste ready with placeholder conventions that are immediately understandable.

3 / 3

Workflow Clarity

The 'Workflow: Addressing Review Comments' section at the end is truncated after only 2 steps, leaving the workflow incomplete. While the commands section is well-organized, the lack of a complete workflow with validation steps (e.g., verifying fixes address comments, re-running checks) prevents a score of 3.

2 / 3

Progressive Disclosure

The content is well-structured with clear sections and a useful table, but references a script `gh-pr-info` without pointing to its source file in a bundle. No bundle files are provided, so we can't verify the script exists. The content is appropriately sized for a single file but the script reference is unresolvable.

2 / 3

Total

10

/

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 description that clearly identifies its domain (GitHub PRs via gh CLI), lists specific capabilities, and provides explicit usage triggers. The distinction between PR-level comments and inline code review comments adds valuable specificity that helps differentiate it from more general GitHub or git skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: fetching PR details, review comments, CI status, and distinguishes between PR-level comments vs inline code review comments.

3 / 3

Completeness

Clearly answers both what ('fetching PR details, review comments, CI status, understanding comment types') and when ('Use for fetching PR details, review comments, CI status') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'GitHub', 'Pull Requests', 'PR', 'gh CLI', 'review comments', 'CI status', 'code review'. These cover common variations of how users refer to PR workflows.

3 / 3

Distinctiveness Conflict Risk

Clearly scoped to GitHub PRs via the gh CLI, with specific mention of PR-level vs inline code review comments. This is a distinct niche unlikely to conflict with general git skills or other 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.

Repository
YPares/agent-skills
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.