agent-github-pr-manager

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

1.08x

Quality

13%

Does it follow best practices?

Impact

94%

1.08x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-github-pr-manager/SKILL.md

Quality

Discovery

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 description is essentially a placeholder that provides no useful information about the skill's capabilities or when to use it. It only names the skill and its invocation command, failing on every evaluation dimension. Claude would have no basis for selecting this skill appropriately from a list of available skills.

Suggestions

Add specific actions the skill performs, e.g., 'Creates, reviews, merges, and manages GitHub pull requests, adds reviewers, checks CI status.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about pull requests, PRs, code reviews, merging branches, or GitHub repository management.'

Remove the invocation instruction ('invoke with $agent-github-pr-manager') from the description as it is operational detail, not selection criteria, and replace it with functional information.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for github-pr-manager' is entirely vague and does not describe what the skill actually does with GitHub PRs (e.g., create, review, merge, list).	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states it's an 'agent skill' and how to invoke it, providing no functional or trigger information.	1 / 3
Trigger Term Quality	The only potentially useful keyword is 'github-pr-manager' which is a tool name, not a natural user term. Users would say things like 'pull request', 'PR', 'merge', 'review', 'GitHub' — none of which appear naturally here.	1 / 3
Distinctiveness Conflict Risk	The description is so generic that it could overlap with any GitHub-related skill. Without specifying what PR operations it handles, Claude cannot distinguish it from other GitHub or PR-related skills.	1 / 3
	Total	4 / 12 Passed

Implementation

27%

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

This skill is overly verbose and descriptive rather than instructional, spending significant tokens explaining PR concepts and workflows that Claude already understands. While it includes some useful concrete gh CLI commands, most content is abstract descriptions of processes without executable specifics. The monolithic structure, lack of validation checkpoints in workflows, and absence of supporting bundle files significantly reduce its effectiveness.

Suggestions

Cut the content by at least 60% — remove explanations of what PRs, merge strategies, and CI/CD are; focus only on specific commands, flags, and decision criteria Claude wouldn't already know.

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

Replace abstract workflow prose with executable command sequences — each numbered step should include the actual `gh` or `git` command to run.

Split the PR description template, error handling strategies, and multi-agent coordination into separate referenced files to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with many sections that describe concepts Claude already knows (what merge strategies are, what CI/CD integration means, what a PR description template looks like). The 'Multi-Agent Coordination' section references vague 'swarm' concepts without actionable detail. Much of this reads like documentation about PR workflows rather than targeted instructions Claude needs.	1 / 3
Actionability	The 'GitHub CLI Integration' section provides real executable commands, and the PR description template is concrete. However, most workflow patterns are listed as numbered prose steps without executable commands, and the 'Usage Examples' section shows natural language prompts rather than actionable instructions. The review swarm and multi-agent coordination sections are entirely abstract with no concrete implementation.	2 / 3
Workflow Clarity	Multiple workflow patterns are listed (Standard Feature PR, Hotfix PR, Large Feature PR) with numbered steps, but they lack validation checkpoints and feedback loops. There's no explicit 'verify before proceeding' step in any workflow. Error handling is mentioned but only as a descriptive list without concrete recovery commands or validation steps.	2 / 3
Progressive Disclosure	All content is in a single monolithic file with no references to supporting files. The skill is well over 100 lines and contains sections (PR description template, detailed error handling, multi-agent coordination) that would benefit from being split into separate referenced files. No bundle files are provided to support the content.	1 / 3
	Total	6 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/ruflo
Commit: 844f68d

Reviewed: about 10 hours ago

Table of Contents

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.