CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gh-review-requests

Find unread GitHub review-request notifications for open PRs in one confirmed repository, filtered by a confirmed team or reviewer.

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 ./.agents/skills/gh-review-requests/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

66%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.

The body presents a clear confirm-scope → read-queue → present-results workflow with explicit validation checkpoints and strong failure-mode handling, but it leans on a helper script that is absent from the bundle and restates its authorization caveats in every section. Commands are concrete in form, yet the primary execution path is not runnable as shipped due to the missing and inconsistently-pathed script.

Suggestions

Bundle the helper script (e.g. under scripts/) or make its path resolvable, and align the "../../../scripts/github-review-requests.mjs" location with the "scripts/..." invocation run from the repository root.

Consolidate the repeated authorization/scoping caveats into the "Confirm the scope" section instead of restating them in each section.

Drop the checkout-specific hardcode ("This checkout belongs to BigSimmo/Communication") or generalize it into a clearly-labeled example.

DimensionReasoningScore

Conciseness

The body is mostly efficient — it explains no concepts Claude already knows — but the authorization/scoping caveats repeat across every section ("Never assume an organization from this copied skill", "do not switch to another organization", "Never fall back to account-wide notifications/search or a different owner/team"), and the hardcoded "This checkout belongs to `BigSimmo/Communication`" is environment-specific noise. Not 4: the repetition is more than minor over-explanation; not 2: there is no padded conceptual exposition.

3 / 5

Actionability

Concrete commands are given ("node scripts/github-review-requests.mjs --repo ExampleOrg/example-repo --team ExampleOrg/example-team", "git remote get-url origin", "gh pr list --repo github.com/OWNER/REPO --state open --search 'team-review-requested:OWNER/TEAM'"), but the primary helper is referenced at "../../../scripts/github-review-requests.mjs" and no scripts/ directory exists in the bundle, and the invocation path ("scripts/..." from the repository root) is inconsistent with that location — so the main path is not executable as shipped. Not 4: a missing helper script is a key gap, not a minor one; not 2: the commands themselves are specific and complete in form, not high-level hints.

3 / 5

Workflow Clarity

A clear sequence (Confirm the scope → Read the scoped queue → Present results and limits) with explicit validation checkpoints: verify the remote host via `git remote get-url origin` before deriving OWNER/REPO, "Stop for GitHub Enterprise", the helper "validates the operands" and "checks that the PR is open, unmerged and still requests that team/reviewer", and "Report zero only after a successful lookup; unavailable tooling, denied access and a failed request are not an empty queue" — an explicit failure-recovery distinction. The skill is read-only, so the destructive/batch cap does not apply. Not 4: essentially all checkpoints are present, including failure-mode handling.

5 / 5

Progressive Disclosure

The body is short (~40 lines) and organized into three well-signed sections, fitting the simple-skill pattern where good organization alone can score highly; however, it depends on a helper whose referenced path ("../../../scripts/github-review-requests.mjs") does not resolve — no references/, scripts/, or assets/ directories exist in the bundle. Not 5: the one external reference is dangling; not 3: nothing that belongs in a separate file is inlined and the structure is otherwise clear.

4 / 5

Total

15

/

20

Passed

Description

57%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.

The description states a clear, distinctive "what" — finding unread GitHub review-request notifications for open PRs scoped to one repository and a confirmed team or reviewer — but it entirely lacks a "when to use" trigger clause and natural synonyms such as "pull request" or "code review". It occupies a narrow niche with minimal conflict risk, yet would surface poorly for users phrasing the need differently.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to check pending GitHub review requests, their review queue, or unread review-request notifications."

Include natural synonyms such as "pull request", "code review", and "review queue" so the description surfaces for varied user phrasings.

Briefly state what is presented (PR number, title, URL, reason) to sharpen the "what" without adding length.

DimensionReasoningScore

Specificity

"Find unread GitHub review-request notifications for open PRs" names the domain and one concrete action with scope qualifiers ("in one confirmed repository, filtered by a confirmed team or reviewer"), matching the anchor for 1-2 concrete actions without comprehensive coverage. Not 4: it does not list several distinct specific actions, only a single find operation with filters; not 2: the action is concrete and domain-specific, not generic.

3 / 5

Completeness

The "what" is clear ("Find unread GitHub review-request notifications for open PRs... filtered by a confirmed team or reviewer") but there is no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. Not 4: the "when" is entirely absent, not merely implicit or imprecise.

3 / 5

Trigger Term Quality

It contains relevant, natural terms — "GitHub", "review-request", "notifications", "open PRs", "team", "reviewer" — but misses common variations a user would say, such as "pull request", "code review", or "review queue". This matches the anchor for some relevant keywords while missing common variations; not 4 because the keyword set is narrow with no synonyms, not 2 because the terms are domain-natural rather than generic.

3 / 5

Distinctiveness Conflict Risk

"unread GitHub review-request notifications for open PRs in one confirmed repository, filtered by a confirmed team or reviewer" carves out a clear niche with distinct triggers and minimal overlap with general GitHub, PR, or notification skills. Not 4: the trigger surface is as narrowly scoped as the domain allows — conflict risk is minimal, not just minor.

5 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/github-review-requests.mjs)

Warning

Total

14

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/gh-review-requests/SKILL.md

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.