Back to skill

Security audit

概念设计

Security checks for vulnerabilities and agentic risk

Overview

ClawScan’s verdict is benign with medium confidence: it found no AIG issues and only two low-to-medium concerns, though Skillspector’s analysis was partial because two local references could not be resolved.

The verdict is benign, but treat it as a moderate-confidence assessment rather than a guarantee of safety. Skillspector inspected all 27 components but marked its analysis partial because two local references could not be resolved; consider whether the detected file-reading, network, and shell capabilities and the fixed English headings suit your needs before installing.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

Skill declares no tool scope ('permissions' or 'allowed-tools') but code capabilities were detected: file_read, network, shell.

Medium
Category
MCP Least Privilege
Confidence
70% confidence
Finding

Without declared permissions the skill's intent is opaque and cannot be validated.

Content

No source excerpt is available for this finding.

Generated section headings are required to be in English without user opt-in.

Low
Category
Output Handling
Confidence
96% confidence
Finding

The contract explicitly fixes five generated section headings in English. It provides neither a user language choice nor a justification for this language constraint.

Content

No source excerpt is available for this finding.