CtrlK
BlogDocsLog inGet started
Tessl Logo

pr

Open a GitHub PR targeting the correct branch with the project template

62

Quality

73%

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/pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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 exemplary: lean, fully actionable, and well-structured with a validation gate and a single well-signaled external reference. The only minor gap is an implicit rather than explicit fix-and-retry feedback loop on failing checks.

Suggestions

Make the failure feedback loop explicit (e.g., 'If `make ci` fails, fix the issues and re-run until it passes before pushing.') to reach top workflow-clarity.

Optionally note what to do if no PR template exists in the target repo, since the referenced template path is repo-dependent.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no concept over-explanation; every line (commands, branch scoping, template sections, notes) earns its place and assumes Claude's competence.

5 / 5

Actionability

Provides fully executable, copy-paste-ready commands ('make ci', 'git push -u origin HEAD', 'gh pr create --base main --fill-first') plus concrete per-section template instructions covering the common case.

5 / 5

Workflow Clarity

A clear 4-step sequence with an explicit validation gate ('make ci' must pass before opening a PR) and a template checklist, but the failure feedback loop (fix and re-run on failing checks) is implied rather than spelled out.

4 / 5

Progressive Disclosure

A sub-50-line skill with well-organized sections (Steps, Notes) and a single clearly-signaled one-level-deep reference to the PR template, matching the simple-skill exception for a top score.

5 / 5

Total

19

/

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 conveys a clear purpose and distinct niche but is held back by a missing 'when to use' trigger clause and limited trigger-term coverage. It is solid but not exemplary.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user asks to open, submit, or create a pull request / PR on GitHub.') to lift completeness.

Broaden trigger terms to include the synonym 'pull request' and natural phrasings like 'submit a PR' or 'create a pull request'.

Consider naming one or two more concrete actions (e.g., 'fill the PR template', 'push a scoped branch') to improve specificity.

DimensionReasoningScore

Specificity

Names the domain ('GitHub PR') and a couple of concrete actions ('targeting the correct branch', 'with the project template'), but the action set is narrow rather than comprehensive.

3 / 5

Completeness

It clearly states what the skill does ('Open a GitHub PR targeting the correct branch with the project template') but provides no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural terms like 'GitHub PR', 'PR', 'branch', and 'template', but omits the common synonym 'pull request' and CLI-related phrasings users might say.

3 / 5

Distinctiveness Conflict Risk

The PR-creation niche is clear and distinct from most skills, with only minor overlap risk against closely related git/PR workflows.

4 / 5

Total

13

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
EverMind-AI/EverOS
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.