diagnosing-bugs

SAFE max severity INFOSkillSpector Caution 27 registry mattpocock last scanned 1 scan

Verdict safe, but 1 finding (1 info), mainly policy violation. Most recent scan 2026-10-22.

Second scanner: NVIDIA SkillSpector

Independent static run, no language model, over the same files as the Cisco scan above. How the two scanners compare across the whole corpus: Two scanners, one corpus.

What this skill does

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

Package
3 files, 9.8 KB
SKILL.md
1403 words, 12+ sections
Code
Shell (1)

SKILL.md covers: Diagnosing Bugs · Redact · Phase 1: Build a feedback loop · Ways to construct one, in roughly this order · Tighten the loop · Non-deterministic bugs · When you genuinely cannot build a loop · Completion criterion: a tight loop that goes red · Phase 2: Reproduce + minimise · Minimise · Phase 3: Hypothesise · Phase 4: Instrument

Findings

INFO Skill does not specify a license Policy Violationstatic

Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms.

SKILL.md

Remediation: Add 'license' field to SKILL.md frontmatter (e.g., MIT, Apache-2.0)

What is in the package

FileKindSize
SKILL.mddoc8.5 KB
agents/openai.yamlconfig103 B
scripts/hitl-loop.template.shscript1.3 KB

Package contents recorded 2026-10-22 at commit 5beb35b040e3. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.

What we checked

What we did not check

Sources