CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-watch-reviews

Use when the user wants to watch the current GitHub repo for pull requests that need their review — new PRs, explicit review requests, re-requests after new commits — e.g. "watch for incoming reviews", "check PRs needing my review", or to set up a recurring check. GitHub-only (gh CLI). Not for reviewing one specific known PR (invoke pr-review directly).

72

Quality

90%

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

92%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 tightly written, highly actionable skill body with clear sequencing, explicit validation and error-recovery checkpoints, and clean progressive disclosure into references and scripts. The only mild weakness is a few rationale paragraphs that slightly pad the token budget.

DimensionReasoningScore

Conciseness

Dense and assumes Claude's intelligence throughout (no basic concept explanations), with every line carrying instruction; the 'Why the body is shaped like that' anti-drift rationale and a few qualifying clauses could be trimmed, so it sits at 'efficient; minor instances of over-explanation' rather than the maximally lean 5.

4 / 5

Actionability

Provides copy-paste-ready commands (`gh repo view --json nameWithOwner -q .nameWithOwner`, `bash .../scripts/scan.sh --once`, `--mark-armed`), a verbatim Skill(...) loop invocation, and exact output-line formats covering the common cases.

5 / 5

Workflow Clarity

The 'One pass' section is a clearly numbered sequence with explicit validation checkpoints per JSON status (error → stop and never continue; stale_in_progress → ask user, fix state, re-run from step 2) and feedback loops for error recovery.

5 / 5

Progressive Disclosure

SKILL.md is a concise overview with well-signaled one-level-deep references (references/setup.md, references/candidates.md) and a scripts/scan.sh bundle, all of which exist on disk; detailed state/interview/candidate content is appropriately split out and read only when needed.

5 / 5

Total

19

/

20

Passed

Description

87%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, well-targeted description that clearly states what it does, when to use it with natural trigger phrases, and how it differs from the related pr-review skill. Minor room to broaden trigger-term synonyms, but no significant weaknesses.

DimensionReasoningScore

Specificity

Names the domain (watching a GitHub repo for PRs needing review) and lists several concrete sub-cases — 'new PRs, explicit review requests, re-requests after new commits' and 'set up a recurring check' — with only minor gaps in coverage, fitting the 'lists several specific actions' anchor rather than the fully comprehensive 5.

4 / 5

Completeness

Explicitly answers both what ('watch the current GitHub repo for pull requests that need their review') and when ('Use when the user wants to...' with concrete trigger phrases), and adds a negative boundary, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural user phrases via the e.g. clause — 'watch for incoming reviews', 'check PRs needing my review' — plus 'recurring check', giving good keyword coverage; not a 5 because coverage is not exhaustive (no synonyms/file-extension-style variants).

4 / 5

Distinctiveness Conflict Risk

Clear niche (GitHub PRs needing the user's own review, gh CLI only) with an explicit disambiguator — 'Not for reviewing one specific known PR (invoke pr-review directly)' — minimizing conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
provectus/awos-recruitment
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.