SKILLEMALL.ai

BC create-github-pr

Create GitHub pull requests using the gh CLI. Use when the user wants to create a new PR, submit code for review, or open a pull request. Trigger keywords - create PR, pull request, new PR, submit for review, code review.

NVIDIA/openshell Agent Skills author: NVIDIA Apache-2.0 1 file body ≈ 2 223 tokens Open the sourcegithub.com↗ analyzed 11 h ago

Create GitHub pull requests using the gh CLI.

As a process C 62/100 · Has gaps — References files that are not bundled: .github/PULL_REQUEST_TEMPLATE.md

IntegrationGitHubSoftware developmentWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
C
62/100
Has gaps
References files that are not bundled: .github/PULL_REQUEST_TEMPLATE.md
Tools and files w 18
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: .github/PULL_REQUEST_TEMPLATE.md

Process rating: all ten parameters 62/100

Will not run. References files that are not bundled: .github/PULL_REQUEST_TEMPLATE.md
  • 0Tools and files. 1 referenced file(s) missing: .github/PULL_REQUEST_TEMPLATE.md
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 16 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 17 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2223 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 221: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 17 items
  • +4Has examples (15 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.