to-tickets

SAFE max severity INFOSkillSpector Safe 17 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

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

Package
2 files, 5.8 KB
SKILL.md
869 words, 12+ sections
Code
None. Instructions only.

SKILL.md covers: To Tickets · Process · 1. Gather context · 2. Explore the codebase (optional) · 3. Draft vertical slices · 4. Quiz the user · 5. Publish the tickets to the configured tracker · <NN>: <Ticket title> · Parent · What to build · Acceptance criteria · Blocked by

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.mddoc5.7 KB
agents/openai.yamlconfig146 B

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