CtrlK
BlogDocsLog inGet started
Tessl Logo

positron-pr-helper

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

56

Quality

63%

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 ./.claude/skills/positron-pr-helper/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and its workflow is clearly sequenced with real validation checkpoints, but it carries redundant repetitions of the tag-safety rule and fails to route to its own bundled reference file, leaving template content duplicated inline.

Suggestions

Link `references/pr-templates.md` from the body (e.g. a '## PR Body Templates' pointer) and move the inline Bug Fix / New Feature templates there to remove duplication.

State the '@:tag only in Validation Steps' rule once in the Tag Safety section and have the Tips list reference it rather than re-explaining it a third time.

Trim the first-person 'I'll' framing in Steps 1–5 to imperative, Claude-addressed instructions to save tokens.

DimensionReasoningScore

Conciseness

Most content is substantive, but the 'never write @:tag outside Validation Steps' rule is repeated three times (Tag Safety section, Step 3, and Tips) and first-person 'I'll' narration ('I'll guide you', 'I'll ask you') adds tokens that assume too little of Claude.

2 / 3

Actionability

It provides concrete executable commands (`gh issue view`, `gh pr edit`, `pbcopy`), a runnable helper script with usage syntax, complete markdown templates, and two fully worked copy-paste-ready examples with real tags and code.

3 / 3

Workflow Clarity

Steps 1–5 are clearly numbered and sequenced, with an explicit validation feedback loop (PETE Insufficient → suggest concrete additions before finalizing) and a self-check (scan the draft for stray `@:` and reword).

3 / 3

Progressive Disclosure

The body is well-sectioned, but `references/pr-templates.md` exists in the bundle yet is never referenced from SKILL.md, and template material is duplicated inline rather than offloaded to that reference, so a one-level-deep reference is left orphaned.

2 / 3

Total

10

/

12

Passed

Description

50%

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 cleanly states the skill's purpose but lacks an explicit use-when trigger and leans on technical jargon, so it sits at the middle band across all dimensions. It is competent but not maximally discoverable.

Suggestions

Add a 'Use when…' clause naming natural triggers, e.g. 'Use when creating or updating a PR body in the posit-dev/positron repository, or when you need the current e2e test tag list for Validation Steps.'

Swap jargon for user-facing phrasing: include 'pull request', 'PR description', 'validation steps' alongside 'e2e test tags'.

Name the repository explicitly to sharpen distinctiveness and avoid overlap with generic PR-writing skills.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('Generates well-structured PR bodies' and 'dynamically fetched e2e test tags'), but does not enumerate multiple specific actions like the top anchor, and 'well-structured' is a soft qualifier rather than a concrete capability.

2 / 3

Completeness

It states what the skill does but has no 'Use when…' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

'PR bodies' is a natural term a user might say, but 'dynamically fetched e2e test tags' is technical jargon and common phrasings like 'write a PR', 'open a PR', or 'create a pull request' are missing, so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The 'e2e test tags' angle gives it a niche, but it does not name the Positron repository and 'PR bodies' could overlap with generic PR-writing skills, so it is only somewhat specific.

2 / 3

Total

8

/

12

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
posit-dev/positron
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.