CtrlK
BlogDocsLog inGet started
Tessl Logo

prepare-paperclip-pr

Prepare a Paperclip branch for PR with commits, template body, and checks.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/prepare-paperclip-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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, highly actionable procedure with a clear numbered workflow, validation checkpoints, and feedback loops. Its only weakness is redundant ALL-CAPS emphasis that slightly inflates token use without adding information.

Suggestions

Remove the redundant 'RUN GREPTILE UNTIL IT GETS TO 5/5 - DO NOT STOP...' line that duplicates the /greploop bullet above it.

Collapse 'YOU DO NOT MERGE THE PR YOURSELF. NEVER MERGE THE PR YOURSELF.' to a single statement to cut redundant tokens.

DimensionReasoningScore

Conciseness

The body is mostly lean and action-oriented, but the redundant ALL-CAPS lines ('RUN GREPTILE UNTIL IT GETS TO 5/5 - DO NOT STOP...' duplicating the /greploop bullet, and 'YOU DO NOT MERGE... NEVER MERGE...') pad tokens that don't each earn their place.

2 / 3

Actionability

Gives concrete, executable guidance throughout: exact commands (`git rev-parse --git-dir`, `gh`), a literal commit trailer, specific files (`pnpm-lock.yaml`), numeric thresholds (100 files, 5/5), and named skills (/greploop, /prcheckloop).

3 / 3

Workflow Clarity

A clearly numbered 0–6 sequence with explicit validation checkpoints (re-verify after rebase, guardrails checklist) and a feedback loop (/greploop until 5/5, address comments, push, repeat).

3 / 3

Progressive Disclosure

A single well-organized SKILL.md with clearly numbered sections and one-level, clearly signaled external references (CONTRIBUTING.md, the /greploop and /prcheckloop skills); no nested or buried references.

3 / 3

Total

11

/

12

Passed

Description

67%

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 specific and distinctively scoped to Paperclip PRs, but it omits an explicit 'Use when' trigger clause and only partially covers natural trigger-term variations. Adding a usage-trigger sentence would lift completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when finishing Paperclip branch work and opening a reviewed pull request against paperclipai/paperclip master.'

Add natural trigger variations like 'pull request' or 'open a PR' alongside 'PR' to improve keyword coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'commits, template body, and checks' — naming the domain (Paperclip PR prep) with three specific deliverables rather than vague language.

3 / 3

Completeness

Clearly states what the skill does but lacks any 'Use when...' trigger clause, so the 'when' guidance is only implied — capping completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Includes relevant natural keywords ('Paperclip', 'PR', 'branch', 'commits') but misses common variations like 'pull request' or 'open a PR', so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The 'Paperclip' qualifier gives it a clear, narrow niche with distinct triggers, making conflict with unrelated skills unlikely.

3 / 3

Total

10

/

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.