SKILLEMALL.ai

BC opensandbox-release-notes

Generate umbrella release notes for the whole OpenSandbox repository (docs/releases/X.Y.Z.md) by analyzing all merged PRs since the previous release baseline. Triggered when users ask to write or generate OpenSandbox release notes, changelogs, or release summaries for a specific version.

opensandbox-group/OpenSandbox Agent Skills author: opensandbox-group Apache-2.0 2 files body ≈ 4 265 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Generate umbrella release notes for the whole OpenSandbox repository (docs/releases/X.Y.Z.md) by analyzing all merged PRs since the previous release baseline.…

As a process C 53/100 · Has gaps — References files that are not bundled: …, …pull/NNNN

GeneratorGitHubKubernetesDockerSoftware developmentWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
C
53/100
Has gaps
References files that are not bundled: …, …pull/NNNN
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: …
  • warning missing-ref reference to a missing file: …pull/NNNN
  • note edit-residue the text marks something as outdated (lines 14, 21, 33, 50, 71, 189): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 53/100

Will not run. References files that are not bundled: …, …pull/NNNN
  • 0Tools and files. 2 referenced file(s) missing: …, …pull/NNNN
  • 0Result and completion. Does not say what the result is
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 25 mutating operations with no state check
  • 70Execution cost. Instruction body is 4265 tokens
  • 85Steps. 46 steps, 3 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (27 tags): a typed call is more reliable

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 288: enough signal without eating the budget
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 46 items
  • +4Has examples (4 code blocks)

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