create-pr

Create a pull request for the current branch with proper labels and description

Quality

55%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

Content

77%

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

This is a strong, actionable skill with a well-sequenced workflow covering edge cases and decision points. The main weakness is some content duplication between the step-by-step instructions and the PR Description Guidelines section, which inflates token usage without adding value. The concrete examples, clear conditional logic, and specific label criteria make this highly usable.

Suggestions

Remove or significantly condense the 'PR Description Guidelines (from CONTRIBUTING.md)' section since it duplicates what's already specified in step 10's PR body instructions.

Consider extracting the label decision logic (step 9) into a concise decision table for faster scanning.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some redundancy — the PR Description Guidelines section largely repeats what's already covered in step 10's PR body instructions. The CONTRIBUTING.md section could be removed or condensed since the same information is already embedded in the workflow steps.	2 / 3
Actionability	The skill provides concrete, executable commands throughout (git log, git diff, gh pr create with specific flags), a complete bash example with proper flag usage, clear label selection criteria, and specific conventional commit format examples. Everything is copy-paste ready.	3 / 3
Workflow Clarity	The 10-step workflow is clearly sequenced with appropriate validation checkpoints — checking branch state, handling edge cases (no changes, main branch), conditional steps (codex review, draft vs real), and clear decision logic for labels. The branch check in step 1 includes a feedback loop for handling uncommitted changes.	3 / 3
Progressive Disclosure	The content is well-structured with clear sections (Instructions, Guidelines, Example, Usage, Output), but the PR Description Guidelines section is essentially duplicated content from step 10 that adds length without new information. For a standalone skill with no bundle files, the organization is reasonable but the inline duplication hurts.	2 / 3
	Total	10 / 12 Passed

Description

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 communicates the core action (creating a pull request) but lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill. It also misses common trigger term variations like 'PR' and 'GitHub', and could be more specific about the full range of capabilities.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to open a PR, submit code for review, or push changes for merging.'

Include common trigger term variations such as 'PR', 'merge request', 'GitHub pull request', 'open a PR', and 'code review'.

Expand the capability list to mention related actions if applicable, such as setting reviewers, linking issues, or drafting PR descriptions from commit history.

Dimension	Reasoning	Score
Specificity	Names the domain (pull requests) and some actions (create with labels and description), but doesn't list multiple concrete actions beyond creation — e.g., no mention of updating PRs, adding reviewers, linking issues, or other PR-related tasks.	2 / 3
Completeness	Describes what the skill does (create a PR with labels and description) but has no explicit 'Use when...' clause or equivalent 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 'pull request', 'branch', 'labels', and 'description' which are relevant keywords, but misses common variations like 'PR', 'merge request', 'open a PR', 'GitHub', or 'code review'.	2 / 3
Distinctiveness Conflict Risk	Fairly specific to pull request creation which narrows the domain, but could overlap with general Git workflow skills or GitHub automation skills since it doesn't clearly delineate its unique scope.	2 / 3
	Total	7 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: DataDog/datadog-agent
Commit: 409dcc9

Reviewed: about 10 hours 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.