CtrlK
BlogDocsLog inGet started
Tessl Logo

pull-requests

Create and review pull requests following project standards including title format, description template, and review checklist. Use when creating PRs, writing PR descriptions, or reviewing pull requests.

71

Quality

86%

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

86%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 concise, well-structured skill body with concrete templates and a review checklist. It is lean and appropriately scoped, with only minor room to add explicit pre-merge validation checkpoints.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — no padding, no explaining of concepts Claude already knows; every line (title examples, template, bullets, checklist) earns its place.

5 / 5

Actionability

Provides copy-paste ready title examples, a complete PR description template, and a concrete review checklist; mostly executable guidance with minor gaps for an instruction-style skill.

4 / 5

Workflow Clarity

Clear sequencing of author and reviewer responsibilities with a checklist, though explicit validation/retry checkpoints (e.g., verify CI before merging) are only implicit.

4 / 5

Progressive Disclosure

A simple, single-purpose skill under 50 lines with no external references needed; well-organized into clearly headed sections, qualifying for the simple-skill exception.

5 / 5

Total

18

/

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 description that clearly states both capabilities and explicit use-when triggers, with concrete, distinct pull-request terminology. Minor gains possible from adding synonyms like 'code review'.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Create and review pull requests', 'title format', 'description template', and 'review checklist' — with only minor coverage gaps, matching the anchor for listing several specific actions.

4 / 5

Completeness

Explicitly answers both what (create/review PRs with title format, description template, review checklist) and when ('Use when creating PRs, writing PR descriptions, or reviewing pull requests') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural triggers 'creating PRs, writing PR descriptions, or reviewing pull requests' cover good keyword ground, though common synonyms like 'code review' are missing.

4 / 5

Distinctiveness Conflict Risk

'Pull requests' is a clear niche with distinct triggers and minimal conflict risk against other skills.

5 / 5

Total

18

/

20

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
redis/RedisInsight
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.