AI Agent Hub
Back to skills
Skill Security Detection Engine icon

Skill Security Detection Engine

IT Ops & Security Updated 2026.08.29

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

Please follow https://skillhub.cn/install/skillhub.md and install @user_c64d3056/sin129.

About this skill

Problem

Third-party skills can introduce risky behavior in code, dependencies, or prompts. Before installation, it is hard to tell whether a skill may access sensitive environments, make network calls, exceed permissions, or ship hardcoded credentials. This skill turns that review into a repeatable static check, useful before onboarding, updating, or CI gating.

How it works

It runs in a sandboxed read-only environment with only read access, dependency checks, and constrained analysis, avoiding writes and execution. It scans for:
- Code behavior: exec, system, file deletion or overwrite, network access, environment-variable tampering, privilege escalation
- Secrets: API keys, database connection strings, encryption keys, PII
- Prompt risk: malicious construction, system-instruction injection, context pollution
- Dependencies and compliance: vulnerable packages, unauthorized dependencies, cross-border data transfer, privacy leaks, signature/hash integrity

The implementation combines AST-based static pattern matching, regex-based secret detection, dependency analysis, and heuristic behavior review, then applies weighted dimension scoring to produce Low, Medium, High risk levels and confidence. It can output standard reports or JSON results, making it suitable for Skills Hub integration and CI/CD pre-checks. Treat it as static analysis: false positives are possible, large skills may scan slowly, rules need periodic updates, and high-risk findings still require manual review.

Use Cases

  • Before adding a third-party skill to an internal Skills Hub, run a read-only sandbox scan to check for risky shells, network access, and hardcoded keys.
  • Before CI merges a skill update, parse the JSON report to block high-risk dimensions and create an audit record.
  • During a skill upgrade review, compare hashes, signatures, dependency versions, and known vulnerable packages to verify integrity and supply-chain risk.
  • When users report a suspicious skill, focus on prompt injection, privilege escalation, and PII exposure, then produce a reviewable static report.

Best For

  • Skills Hub operations reviewers who need a reviewable security risk report before publishing a skill.
  • DevOps engineers maintaining CI/CD who need to connect third-party skill scan results to merge gates.
  • Security compliance engineers who need to check hardcoded secrets, PII, cross-border data, and dependency risk.
  • Platform engineers managing internal AI assistants who need to investigate prompt injection, privilege escalation, and suspicious network access.