agent-github-pr-manager

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

1.08x

Quality

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 is an extremely weak description that fails on all dimensions. It provides no information about what the skill does, when it should be used, or what user requests should trigger it. It reads more like a technical invocation reference than a functional description.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates, reviews, merges, and manages GitHub pull requests, adds reviewers, updates PR descriptions, and 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 wastes space that should be used for capability and trigger information.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for github-pr-manager' is entirely vague and does not describe what the skill actually does (e.g., create PRs, review PRs, merge PRs, etc.).	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 relevant term is 'github-pr-manager' which is a tool name, not a natural keyword a user would say. Missing natural terms like 'pull request', 'PR', 'review', 'merge', 'GitHub', etc.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it could overlap with any GitHub-related skill. Without specifying what PR management actions it performs, there's no way to distinguish it from other GitHub or PR-related skills.	1 / 3
	Total	4 / 12 Passed

Implementation

14%

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, explaining many concepts Claude already understands (merge strategies, PR best practices, what CI/CD is). The workflows are vague outlines rather than concrete, validated sequences, and references to 'spawning specialized agents' and 'swarm coordination' lack any implementation detail. The entire content is monolithic with no progressive disclosure or external references.

Suggestions

Cut the content by 60-70%: remove explanations of merge strategies, PR best practices, and review coordination concepts that Claude already knows. Focus only on project-specific conventions and concrete commands.

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

Replace vague steps like 'Spawn specialized review agents' with concrete implementation: actual commands, tool invocations, or code that Claude can execute.

Split content into separate files (e.g., WORKFLOWS.md, CLI_REFERENCE.md, TEMPLATES.md) and provide a concise overview with clear navigation links in the main skill file.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive content Claude already knows (what merge strategies are, what PR descriptions should contain, basic gh CLI commands). The PR description template, best practices, and multi-agent coordination sections are largely generic knowledge padding. Much of this reads like documentation for humans rather than actionable instructions for Claude.	1 / 3
Actionability	The gh CLI commands section provides some concrete, executable commands, and the PR description template is copy-paste ready. However, the workflow patterns are numbered lists of vague descriptions rather than executable steps, and concepts like 'spawn specialized review agents' and 'coordinate parallel reviews' lack any concrete implementation details.	2 / 3
Workflow Clarity	The workflow patterns are high-level descriptions without validation checkpoints or feedback loops. Steps like 'Address feedback' and 'Merge when approved' are vague. There are no explicit validation steps for destructive operations like merging, no error recovery loops, and the numbered steps read more like aspirational outlines than actionable workflows.	1 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files. Everything is inlined in a single document—the PR template, CLI reference, workflow patterns, best practices, and error handling could all be split into separate referenced files. There is no navigation structure or signposting to deeper resources.	1 / 3
	Total	5 / 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: 398f7c2

Reviewed: 3 days 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.