Back to skill

Security audit

AI员工协作技能包

Security checks for vulnerabilities and agentic risk

Overview

This AI team-management skill is mostly coherent with its stated purpose, but its local file handling is under-scoped and can escape intended directories through unvalidated inputs.

Install only if you are comfortable with a local prototype that writes persistent config and memory files. Use it in a dedicated workspace with non-sensitive data, avoid untrusted employee role/template inputs, and review or patch path validation and deletion/retention controls before using it with business or private information.

Vulnerability Patterns
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (2)

T09 · Insecure Skill Coding Practices

Error
Location
scripts/employee-manager.js:53
Finding

Path Traversal Through Attacker-Controlled Employee Role and Identifier

Content
View full analysis
Remediation
View remediation

T05 · Unauthorized Access and Privilege Escalation

Error
Location
scripts/employee-manager.js:85
Finding

Arbitrary Local File Read Through Template Path Traversal

Content
View full analysis
/workflow.md`. 7. Any party or subsequent component able to access that workflow file can ...[truncated 726 chars]
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (7)

Tp4

High
Category
MCP Tool Poisoning
Confidence
91% confidence
Finding

The skill documentation promises collaboration features like automatic task assignment, progress monitoring, and reporting, but the analyzed behavior reportedly includes undeclared local filesystem read/write and archival operations plus CLI employee-management actions. This mismatch is security-relevant because users may grant trust and permissions based on the stated purpose while the skill performs broader actions that can affect local data and system state.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The README states that work records are automatically saved to the memory/ directory and reloaded on startup, but it does not warn users about retention, possible sensitive data accumulation, or how to review and delete stored data. In a multi-agent collaboration skill, stored task history may contain business plans, credentials, customer information, or internal discussions, so silent persistence creates meaningful privacy and security risk.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

Advertising persistent memory and real-time status monitoring without disclosing retention, access, deletion, or privacy boundaries can lead users to expose sensitive operational or personal data without informed consent. In a team-automation context, monitored status and long-term memory may contain project details, employee activity, or business secrets, increasing privacy and compliance risk.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The natural-language comments, error messages, logs, and CLI usage are presented only in Chinese throughout the file, which imposes a specific language on users. The file does not offer a language option or explain that the skill is intentionally limited to a Chinese-speaking or region-specific context.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The CLI directly executes the 'fire' command from user input, which removes the employee from the active roster and moves that employee's memory directory to an archive. Although there is a status check and a post-action log message, there is no pre-action confirmation or user-facing warning before this potentially disruptive state-changing operation runs.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
85% confidence
Finding

A language policy issue exists when a skill effectively forces a specific language without user opt-in or documented justification. This README presents all instructions, commands context, and operational guidance only in Chinese, with no alternative language option or note that the skill is intended solely for a Chinese-speaking audience.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
89% confidence
Finding

The natural-language instructions, descriptions, commands, and role explanations are all written in Chinese, which effectively forces a specific language experience. The file does not indicate that this is a China-specific or Chinese-only skill, nor does it offer users an alternative language or explicit opt-in.

Content

No source excerpt is available for this finding.