simple-pr
Create a simple PR from staged changes with an auto-generated commit message
72
58%
Does it follow best practices?
Impact
99%
1.67xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/simple-pr/SKILL.mdQuality
Discovery
32%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 conveys the core action (creating a simple PR with an auto-generated commit message) but lacks a 'Use when...' clause, which significantly hurts completeness. It uses some natural trigger terms but misses key variations like 'pull request'. The scope is reasonably narrow but could benefit from more explicit differentiation from related git skills.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to quickly open a pull request, create a PR from staged changes, or needs an auto-generated commit message.'
Include common trigger term variations such as 'pull request', 'git', 'open PR', 'push changes', and 'merge request' to improve discoverability.
List additional specific capabilities if applicable (e.g., 'creates a feature branch, commits staged changes with a generated message, and opens a pull request') to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (PR creation) and a couple of actions (create PR, auto-generate commit message), but doesn't list comprehensive capabilities like branch management, diff analysis, or review options. | 2 / 3 |
Completeness | Describes what it does (create a PR from staged changes with auto-generated commit message) but has no explicit 'Use when...' clause or trigger guidance, which per the rubric should cap completeness at 2, and the 'when' is entirely missing, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes natural terms like 'PR', 'staged changes', and 'commit message' which users might say, but misses common variations like 'pull request', 'git', 'push', 'merge request', or 'open a PR'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to PR creation with auto-generated commit messages, but could overlap with general git/commit message skills or broader PR management skills since it doesn't clearly delineate its narrow scope. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, actionable skill that clearly guides Claude through creating a PR from staged changes. The workflow is logically sequenced with appropriate validation checkpoints (state verification, user confirmation). Minor verbosity in explanatory phrases could be trimmed, but overall the skill is effective and practical.
Suggestions
Remove explanatory phrases Claude already knows, such as 'This ensures we're working from the latest code' and 'Review the staged changes to understand what the PR will contain' to improve token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some unnecessary verbosity - phrases like 'This ensures we're working from the latest code' explain things Claude already knows. Some steps could be tightened (e.g., the explanation about staging could be shorter). | 2 / 3 |
Actionability | Provides specific, executable git commands at each step with clear parameterization (e.g., branch naming convention, commit message format). Commands are copy-paste ready with placeholder variables clearly indicated. | 3 / 3 |
Workflow Clarity | Clear 7-step sequential workflow with validation checkpoints (checking workspace state, verifying branch, reviewing staged changes, asking user confirmation before proceeding). Includes abort conditions and explicit user confirmation gates. | 3 / 3 |
Progressive Disclosure | This is a simple, single-purpose skill under 50 lines that is well-organized with clear numbered steps and headers. No need for external references given the scope, and the content is appropriately structured. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- quickwit-oss/quickwit
- Commit
cfb53e9
- 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.