CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agent-github-pr-manager

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

1.08x
Quality

51%

Does it follow best practices?

Impact

94%

1.08x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-github-pr-manager/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a reasonable high-level catalog of PR-management concerns with a few genuinely useful gh CLI commands and a good PR description template, but it is undermined by pseudocode workflow blocks, absent validation gates for destructive merge operations, and a stray duplicate YAML frontmatter embedded in the markdown. It reads as an agent feature sheet rather than an executable playbook.

Suggestions

Convert the three pseudocode ```bash workflow blocks into real, executable command sequences (actual gh commands per step) or plain numbered prose without the bash fence, and add explicit validation gates such as 'gh pr checks <num> --required' before any merge step.

Move the PR description template and the multi-agent swarm setup into references/ files (e.g. references/pr-template.md, references/review-swarm.md) and link them from the body, keeping SKILL.md as a lean overview.

Delete the second embedded YAML frontmatter block (lines 6-31) or merge its capabilities/hooks into the single top-level frontmatter — the duplicate block is malformed structure and pure token overhead.

DimensionReasoningScore

Conciseness

The body is mostly tight bullet sections but includes filler Claude does not need ('Handles rollback if needed', 'Maintain clear review SLAs', 'Coordinates with deployment pipelines') and a duplicate/embedded second YAML frontmatter block that adds noise. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is not 4 because the stray metadata block and vague filler bullets are genuinely removable.

3 / 5

Actionability

The gh CLI section gives real commands ('gh pr create --title "..." --body "..." --base main', 'gh pr merge --squash --delete-branch'), but the three 'Workflow Patterns' blocks are numbered prose lists wrapped in ```bash fences — pseudocode that is neither executable bash nor concrete steps — and many bullets are abstract ('Handles merge conflicts intelligently'). This matches 'some concrete guidance but incomplete; pseudocode instead of executable code'.

3 / 5

Workflow Clarity

Sequences exist (e.g., 'Standard Feature PR' 1-6) but contain no validation checkpoints or feedback loops — 'Run automated checks' and 'Merge when approved' are mentioned without any verify-then-proceed gate. Since merging and branch deletion are destructive operations, the guideline caps workflow clarity at 3; it is not 2 because the sequences themselves are coherent and ordered.

3 / 5

Progressive Disclosure

The body has clear section headers and no deep nesting, but there are no bundle files at all (references/, scripts/, assets/ are absent) and none are referenced; the PR description template, usage examples, and multi-agent coordination detail all sit inline in a ~180-line monolith. This matches 'some structure but could be better organized'; it is not 4 because content that clearly belongs in separate reference files (templates, swarm setup) is inlined and the stray second frontmatter block muddies navigation.

3 / 5

Total

12

/

20

Passed

Description

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

The frontmatter description fails at its core job: it states only that this is an agent skill with an invocation string, without describing any capability or any condition under which to use it. A user (or Claude) selecting a skill would have no basis to choose it over a generic PR or git skill. The rich capability list in the body's second YAML block should be surfaced here.

Suggestions

Replace the description with a concrete capability list, e.g. 'Manages the full pull request lifecycle: creates PRs with structured descriptions, coordinates multi-agent reviews, executes squash/merge/rebase strategies, and monitors CI/CD checks via the gh CLI.'

Add an explicit trigger clause, e.g. 'Use when the user asks to create, review, merge, or manage pull requests on GitHub, or mentions gh pr, PR checks, or merge conflicts.'

Remove the '$agent-github-pr-manager' invocation syntax from the description — it consumes trigger-term space without helping a user decide whether this skill applies.

DimensionReasoningScore

Specificity

The description is "Agent skill for github-pr-manager - invoke with $agent-github-pr-manager" — it names the domain (PR management on GitHub) but states zero concrete actions, offering only an invocation directive. This matches the anchor 'Names the domain but actions are minimal or generic'; it is not a 1 because the domain itself is specific rather than pure abstract language like 'Helps with documents'.

2 / 5

Completeness

There is only a vague 'what' (an 'agent skill for' a named tool) and no 'when' clause or equivalent trigger guidance whatsoever, matching 'Has a vague what and no when'. It cannot be 3 because a clear statement of what the skill does is missing, and the missing 'Use when' clause caps this dimension at 3 anyway.

2 / 5

Trigger Term Quality

The only candidate keywords are the technical identifiers 'github-pr-manager' and '$agent-github-pr-manager'; natural phrases users would actually say ('pull request', 'PR', 'merge', 'review a PR', 'gh pr') are entirely absent. This is 'one or two generic/technical keywords; missing the natural phrases users say', not 3, because there is no coverage of common variations at all.

2 / 5

Distinctiveness Conflict Risk

'github-pr-manager' identifies a fairly specific niche, but with no trigger phrases it could still be selected for overlapping tasks (e.g., generic code review, merge requests on other platforms), matching 'Somewhat specific but could still overlap with similar skills'. Not 4 because the description gives no language that would distinguish it from adjacent git/PR/review skills at trigger time.

3 / 5

Total

9

/

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

ruvnet/ruflo

Path

.agents/skills/agent-github-pr-manager/SKILL.md

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.