CtrlK
BlogDocsLog inGet started
Tessl Logo

dryrun-pr-review

Use when the user asks to create a pull request or merge request, submit changes for review, push for review, or open a pull request.

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/dryrun-pr-review/skills/dryrun-pr-review/SKILL.md
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 an executable, well-sequenced PR-lifecycle workflow with concrete GitHub and GitLab commands and a clear re-poll feedback loop. It is concise and actionable, with only minor gaps around commit/push validation and PR-number capture.

Suggestions

Add an explicit validation checkpoint after commit/push (e.g. check exit status before opening the PR) to satisfy the destructive-operation feedback-loop guidance.

Turn the PR_NUMBER capture from `gh pr create` / `glab mr create` into actual code (e.g. parse the URL) rather than a comment hint.

Consider extracting the per-platform polling block into a bundled script under scripts/ to slim the inline SKILL.md body.

DimensionReasoningScore

Conciseness

The body is lean and purposeful — concrete bash commands with minimal prose and no padding about what a PR or git is; the duplicated per-platform polling logic and the 'Important Notes' recap are minor trims that could be made.

4 / 5

Actionability

Largely executable: complete bash for platform detection, branch, commit, push, PR/MR creation, polling, fetching and replying to comments across both GitHub and GitLab; minor gaps like capturing PR_NUMBER 'from the URL last path segment' are left as comments rather than code.

4 / 5

Workflow Clarity

A clearly numbered 7-step sequence (Branch → Commit → Push/PR → Poll → Present → Act → Re-poll) with a feedback loop back to Step 4 and an explicit timeout; git operations lack explicit success validation before proceeding, so it stops short of 5.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is a self-contained workflow with clean section headers and numbered steps; the long inlined per-platform polling blocks could plausibly live in script files, which is the minor organization gap keeping it from 5.

4 / 5

Total

16

/

20

Passed

Description

70%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 is trigger-rich and uses natural, well-covered phrasing with an explicit 'Use when' clause, but it describes only the PR-creation action and never surfaces the DryRunSecurity review-loop capability that defines the skill.

Suggestions

Add one concrete clause naming the DryRunSecurity review loop, e.g. 'opens a PR and polls DryRunSecurity review comments, presenting findings for the user to act on.'

State the 'what' explicitly alongside the 'when' so the skill's distinctive behavior is visible in the description alone.

Consider adding 'review my PR' or 'request review on my changes' as natural trigger variations.

DimensionReasoningScore

Specificity

The description names the PR/MR domain and lists concrete trigger actions ('create a pull request or merge request, submit changes for review, push for review, or open a pull request'), but these are synonyms for one action and omit the skill's distinctive capability — the DryRunSecurity review loop.

3 / 5

Completeness

It has an explicit 'Use when the user asks to...' trigger clause and the 'what' is conveyed via the action verbs (create/submit/push/open a PR); the distinctive DRS-review behavior is not stated, so it does not reach a 5.

4 / 5

Trigger Term Quality

Strong natural-keyword coverage with synonyms ('pull request', 'merge request', 'PR', 'MR', 'submit for review', 'push for review') that users would genuinely say; a few natural phrasings like 'review my changes' are absent.

4 / 5

Distinctiveness Conflict Risk

PR/MR creation is a distinct niche with specific triggers and low conflict risk; without the DryRunSecurity differentiator it reads slightly generic against built-in PR tooling, keeping it just below 5.

4 / 5

Total

15

/

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
DryRunSecurity/external-plugin-marketplace
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.