agent-github-pr-manager

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

1.08x

Quality

24%

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

22%

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 severely lacking - it functions more as an invocation reference than a skill description. It provides no information about what PR management capabilities are available (create, review, merge, comment, etc.) and offers no guidance on when Claude should select this skill. The description fails to help Claude distinguish this skill from other GitHub or code review tools.

Suggestions

Add specific actions the skill performs, e.g., 'Creates, reviews, merges, and comments on GitHub pull requests. Lists open PRs, checks CI status, and manages reviewers.'

Add explicit trigger guidance with a 'Use when...' clause, e.g., 'Use when the user mentions pull requests, PRs, code review, merging branches, or GitHub repository management.'

Include natural keyword variations users would say: 'pull request', 'PR', 'merge', 'code review', 'GitHub', 'reviewers', 'CI checks'

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions - it only states it's an 'agent skill' that can be invoked, without explaining what the skill actually does with GitHub PRs.	1 / 3
Completeness	Fails to answer both 'what does this do' and 'when should Claude use it' - only provides invocation syntax without any functional description or usage triggers.	1 / 3
Trigger Term Quality	Contains 'github' and 'pr' which are relevant keywords users might say, but lacks natural variations like 'pull request', 'merge', 'review', 'code review', or specific PR actions.	2 / 3
Distinctiveness Conflict Risk	The 'github-pr-manager' name provides some specificity to GitHub PRs, but without describing actual capabilities, it could conflict with other GitHub-related skills or PR tools.	2 / 3
	Total	6 / 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 significantly over-engineered and verbose, explaining basic GitHub and git concepts that Claude already understands. While it contains some useful gh CLI commands, most content is descriptive rather than actionable. The lack of progressive disclosure results in a bloated document that wastes context window space.

Suggestions

Remove explanatory content about what PRs, merge strategies, and reviews are - focus only on project-specific conventions and commands

Convert workflow patterns from abstract numbered lists into executable command sequences with validation checkpoints (e.g., 'verify PR created: gh pr view --json number')

Split detailed content (PR templates, review coordination details, error handling) into separate reference files and link from a concise overview

Add explicit validation steps to workflows, especially for merge operations and conflict resolution (e.g., 'Run tests locally before pushing: npm test')

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive explanations of concepts Claude already knows (what PRs are, what merge strategies mean, basic git concepts). Contains redundant sections like 'Purpose' that restate the obvious, and workflow patterns that describe standard git operations without adding value.	1 / 3
Actionability	Includes some concrete gh CLI commands which are useful, but most content is descriptive rather than executable. Workflow patterns are numbered lists of abstract steps rather than copy-paste ready commands. The 'Usage Examples' section contains natural language prompts rather than actual implementation.	2 / 3
Workflow Clarity	Steps are listed for various workflows but lack explicit validation checkpoints. No feedback loops for error recovery - the 'Error Handling' section describes issues but doesn't integrate validation into the workflows. Missing verification steps between critical operations like merge conflict resolution.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content is inline including templates, examples, and detailed workflows that could be split into separate reference documents. No clear navigation structure or signposted links to detailed materials.	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/claude-flow
Commit: b2618f9

Reviewed: 4 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.