CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

git-pr-workflows-pr-enhance

You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensu

Quality

50%

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/git-pr-workflows-pr-enhance/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

25%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.

The body is well-sectioned but nearly content-free: generic instruction boilerplate fills the space where a concrete PR-enhancement workflow should be, and the sole reference to detailed material points at a nonexistent file. Claude would finish reading it knowing the desired output categories but not how to accomplish any of them.

Suggestions

Replace the generic Instructions with a concrete PR-enhancement workflow, e.g. inspect the diff (git diff main...HEAD or gh pr diff), draft the description from a stated template, run and compare test coverage, and propose split points for oversized PRs.

Include a filled-in example PR description or a copy-paste template under Output Format so the eight deliverable categories become executable guidance.

Fix or remove the dangling resources/implementation-playbook.md reference — either ship the playbook with worked patterns or delete the pointer so Claude is not directed to a missing file.

Cut the description-duplicating intro and the tautological Use/Do-not-use/Limitations boilerplate; state one domain-specific trigger line and one real limitation instead.

DimensionReasoningScore

Conciseness

Noticeably padded: the opening paragraph duplicates the frontmatter description verbatim, and "Use this skill when / Do not use this skill when / Limitations" sections are tautological boilerplate ("The task is unrelated to pull request enhancement") that teaches Claude nothing PR-specific. This matches anchor 2 (several unnecessary or padded sections) better than anchor 3, since well over half the body is generic scaffolding.

2 / 5

Actionability

The Instructions are entirely generic — "Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes" — with no commands (e.g. gh pr), no PR description template, and no example. The Output Format section enumerates eight deliverable names (PR Summary, Review Checklist, Risk Assessment, etc.), which is the only concrete element, but it stays at the level of high-level hints about what to produce with zero guidance on how, matching anchor 2.

2 / 5

Workflow Clarity

There is only a rough pseudo-sequence (clarify goals → apply best practices → provide steps and verification) with no domain-specific steps (analyze the diff, run coverage, draft the description, propose splits) and no validation checkpoints, matching anchor 2 (rough sequence, steps poorly defined, validation absent) rather than anchor 3's more defined step list.

2 / 5

Progressive Disclosure

The body is short with clear section headers, but its only depth pointer — "open resources/implementation-playbook.md" and the matching Resources entry — references a file that does not exist in the bundle (no resources/, references/, scripts/, or assets/ directories). The promised "detailed patterns and examples" are therefore unreachable, so navigation to the substantive content fails outright, placing this below anchor 3.

2 / 5

Total

8

/

20

Passed

Description

52%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 communicates a PR-writing/review-facilitation domain with a few natural trigger terms, but it is written in second person, is cut off mid-sentence ("ensu"), and entirely lacks a "Use when" trigger clause. It reads as a generic persona statement rather than a crisp capability-plus-trigger description.

Suggestions

Rewrite in third person and complete the truncated sentence, e.g. "Generates comprehensive PR descriptions, review checklists, and coverage analysis from a git diff. Use when creating or improving pull requests, writing PR descriptions, or preparing changes for code review."

Add an explicit "Use when..." clause listing concrete triggers (PR description, pull request, code review prep, splitting a large PR) to lift completeness above 3.

Trim buzzwords like "optimization expert" and "high-quality" in favor of one or two more concrete actions (e.g., "runs test coverage comparison", "suggests PR splits").

DimensionReasoningScore

Specificity

Phrases like "Generate comprehensive PR descriptions, automate review processes" name the domain with 1-2 actions (a base 3), but the description opens with second person ("You are a PR optimization expert"), which the guidelines penalize by 1, and the sentence is truncated mid-word ("...and ensu"), with buzzword padding ("optimization expert", "high-quality") adding no concrete capability.

2 / 5

Completeness

The "what" is stated (generate comprehensive PR descriptions, automate review processes) but there is no "Use when..." clause or equivalent trigger guidance anywhere, which caps completeness at 3 per the judging guidelines; the truncated ending further weakens the statement of capabilities.

3 / 5

Trigger Term Quality

Includes natural terms a user would say — "pull requests", "PR", "PR descriptions", "code reviews" — comparable in breadth to the anchor-4 example ("PDF files, forms, document extraction"), though common variations like "diff", "merge request", or "split a PR" are missing, keeping it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Creating high-quality pull requests" and "PR descriptions" carve a reasonably distinct niche, but "automate review processes" and "facilitate efficient code reviews" overlap broadly with code-review and commit-message skills, matching anchor 3 (somewhat specific but could overlap with similar skills) rather than anchor 4's "minor overlap risk".

3 / 5

Total

12

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/git-pr-workflows-pr-enhance/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.