CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-github-pr-manager

Agent skill for github-pr-manager - invoke with $agent-github-pr-manager

52

1.08x
Quality

Does it follow best practices?

Impact

94%

1.08x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The body is a reasonably comprehensive, well-sectioned PR-management reference with real executable gh CLI commands, but it is monolithic, padded with basic concept explanations and a stray config block, and its merge workflows lack explicit validation checkpoints. Splitting reference material into bundle files and tightening the prose would lift it notably.

Suggestions

Remove the duplicate YAML config/hooks block at the top of the body (lines 6–31) — it is leaked configuration noise, not skill guidance.

Add explicit validation checkpoints to the merge workflows, e.g. 'Run `gh pr checks` and only proceed to `gh pr merge` when all checks are passing.'

Move the PR description template and full command reference into separate reference files (e.g. references/pr-template.md, references/gh-commands.md) and link to them from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly organized reference material, but it pads in concepts Claude already knows (basic squash/merge/rebase explanations) and leads with a stray leaked YAML config/hooks block that earns no value.

2 / 3

Actionability

The 'Common Commands' section gives genuinely executable `gh pr create/review/status/merge` commands, but the workflow-pattern steps are abstract ('Create PR with detailed description', 'Assign reviewers') with placeholder arguments, so guidance is concrete but incomplete.

2 / 3

Workflow Clarity

Workflows are sequenced with numbered lists, but merging is a partially destructive operation and the steps lack explicit validation checkpoints (e.g. verify all CI checks pass before merge), which caps clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

Content is a single monolithic ~180-line file with no bundle files and no external references; sections are organized, but material that could be split out (PR description template, command reference, swarm setup) is all inline, so it sits at level 2 rather than 3.

2 / 3

Total

8

/

12

Passed

Description

7%

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 a boilerplate placeholder that names the PR-management domain but specifies no concrete actions and provides no natural trigger terms or 'when to use' guidance. It needs to be rewritten to state what the skill does and when Claude should invoke it.

Suggestions

Replace the templated text with concrete actions, e.g. 'Creates, reviews, and merges GitHub pull requests using the gh CLI, coordinates multi-agent reviews, and manages merge conflicts.'

Add an explicit trigger clause such as 'Use when the user asks to create or manage pull requests, request reviews, or merge branches on GitHub.'

Use natural user-facing terms (pull request, PR, review, merge, branch) instead of the '$agent-github-pr-manager' invocation syntax.

DimensionReasoningScore

Specificity

The description 'Agent skill for github-pr-manager - invoke with $agent-github-pr-manager' names a domain but lists zero concrete actions, matching the vague/abstract anchor rather than the 'names some actions' level 2 anchor.

1 / 3

Completeness

It gives a templated, very weak 'what' ('Agent skill for github-pr-manager') and entirely omits any 'when'/'Use when...' trigger guidance, so both halves are weak or missing.

1 / 3

Trigger Term Quality

The only 'keywords' are the invocation syntax '$agent-github-pr-manager' and 'github-pr-manager' — technical jargon a user would never naturally say instead of 'create a PR' or 'merge a pull request'.

1 / 3

Distinctiveness Conflict Risk

Tying the description to a single named niche (GitHub PR management) makes it somewhat distinguishable, but the generic templated wording offers no distinct natural triggers, so it stays below level 3.

2 / 3

Total

5

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ruvnet/claude-flow
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.