cavecrew

SAFE max severity INFOSkillSpector Safe 0 registry juliusbrussee last scanned 2 scans

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

When to delegate to `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit) or `cavecrew-reviewer` (diff review) instead of working inline or using `Explore`. Their output is compressed, so main context lasts longer.

Package
2 files, 6.5 KB
SKILL.md
512 words, 6 sections
Code
None. Instructions only.

SKILL.md covers: When to use cavecrew vs alternatives · Why this exists (the real win) · Output contracts · Chaining patterns · What NOT to do · Auto-clarity (inherited)

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
README.mddoc2.8 KB
SKILL.mddoc3.7 KB

Environment variables referenced

CAVECREW_BUILDER_MODEL CAVECREW_INVESTIGATOR_MODEL CAVECREW_REVIEWER_MODEL

Package contents recorded 2026-10-22 at commit bad48a0e1df5. 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

Scan history

DateVerdictFindingsChangeAnalyzersRaw
SAFE 1 = static bytecode pipeline correlation behavioral trigger JSON
SAFE 1 first scan static bytecode pipeline correlation behavioral trigger JSON

Sources