ClawHub
Back to skill

Security audit

前端开发规范

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only frontend standards skill with no executable behavior or hidden access requests.

Installers should treat this as a Chinese-language frontend coding standards reference. It appears safe from a security perspective, but users may want narrower triggers or explicit language-preference handling for better usability.

A.I.G

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

SkillSpector

Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Natural-Language Policy Violations

Medium
Confidence
88% confidence
Finding
The skill metadata, title, and usage examples are entirely written in Chinese, with no indication that other languages are supported or that the user can choose their preferred language. Under the language/locale policy, a skill should not implicitly force a specific language unless the constraint is explicitly justified or optional.

Vague Triggers

Medium
Confidence
93% confidence
Finding
The trigger field includes generic phrases such as “代码规范”, “命名规范”, and “前端最佳实践”, which are broad enough to match many normal conversations rather than a narrowly scoped invocation. The file does not provide exclusion conditions or negative examples to clarify when the skill should not activate.

Static analysis

No suspicious patterns detected.