CtrlK
BlogDocsLog inGet started
Tessl Logo

prcheckloop

Iterate on a GitHub PR until latest-head checks are green or a precise blocker is named. Use when a PR still has failing or pending checks after review fixes, including after greploop.

80

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.

The body is a tight, executable workflow with concrete gh/git commands, explicit validation checkpoints, and a well-defined feedback loop, organized into clearly labeled sections. It adds only what Claude would not already know and stays within a single appropriately structured file.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no filler explaining what a PR or CI check is, and every line is a command, a state classification, or an exit condition. Nothing to trim without losing useful signal.

3 / 3

Actionability

Provides copy-paste-ready executable commands (gh pr view, gh api check-runs/status, gh run view --log-failed, git push) plus a failure-type → action table. Guidance is concrete and directly runnable.

3 / 3

Workflow Clarity

Clear 8-step sequence with explicit validation checkpoints (poll until terminal state, 'Only rerun a failed job once without code changes', 'loop is only complete when the remote PR checks ... are green') and a genuine fix → push → refresh SHA → restart feedback loop.

3 / 3

Progressive Disclosure

No bundle files are present; the single self-contained SKILL.md is well-organized into Scope, Inputs, Workflow, Output, and Notes sections. Per the rubric's simple-skills note, a clear single-file structure scores 3 without external references.

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.

The description is concise, specific, and includes an explicit 'Use when' trigger clause that clearly scopes the skill to PR-check repair. It distinguishes itself from related skills, leaving little room for conflict.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Iterate on a GitHub PR until latest-head checks are green or a precise blocker is named' — rather than vague language. It names the domain (GitHub PR checks) and the specific outcomes (green checks, named blocker).

3 / 3

Completeness

Explicitly answers both what ('Iterate on a GitHub PR until latest-head checks are green or a precise blocker is named') and when ('Use when a PR still has failing or pending checks after review fixes, including after greploop'). The explicit 'Use when' trigger satisfies the completeness bar.

3 / 3

Trigger Term Quality

Uses natural terms users would say — 'GitHub PR', 'failing or pending checks', 'after review fixes' — covering common phrasings like 'PR checks are failing'. Coverage is good and not jargon-only.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — a PR-check repair loop — and explicitly distinguishes itself from check-pr and greploop, making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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
paperclipai/paperclip
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.