CtrlK
BlogDocsLog inGet started
Tessl Logo

github-pr-workflow

GitHub PR lifecycle: branch, commit, open, CI, merge.

58

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/github/github-pr-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The content is highly actionable and clearly sequenced with strong feedback loops, but it is somewhat redundant and fails to point readers from the overview to the existing reference files.

Suggestions

Replace the conventional-commits and CI-failure detail currently inline with clear links to references/conventional-commits.md and references/ci-troubleshooting.md.

De-duplicate the owner/repo extraction and CI-polling blocks by defining them once and reusing them.

Tighten the inline Python heredocs or move them into a shared reference to reduce token weight.

DimensionReasoningScore

Conciseness

The body is command-focused and assumes Claude's knowledge of git/GitHub, but it carries some redundancy (repeated owner/repo and auth extraction, two polling-loop variants, inline Python heredocs) that could be tightened.

2 / 3

Actionability

It provides fully executable gh and curl commands with concrete JSON payloads and complete, copy-paste-ready blocks rather than pseudocode.

3 / 3

Workflow Clarity

The seven-section lifecycle is clearly sequenced with an explicit auto-fix feedback loop (check -> read logs -> fix -> push -> re-check, up to 3 attempts then ask the user) and validation checkpoints before merge.

3 / 3

Progressive Disclosure

The bundle is well-organized one level deep (references/ci-troubleshooting.md, references/conventional-commits.md), but the SKILL.md body never links to or signals these files, so navigation from the overview to the details is missing.

2 / 3

Total

10

/

12

Passed

Description

60%

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 is concise and names concrete actions, but it omits explicit trigger guidance and natural keyword variations, leaving both completeness and trigger-term quality at the middle level.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to open, review, or merge a pull request, check CI status, or fix a failing PR check.'

Broaden trigger terms to include natural phrasings like 'pull request', 'code review', and 'PR comments' alongside 'PR' and 'CI'.

Sharpen distinctiveness by noting what falls outside this skill (e.g., review of code content vs. the lifecycle mechanics).

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'branch, commit, open, CI, merge' — matching the anchor for enumerating several specific capabilities rather than naming only a domain.

3 / 3

Completeness

It conveys what the skill does (the lifecycle actions) but lacks any explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

It includes relevant natural terms ('GitHub PR', 'CI', 'merge') but misses common variations users would actually say, such as 'pull request' spelled out, 'code review', or 'PR comments'.

2 / 3

Distinctiveness Conflict Risk

It is scoped to a clear niche (the GitHub PR lifecycle) but could still overlap with adjacent skills like github-code-review given the shared CI/merge territory.

2 / 3

Total

9

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
NousResearch/hermes-agent
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.