CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-writer

Create pull requests following Sentry's engineering practices.

55

Quality

62%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/pr-writer/SKILL.md

The canonical home for this skill is pr-writer in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a strong, executable workflow with concrete commands, clear sequencing, and useful examples that assume Claude's intelligence. Minor gains are available by reducing example redundancy and adding an explicit post-creation verification checkpoint.

Suggestions

Add an explicit verification step after Step 4 (e.g. confirm the PR opened with `gh pr view` and report its URL).

Consider trimming to one or two example PR descriptions and moving the issue-reference table or examples to a reference file to improve token efficiency and progressive disclosure.

Replace the manual BASE/PR_NUMBER substitution with a concrete note or a small script snippet so commands are fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explanation of what a PR or git is); it only loses a point for three full example PR descriptions that add length beyond what one or two would convey.

4 / 5

Actionability

Provides concrete, copy-pasteable commands (gh repo view, git status, git log, git diff, gh pr create, gh api) with specific title formats; the BASE and PR_NUMBER placeholders requiring manual substitution are the minor gaps keeping it from 5.

4 / 5

Workflow Clarity

A clear four-step sequence (Verify Branch State, Analyze Changes, Write Description, Create PR) with a prerequisite check (git status --porcelain); it lacks an explicit post-creation verification step, which is the minor checkpoint gap.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with inline content and external doc links at the end; since the skill exceeds 50 lines and inlines three full examples plus an editing section, it does not qualify for the simple-skill 5.

4 / 5

Total

16

/

20

Passed

Description

50%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 states a clear purpose but is too thin: it covers only one action and provides no explicit trigger guidance. Adding a "Use when..." clause with natural synonyms (PR, draft PR, open a PR) would lift completeness and trigger quality.

Suggestions

Add a "Use when..." clause naming concrete triggers, e.g. 'Use when the user asks to open, create, or draft a pull request / PR.'

Include synonym trigger terms such as 'PR', 'draft PR', and 'open a PR' alongside 'pull requests'.

Broaden specificity beyond 'Create' to the actual capabilities, e.g. creating, drafting, and updating PRs following Sentry conventions.

DimensionReasoningScore

Specificity

Names the domain ("pull requests") and one concrete action ("Create") but offers no further actions, matching the anchor for 1-2 concrete actions without being comprehensive.

3 / 5

Completeness

Has a clear "what" ("Create pull requests following Sentry's engineering practices") but no "Use when..." clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Includes the natural term "pull requests" but omits common variations users say like "PR", "open a PR", or "draft PR", fitting the anchor with some relevant keywords missing synonyms.

3 / 5

Distinctiveness Conflict Risk

The Sentry niche adds some specificity, but the single weak trigger means it could still overlap with generic commit or PR skills, matching the somewhat-specific-but-overlapping anchor.

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.

Validation15 / 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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.