SkillSpector
SkillSpector inspects AI agent skill bundles for prompt injection, credential access and other security risks before installation. It is relevant to teams reviewing external resources, especially when they need findings tied to files and source locations. We tested package 2.12.0 at a fixed commit in an isolated Python 3.12 environment. This is a commit-specific static-mode review, not a claim about the latest release, every scanner rule or optional model-assisted analysis. The package uses Apache-2.0 licensing and retains normal workflow dependencies even when model analysis is disabled.
Three handwritten skill files described a benign local task, deliberately unsafe instructions and a warning that explicitly prohibited the unsafe behavior. The benign example produced no issues and score zero. Both other examples triggered P1 instruction override and PE3 credential access, with score 42, overall MEDIUM severity and highest individual severity HIGH. With --fail-on-findings, both scans exited one. JSON retained finding evidence, and SARIF 2.1.0 contained two results. The warning example demonstrates why a static match should lead to contextual review rather than automatic classification of intent.
After reviewing the warning, we generated an explicit baseline with an explanatory reason and rescanned the same directory. Two findings were suppressed, no active issues remained and the gate returned zero. Suppression records acceptance; it does not repair the source or prove safety. All scans used --no-llm, and no unsafe specimen was executed or installed. We did not test dependency manifests, remote ingestion, CVE lookups, runtime containment or real-host behavior. Adopt it as one review step when findings and coverage limits will be examined, not as an unconditional installation approval.
Read the full review, verification scope and sources →Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-11-05
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 18
- Latest release
- v2.13.4 (2026-11-04)
- Open issues
- 178
- Recent issues with at least one comment
- 1/13
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #596 AE1 classifies opaque-by-type assets as `analysis-evasion` HIGH, discarding the ledger `reason_code` that distinguishes them from real cover8 comments · 2026-09-20
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You need an additional pre-installation review step with source locations.
- You can review findings and document narrow baseline decisions.
- You need automatic proof that a skill is safe to execute.
- You expect static matching to reliably distinguish quotation and intent.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!