CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-review-triage

Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

An exemplary instruction-only skill: lean, highly actionable, and well-structured, with sharp edge-case rules that preempt common misjudgments (zero checks, administrative vs functional CI, mergeable ≠ ready). No bundle files are present or needed given the skill's scope.

DimensionReasoningScore

Conciseness

The body is lean — a compact enum-style output template plus tight rules — with no explanation of concepts Claude already knows; every line earns its place.

3 / 3

Actionability

It gives an exact per-PR output template and concrete decision rules with specific thresholds (idle >4 days, high-risk labels → escalate-human), so Claude knows precisely what to produce and how to decide.

3 / 3

Workflow Clarity

This is a single, unambiguous triage-and-report task; per the simple-skill exception workflow clarity scores 3, and no destructive/batch validation cap applies since the skill is read-only.

3 / 3

Progressive Disclosure

Under 50 lines with no external references needed and well-organized sections (## Per-PR Output, ## Rules); no bundle files exist, so the simple-skill exception applies.

3 / 3

Total

12

/

12

Passed

Description

100%

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 concise, third-person description that states concrete capabilities and provides an explicit use-trigger, covering both what and when clearly. The only mild weakness is the "PR babysitter loops" trigger phrasing being slightly jargon-flavored, but natural keyword coverage is strong overall.

DimensionReasoningScore

Specificity

"Triage open pull requests for CI status, review comments, and merge readiness" lists multiple concrete actions rather than a single vague domain, matching the score-3 anchor.

3 / 3

Completeness

It answers what ("Triage open pull requests for...") and supplies an explicit when clause ("Use in PR babysitter loops"), satisfying the score-3 both-answered requirement.

3 / 3

Trigger Term Quality

Natural user terms appear throughout — "pull requests", "PR", "CI status", "review comments", "merge readiness" — giving good coverage rather than a single keyword.

3 / 3

Distinctiveness Conflict Risk

The PR-triage-for-CI/review/merge-readiness niche with babysitter-loop triggers is distinct and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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
cobusgreyling/loop-engineering
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.