AI Agent Hub
Back to skills
Skill Vetter Pro icon

Skill Vetter Pro

IT Ops & Security Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md to install @user_80e2caa5/skill-vetter-pro

About this skill

Problem

When an agent installs a third-party skill, the risk is often hidden behavior: unsafe code, file overreach, outbound transmission, vulnerable dependencies, or post-install tampering. skill-vetter-pro turns ad hoc review into a repeatable, traceable security workflow.

How It Works

It is organized around a four-dimensional review. skill_vet.py uses AST scanning to detect patterns such as eval, exec, base64 decoding, and SSH key reads. skill_behavior_monitor.py uses strace to observe system calls, file changes, process creation, and network activity. skill_integrity_checker.py verifies SHA256 state to reduce post-review tampering risk, while dependency_cve_checker.py audits dependencies for known vulnerabilities.

The flow confirms the target and policy, checks Docker, images, and scripts, runs the review in a sub-session via sessions_spawn, and renders a verdict as LOW / MEDIUM / HIGH / EXTREME before logging it to records/vetting-log.md.

Boundaries

Use it before installing third-party skills, when re-reviewing official skills, or after alerts. Static scanning only detects known risky patterns. Runtime monitoring depends on the sandbox. CVE checks cover common manifests but do not replace patching.

Use Cases

  • Review an unknown community skill before installation and produce a risk verdict.
  • Re-audit a newly updated official skill for integrity and dependency CVE changes.
  • Investigate a skill alert by tracing runtime behavior in an isolated sub-session.
  • Check requirements.txt or package.json dependencies before onboarding an agent plugin.

Best For

  • Ops engineers installing third-party skills into agent workspaces and needing pre-install risk verdicts.
  • Platform engineers maintaining an agent skill registry and needing traceable audit records.
  • Backend engineers managing requirements.txt or package.json dependencies and needing CVE checks.
  • SREs handling security alerts and needing isolated runtime evidence for follow-up review.