CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-github-pr-manager

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

68

1.08x
Quality

53%

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

57%

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

The body is well-structured and navigable with usable gh command examples, but several blocks are placeholder/pseudocode rather than executable guidance and merge workflows lack explicit validation checkpoints. It is solid but leaves actionability and workflow-clarity gaps.

Suggestions

Replace placeholder commands with concrete, copy-paste-ready examples (real --title/--body values and full flags) instead of '...'.

Add explicit validation checkpoints to merge workflows, e.g. 'Only run gh pr merge after `gh pr checks` reports all passing'.

Convert the prose pseudocode workflow lists into actual runnable bash steps or remove the ```bash fences from non-command numbered lists to avoid mislabeling.

DimensionReasoningScore

Conciseness

The body is mostly efficient and well-sectioned, but the 'Common Commands' block uses placeholder args ('--title "..." --body "..."') and the workflow-pattern code fences contain numbered prose rather than code, adding padding that could be tightened.

2 / 3

Actionability

It provides some concrete executable gh commands ('gh pr create --title ... --base main', 'gh pr merge --squash --delete-branch'), but several blocks are non-executable placeholders or pseudocode ('1. Create PR with detailed description') and key details like flags and reviewer assignment are missing.

2 / 3

Workflow Clarity

Multi-step processes (Standard/Hotfix/Large Feature PR) are clearly sequenced as numbered lists, but these are prose pseudocode with no validation checkpoints for destructive/batch operations like merging, and the Error Handling section only describes issues rather than gating 'merge only when checks pass'.

2 / 3

Progressive Disclosure

For a single-file skill under ~150 lines with no external bundle files, content is well organized into clear sections (Purpose, Workflow Patterns, CLI Integration, Best Practices, Error Handling) that support easy navigation, satisfying the simple-skill criterion for a top score.

3 / 3

Total

9

/

12

Passed

Description

50%

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 clearly states what the skill does and lists capabilities, but it lacks an explicit 'Use when...' trigger clause and only partially covers natural user phrasings. It is adequate but not exemplary.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when creating, reviewing, merging, or troubleshooting pull requests via the gh CLI.'

Expand trigger terms to include natural variations users would say, such as 'merge', 'code review', 'open a PR', and 'CI checks'.

Restate capabilities as concrete action verbs ('Creates, reviews, and merges pull requests...') rather than terse hyphenated tags to reach full specificity.

DimensionReasoningScore

Specificity

It names the domain ('pull request lifecycle management') and several concrete actions via the capability list ('pr-creation', 'merge-management', 'conflict-resolution'), but these are terse tags rather than full concrete action phrases, so it stops short of the multi-action 3 anchor.

2 / 3

Completeness

It answers 'what' clearly ('Complete pull request lifecycle management and GitHub workflow coordination') but provides no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

It includes 'pull request', 'PR', and 'GitHub workflow', which are relevant natural terms, but it misses common variations a user would actually say ('merge', 'code review', 'open a PR', 'CI checks'), so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The PR/GitHub-CLI niche is reasonably distinct from unrelated skills, yet 'GitHub workflow coordination' is broad and could overlap with generic CI/CD or code-review skills, so it is not a clear conflict-free niche.

2 / 3

Total

8

/

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.