ClawHub
Back to skill

Security audit

Agile Pm Workflow Modular

Security checks for vulnerabilities and agentic risk

Overview

This is a Chinese-language product-management workflow skill that guides document and prototype planning with user confirmation and does not request system access or run code.

Install this if you want a Chinese-language PM workflow assistant for structuring requirements and delivery documents. Be aware it may activate on broad product-requirement descriptions, so confirm the selected modules before proceeding.

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
82% confidence
Finding
The primary instructions and workflow content are presented in Chinese, and the file does not indicate that the user may choose another language. For a general-purpose skill, fixing the interaction language without opt-in can violate language/locale policy expectations.

Vague Triggers

Medium
Confidence
95% confidence
Finding
The trigger condition is overly broad because the skill can activate not only on an explicit command but also whenever a user merely describes a requirement. This increases the chance of unintended invocation, context hijacking, or the skill taking over ordinary conversation flows without clear user consent, which is especially risky for a workflow that drives multi-step structured outputs.

Static analysis

No suspicious patterns detected.