Individual skill
skill-inspector
Review AI agent skills before installation using NVIDIA SkillSpector and source-aware semantic review. Use when asked whether a skill or downloaded skill folder is safe, trustworthy, installable, over-permissioned, or malicious.
skills/skill-inspector/SKILL.md
Source commit e48d771a26f7398b36256ceb8d8f94adce3d5c44
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 25,203
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-security Repository topic
- agent-skills Repository topic
- agentic-ai Repository topic
- ai-security Repository topic
- claude-code Repository topic
- mcp Repository topic
- prompt-injection Repository topic
- security-scanner Repository topic
- security-tools Repository topic
- security-workflow Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Skill Inspector
## Goal
Decide whether an AI agent skill is safe to install, keep installed, or submit for review.
Use two independent review lines:
1. SkillSpector static evidence: deterministic scanning for known risk patterns.
2. Agent semantic review: source-aware judgment about intent, permission fit, hidden behavior, and user control.
Do not rely on the numeric score alone. A low score can miss semantic risk, and a high score can be justified when sensitive behavior is clearly documented, necessary, and bounded.
## Operating Rules