CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pr-gardening

Discover the pull requests this Paperclip instance opened (never community contributions), report what each is for and how confident we are that it is merge-ready, and automatically drive the non-ready ones back to green with /prepare-paperclip-pr — without ever merging.

Quality

81%

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

81%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, script-driven multi-stage workflow with strong sequencing, explicit re-verification loops, and a thorough verification section. The main weaknesses are repeated guardrail/dry-run statements and inline policy detail that could be moved to reference files.

Suggestions

Consolidate the repeated never-merge and --dry-run rules into the Hard Guardrails section and reference it once from each stage instead of restating them.

Define $RUN_DIR explicitly (e.g. RUN_DIR="$PAPERCLIP_RUN_SCRATCH_DIR/pr-gardening") where the Stage A command first uses it.

Move the marker-comment templates and Stage D edge-case policy into a references/ file to shorten the main body.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence and never explains known concepts, but guardrail statements repeat across sections ("never merge" appears in Hard Guardrails, Stage C, the marker template, and Stage F; --dry-run semantics are restated four times), so minor trimming is possible.

4 / 5

Actionability

Stages A, B, F, and the test section give copy-paste node commands, exact marker syntax, suggested comment bodies, and named API endpoints with headers. Minor gaps: $RUN_DIR is used in commands without a direct definition, and Paperclip API mutations lack full request examples.

4 / 5

Workflow Clarity

Stages A-F are clearly sequenced with explicit validation checkpoints ("Always rerun this stage after any wake", "On every wake, rerun Stage B first"), feedback loops after prepare work, mechanical termination conditions, and a verification section with expected outcome buckets — a strong fit for a batch operation.

5 / 5

Progressive Disclosure

All four referenced script paths (find-candidates.mjs, check-readiness.mjs, render-report.mjs, pr-gardening.test.mjs) exist in scripts/ and are one level deep, and sections are clearly headed. However, all policy detail, guardrail edge cases, and comment templates live inline in a ~170-line file rather than being split into reference files.

4 / 5

Total

17

/

20

Passed

Description

75%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 is highly specific, concrete, and clearly differentiated, with strong scope boundaries. Its one material weakness is the absence of any "when to use this" trigger guidance, which caps completeness.

Suggestions

Add a "Use when..." clause (e.g. "Use when asked to garden, triage, or check the merge-readiness of this instance's open PRs").

Include natural trigger variations such as "PRs", "failing checks", or "get PRs green" so users' phrasings match without exact wording.

DimensionReasoningScore

Specificity

"Discover the pull requests this Paperclip instance opened", "report what each is for and how confident we are that it is merge-ready", "drive the non-ready ones back to green" are multiple concrete, well-scoped actions with no generic filler — a clear match to the comprehensive-specificity anchor.

5 / 5

Completeness

The "what" is explicit and detailed, but there is no "Use when..." clause or equivalent trigger guidance, which the rubric says caps completeness at 3; the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

"pull requests", "merge-ready", and "back to green" are natural phrasings, but common variations users would say — "PRs", "failing checks", "CI", "review" — are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Scoping to "this Paperclip instance", naming "/prepare-paperclip-pr", and excluding community contributions carve out a clear niche with distinct triggers and minimal overlap risk against generic PR-management skills.

5 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

paperclipai/paperclip

Path

.agents/skills/pr-gardening/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.