SKILLEMALL.ai

BB fix-issue

Fix a GitHub issue in NeMo Speech (NVIDIA-NeMo/Speech). Read the issue, reproduce the bug with a failing test, implement the fix, and verify tests pass. Only opens a PR if the user explicitly asks for it.

NVIDIA-NeMo/Speech Agent Skills author: NVIDIA-NeMo Apache-2.0 1 file body ≈ 702 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Fix a GitHub issue in NeMo Speech (NVIDIA-NeMo/Speech).

As a process B 69/100 · Nearly there — weak spots: result and completion, running it twice

ProcedureGitHubWriting and documentsSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
B
69/100
Nearly there
Result and completion w 14
0
Running it twice w 4
30
When it triggers w 12
50
the three weakest of ten parameters · all ten

How to improve

    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

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 69/100

    • 0Result and completion. Does not say what the result is
    • 30Running it twice. 1 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 55Failures and branches. 1 branches
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 22 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 702 tokens
    • 100Progress reporting. Reports progress

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

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