CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pr

Push the current branch and open a draft PR for Meshtastic-Android the repo way — baseline verified first, body drafted per CONTRIBUTING.md (WHY-first, categorized changes, screenshots for UI work). Use whenever work is ready to go up as a PR.

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A tight, repo-specific SOP that delegates the canonical PR policy to CONTRIBUTING.md and adds only the surrounding steps: pre-flight baseline verification, body drafting, and push/create commands. Its one weakness is the undefined `$BODY` variable in the otherwise copy-paste-ready gh command.

Suggestions

Show how $BODY is materialized before `gh pr create` (e.g., write the drafted body to a temp file and pass its path via --body-file) so the command is fully self-contained.

DimensionReasoningScore

Conciseness

The body is lean and delegates the SOP ('this skill only adds the steps around it') while assuming Claude's competence with git and gh; every line carries repo-specific, non-obvious information with no padding.

5 / 5

Actionability

Commands are copy-paste ready with sensible placeholders (`git push -u origin HEAD`, the full `gh pr create` invocation, `git restore --source=HEAD ...`, the gradle baseline chain, the commit-pinned raw URL format), but `$BODY` is referenced in the gh command without ever being defined or materialized, a minor executable gap that keeps it below anchor 5.

4 / 5

Workflow Clarity

The three sections are clearly sequenced with an explicit validation gate ('Baseline must be green this session... If it hasn't run since the last code change, run /baseline first') that includes a recovery path, plus pre-push git status checks and a final reporting step.

5 / 5

Progressive Disclosure

At under 50 lines with no bundle files needed, the skill is well organized into three numbered sections and its repo-file references (CONTRIBUTING.md sections) are clearly signaled one level deep with exact section paths.

5 / 5

Total

19

/

20

Passed

Description

87%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.

A strong description that states concrete capabilities, scopes the skill to one repo's PR conventions, and includes an explicit 'Use whenever' trigger clause. Keyword coverage of common PR phrasings (e.g., 'pull request') is the only notable gap.

Suggestions

Add natural trigger synonyms such as 'pull request' or 'open a PR' alongside 'PR' to broaden keyword coverage.

Mention remaining actions like converting the draft to ready or reporting the PR URL to close the small specificity gap.

DimensionReasoningScore

Specificity

Names several concrete actions ('Push the current branch and open a draft PR', 'baseline verified first', 'body drafted per CONTRIBUTING.md (WHY-first, categorized changes, screenshots for UI work)') with only minor coverage gaps such as draft-to-ready conversion, so it matches anchor 4 rather than the comprehensive anchor 5.

4 / 5

Completeness

It explicitly answers what the skill does (push, open draft PR, verify baseline, draft body per CONTRIBUTING.md) and when to use it ('Use whenever work is ready to go up as a PR') with a concrete trigger phrase, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Good natural keywords ('draft PR', 'Push the current branch', 'ready to go up as a PR') that users would actually say, but common variations like 'pull request', 'open a PR', or 'submit for review' are missing, placing it at anchor 4.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — draft PR creation for Meshtastic-Android following the repo's own CONTRIBUTING.md — with PR-specific triggers, so conflict with other skills is minimal.

5 / 5

Total

18

/

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

meshtastic/Meshtastic-Android

Path

.claude/skills/pr/SKILL.md

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.