CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-review

Draft and post direct, unhedged GitHub PR reviews and issue comments — every item is a required change with a pointer and reason, PR reviews land as "request changes" or "approve" (never a bare comment), and nothing is marked optional or deferred to a follow-up. Use whenever understand-pr or understand-issue (or any review) is about to draft or post to GitHub.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

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

A well-structured, highly actionable protocol skill with concrete commands and strong validation gates around an outward-facing operation. Its only weakness is minor repetition of the core voice rule across sections.

Suggestions

Consolidate the no-hedging/required-changes rule so it is stated once authoritatively in "The rule" and only referenced (not restated) in "Voice" and "Before posting".

If the voice section grows, consider extracting the worked review-body templates into a references file so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

The body is dense and directive without explaining concepts Claude already knows, but the no-hedging/required-changes rule is restated across "The rule", "Voice", and "Before posting" sections and could be tightened.

4 / 5

Actionability

Provides copy-paste-ready commands covering the common cases — `gh pr review --request-changes --body-file`, `gh pr view ... --json`, the full `gh api .../reviews -X POST --input -` JSON payload with `side`/`start_line` anchoring, and `gh issue comment --body-file` — plus concrete review-body examples.

5 / 5

Workflow Clarity

Clear before/during/after sequencing with explicit validation gates: `gh auth status` once, refresh the PR via `gh pr view --json state,isDraft,author,headRefOid` immediately before each autonomous post, and a "Before posting" checklist that re-reads the body and confirms the event/requests agreement.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed; the skill is a single cohesive document organized under clear headers (Who is posting, The rule, Voice, Structure, How to post, After posting, Before posting) with no nested references, though at ~100 lines some voice-rule content could conceivably be split out.

4 / 5

Total

18

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with a clear what/when split and concrete actions. It is held back only by reliance on internal skill names for triggers and a slightly broad "or any review" clause.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Draft and post direct, unhedged GitHub PR reviews and issue comments", "every item is a required change with a pointer and reason", and routing reviews to "request changes" or "approve" — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what (draft/post unhedged required-change reviews) and when with a concrete "Use whenever understand-pr or understand-issue (or any review) is about to draft or post to GitHub" trigger clause.

5 / 5

Trigger Term Quality

Natural terms like "GitHub PR reviews", "issue comments", and "review" are present, but it leans on internal skill names ("understand-pr or understand-issue") and misses common synonyms like "code review", "pull request", or "comment on a PR".

4 / 5

Distinctiveness Conflict Risk

The niche (posting required-changes GitHub reviews in a direct voice) is clearly distinct, but the "(or any review)" phrase creates minor overlap risk with general review skills rather than zero conflict.

4 / 5

Total

18

/

20

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
mastra-ai/mastra
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.