Name: positron-pr-helper
Rating: 51.2 (1 reviews)
Author: posit-dev

Blog Docs Log in Get started

positron-pr-helper

Generates well-structured PR bodies with dynamically fetched e2e test tags

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/positron-pr-helper/SKILL.md

Quality

Content

63%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 content is actionable with a clear, validated workflow and real commands, but it is longer than necessary and duplicates template material that already lives in the references file. Progressive disclosure is weakened by inlining templates instead of pointing to the existing reference.

Suggestions

Move the inlined Bug Fix and New Feature templates out of SKILL.md and link to references/pr-templates.md instead, since that file already contains them and more.

Tighten the Tag Safety and PETE sections to remove repeated phrasing and cut overall length.

Add explicit links to the bundle files (e.g. 'See references/pr-templates.md for all PR-type templates') so the reference is clearly signaled.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and concrete, but the ~230 lines include redundant template material that also appears in references/pr-templates.md and verbose prose in the Tag Safety and PETE sections that could be tightened.	3 / 5
Actionability	It provides concrete commands (gh issue view, gh pr edit, pbcopy), a documented script invocation with format flags, and executable example PR bodies with real tags; minor gaps remain in placeholder templates like #[issue].	4 / 5
Workflow Clarity	A clear five-step sequence is present with validation checkpoints (PETE Insufficient feedback before finalizing, and a self-scan for @: outside Validation Steps), but the steps are prose-heavy rather than crisp checklists, keeping it just below a 5.	4 / 5
Progressive Disclosure	Bundle files exist (references/pr-templates.md, scripts/fetch-test-tags.sh), but PR templates are inlined in the body and largely duplicated in the reference file, and the body never links to references/pr-templates.md, so references are present but not clearly signaled and content that should be separate is inline.	3 / 5
	Total	14 / 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 and a couple of concrete actions but omits any explicit 'when to use' trigger and does not name the Positron repository that would distinguish it. It is competent but not comprehensive or tightly triggered.

Suggestions

Add an explicit 'Use when ...' clause naming natural triggers such as 'creating or updating a Positron pull request' or 'needing current e2e test tags'.

Mention the posit-dev/positron repository in the description to reduce overlap with generic PR-body skills.

Include common user phrasings ('PR description', 'pull request body', 'validation steps') alongside 'PR bodies' and 'e2e test tags'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('PR bodies') and two concrete actions ('Generates well-structured PR bodies' and 'dynamically fetched e2e test tags'), matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It gives a clear 'what' but no 'Use when...' or equivalent trigger clause; per the rubric a missing explicit trigger guidance caps completeness at 3.	3 / 5
Trigger Term Quality	It includes 'PR bodies' and 'e2e test tags' but leans technical ('dynamically fetched', 'e2e') and omits natural user phrases like 'pull request', 'PR description', or 'validation steps', so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	'PR bodies with e2e test tags' is a recognizable niche, but without naming the Positron repository it could overlap with generic PR-helper skills, so it is only somewhat distinct.	3 / 5
	Total	12 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: posit-dev/positron
Path: .claude/skills/positron-pr-helper/SKILL.md
Commit: 9bb0f27

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.