CtrlK
BlogDocsLog inGet started
Tessl Logo

simple-pr

Create a simple PR from staged changes with an auto-generated commit message

58

Quality

68%

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/simple-pr/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 content is a well-structured, actionable 8-step PR workflow with concrete commands and real validation checkpoints. Its main weaknesses are minor over-explanation, a truncated license-header example, and a terse fix-loop that does not explicitly require re-running checks.

Suggestions

Make the Step 6 fix loop explicit: 'fix the issue, then re-run the failing check before proceeding.'

Provide the full Apache 2.0 license header instead of the truncated "// ..." so the example is copy-paste ready.

Trim filler lines such as "This ensures we're working from the latest code." to improve token efficiency.

DimensionReasoningScore

Conciseness

The 8-step workflow is efficient and mostly assumes Claude's competence (concrete commands per step); it is not a 5 because of minor over-explanation such as "This ensures we're working from the latest code." and "Review the staged changes to understand what the PR will contain."

4 / 5

Actionability

Steps give copy-paste-ready commands (git status, git diff --cached, cargo clippy, gh pr create, etc.); it is not a 5 because the commit-message generation is described rather than given as a concrete example and the license header snippet is truncated with "// ...".

4 / 5

Workflow Clarity

The 8 steps are clearly sequenced with validation checkpoints (verify staged/branch in Step 1, user confirmation in Step 4, pre-PR checks in Step 6 with a fix-before-proceeding loop); not a 5 because the Step 6 fix loop is terse and does not explicitly instruct re-running the checks after fixing.

4 / 5

Progressive Disclosure

The skill is well-organized into clearly headed sections with no external bundle files and no need for them; it is not a 5 because the body (~78 lines) slightly exceeds the under-50-line simple-skill exception and there is no overview/detail split, only minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

61%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 concrete and third-person with solid trigger terms, but it lacks an explicit 'Use when...' clause, which caps completeness. It is a clear, distinct skill description with minor room for explicit trigger guidance and synonym coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to open a pull request from already-staged changes.'

Include natural synonyms such as 'pull request' spelled out or 'submit changes for review' to broaden trigger coverage.

Optionally mention the branch-from-username convention in the description to sharpen distinctiveness from generic PR skills.

DimensionReasoningScore

Specificity

"Create a simple PR from staged changes with an auto-generated commit message" names the domain (PR creation) and two concrete actions (creating the PR, auto-generating a commit message), matching the '1-2 concrete actions but not comprehensive' anchor; not a 4 because it omits the surrounding sub-actions (branch creation, pre-PR checks, push).

3 / 5

Completeness

The 'what' is clearly stated (create a PR from staged changes with an auto-generated commit message) but there is no explicit 'Use when...' trigger clause, so completeness is capped at 3 per the missing-trigger-guidance rule.

3 / 5

Trigger Term Quality

"PR", "staged changes", and "commit message" are natural phrases a developer would say when needing this skill, giving good keyword coverage; not a 5 because the spelled-out "pull request" and synonyms like "submit changes for review" are absent.

4 / 5

Distinctiveness Conflict Risk

The niche (PR from staged changes with an auto-generated commit message) is fairly distinct with clear triggers and only minor overlap risk against generic git/PR skills; not a 5 because 'create a PR' could still collide with broader PR workflows.

4 / 5

Total

14

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
quickwit-oss/quickwit
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.