CtrlK
BlogDocsLog inGet started
Tessl Logo

simple-pr

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

78

1.67x
Quality

66%

Does it follow best practices?

Impact

99%

1.67x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/simple-pr/SKILL.md

The canonical home for this skill is simple-pr in quickwit-oss/quickwit

SKILL.md
Quality
Evals
Security

Quality

Content

78%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-sequenced, highly actionable workflow with concrete git and gh commands and sensible abort/confirmation checkpoints. Its main flaws are minor: a step cross-reference error in Step 6, a placeholder in the gh pr create command, and one or two trimmable explanatory sentences.

Suggestions

Fix the cross-reference in Step 6: the commit message is generated in Step 4, not Step 3.

Clarify the gh pr create --body placeholder, e.g. specify using the commit message body or a brief summary of the staged changes.

Trim low-value explanatory sentences (e.g. "This ensures we're working from the latest code.") and add a lightweight verification after push (e.g. check the gh pr create output/URL before reporting).

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with direct commands, but a few sentences add little ("This ensures we're working from the latest code.", "Review the staged changes to understand what the PR will contain."), keeping it just below the 'every token earns its place' anchor.

4 / 5

Actionability

Most steps give exact, executable commands (git status, git pull origin main, git diff --cached, git checkout -b, git push, gh pr create), but "--body "{longer-description-if-needed}"" is a vague placeholder and commit-message generation lacks a concrete example.

4 / 5

Workflow Clarity

The 7-step sequence is clear with abort conditions in Step 1 and a user-confirmation checkpoint in Step 4, but Step 6 misreferences "the message from step 3" (it is generated in Step 4), and there is no verification after push/PR creation.

4 / 5

Progressive Disclosure

This is a simple skill under 50 lines with no need for external references; the content is well-organized into clearly headed sections, which qualifies for a 5 under the simple-skill guideline.

5 / 5

Total

17

/

20

Passed

Description

53%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 clearly states what the skill does but omits any 'when to use' trigger guidance, which limits its discoverability and completeness. Keywords are relevant but lack natural synonyms. Adding an explicit 'Use when...' clause with common user phrases would substantially improve it.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to create/open/submit a PR or pull request from already-staged changes."

Include natural synonyms such as "pull request", "open a PR", and "submit a PR" alongside "PR" to improve trigger-term coverage.

Slightly broaden the stated capabilities (e.g. mention branch creation and pushing) to make the 'what' more comprehensive and distinctive.

DimensionReasoningScore

Specificity

"Create a simple PR from staged changes" names the domain and concrete details ("staged changes", "auto-generated commit message"), but lists only one real action, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

The 'what' is clear (create a PR from staged changes with an auto-generated commit message), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Relevant keywords like "PR", "staged changes", and "commit message" are present, but common natural variations such as "pull request", "open a PR", or "submit a PR" are missing.

3 / 5

Distinctiveness Conflict Risk

"Simple PR from staged changes" carves a fairly distinct niche, though "PR" alone could overlap with broader pull-request or git workflow skills, keeping it at 'mostly distinct' rather than minimal conflict risk.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

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