CtrlK
BlogDocsLog inGet started
Tessl Logo

pr

Push the current branch and open a draft PR for Meshtastic-Android the repo way — baseline verified first, body drafted per .github/copilot-pull-request-instructions.md (WHY-first, categorized changes), screenshots embedded via commit-pinned raw URLs. Use whenever work is ready to go up as a PR.

74

Quality

91%

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

100%

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

The body is an efficient, executable SOP wrapper: well-sequenced with a validation checkpoint, copy-paste commands, and a single clearly signaled external reference. It assumes Claude's competence and adds only repo-specific procedural detail.

DimensionReasoningScore

Conciseness

Lean and directive throughout: it defers detail to the SOP file rather than re-explaining concepts, and every line is actionable instruction (e.g. 'Pin to the SHA that contains the image, not the branch name') with no padding about what a PR or a branch is.

3 / 3

Actionability

Provides copy-paste-ready commands (`git push -u origin HEAD`, the `gh pr create --draft ...` invocation, the commit-pinned raw-URL template) plus concrete flags and exact tail content, leaving little to interpret.

3 / 3

Workflow Clarity

A clear pre-flight → body → push-and-open sequence with an explicit validation checkpoint ('Baseline must be green this session') and a stated recovery path ('If it hasn't run since the last code change, run /baseline first'), addressing the risky pre-push gate.

3 / 3

Progressive Disclosure

No bundle files exist, and the body is a compact, well-sectioned overview that signals its one external reference (the SOP file) clearly; for a sub-50-line skill with no nested references this matches the simple-skill allowance for a top score.

3 / 3

Total

12

/

12

Passed

Description

82%

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 is concrete and complete, covering both what the skill does and when to trigger it within a tight, repo-specific niche. Its only weak spot is trigger-term breadth, relying almost entirely on the single keyword 'PR'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'Push the current branch and open a draft PR', 'baseline verified first', 'body drafted per .github/copilot-pull-request-instructions.md', 'screenshots embedded via commit-pinned raw URLs' — a specific, multi-step action set rather than vague language.

3 / 3

Completeness

Explicitly answers what it does ('Push the current branch and open a draft PR...') and when to use it ('Use whenever work is ready to go up as a PR'), satisfying both halves with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes the natural trigger 'Use whenever work is ready to go up as a PR', but the keyword surface is narrow (only 'PR' / 'draft PR'); common phrasings like 'open a pull request', 'submit code for review', or 'propose changes' are not covered.

2 / 3

Distinctiveness Conflict Risk

Scoped to a specific repo workflow ('Meshtastic-Android the repo way', SOP file, baseline commands, screenshot embedding) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
meshtastic/Meshtastic-Android
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.