simple-pr

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

Install with Tessl CLI

npx tessl i github:quickwit-oss/tantivy --skill simple-pr

What are skills?

1.67x

Quality

52%

Does it follow best practices?

Impact

99%

1.67x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/simple-pr/SKILL.md

SKILL.md

Review

Evals

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 provides a basic understanding of the skill's purpose but is too terse to be effective for skill selection. It lacks explicit trigger guidance ('Use when...') and misses common keyword variations that users would naturally say. The description would benefit from expanded trigger terms and clear usage conditions.

Suggestions

Add a 'Use when...' clause specifying triggers like 'when user wants to create a pull request', 'submit code for review', or 'push staged changes'

Include keyword variations such as 'pull request', 'PR', 'git', 'GitHub', 'GitLab', 'merge request' to improve trigger term coverage

Clarify what 'simple PR' means and any limitations (e.g., single branch, no complex merge scenarios) to improve distinctiveness

Dimension	Reasoning	Score
Specificity	Names the domain (PR creation) and some actions (staged changes, auto-generated commit message), but lacks comprehensive detail about what 'simple PR' means or additional capabilities.	2 / 3
Completeness	Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant terms like 'PR', 'staged changes', and 'commit message' that users might say, but missing common variations like 'pull request', 'git', 'push', or 'branch'.	2 / 3
Distinctiveness Conflict Risk	Somewhat specific to PR creation workflow, but could overlap with general git skills, commit message generators, or code review tools without clearer boundaries.	2 / 3
	Total	7 / 12 Passed

Implementation

72%

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

This is a solid, actionable skill with clear step-by-step commands for creating a PR. The main weaknesses are minor verbosity and missing validation/error handling for the later steps (push failures, PR creation issues). The workflow is clear but could benefit from explicit checkpoints after destructive operations.

Suggestions

Remove explanatory phrases like 'This ensures we're working from the latest code' - Claude understands why git pull is needed

Add error handling guidance for step 7: what to do if push fails or gh pr create returns an error

Consider adding a validation step after commit to verify it succeeded before pushing

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some unnecessary verbosity like 'Follow these steps to create a simple PR from staged changes' and explanatory phrases like 'This ensures we're working from the latest code' that Claude doesn't need.	2 / 3
Actionability	Provides concrete, executable git commands throughout with clear syntax. Commands are copy-paste ready with placeholder variables clearly indicated in curly braces.	3 / 3
Workflow Clarity	Steps are clearly sequenced with good abort conditions in steps 1, but lacks validation checkpoints after critical operations like the commit and push. No feedback loop for handling push failures or PR creation errors.	2 / 3
Progressive Disclosure	For a simple, single-purpose skill under 50 lines, the content is well-organized with clear section headers. No external references needed and the linear flow is appropriate for this task.	3 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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

Reviewed: 15 days ago

Table of Contents

Discovery Implementation Validation

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.