Back to skill

Security audit

feishu-doc-tech-optimizer

Security checks for vulnerabilities and agentic risk

Overview

This is a simple Feishu technical-document rewriting prompt with restrictive style rules, but no hidden code, credential access, persistence, or external data handling.

Install this only if you want a strongly opinionated Feishu technical-document polishing prompt. Review the generated or applied edits before relying on them, especially for documents where tone, terminology, or preserving original wording matters.

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • 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
Findings (2)

Vague Triggers

Medium
Confidence
92% confidence
Finding
The skill description is broad enough to match many generic document-editing requests, which can cause the agent to invoke this skill outside a narrowly intended context. That increases the chance of unintended overwrites or style-enforcement on unrelated Feishu documents, especially because the prompt demands direct modification and suppresses confirmation or explanation.

Natural-Language Policy Violations

Medium
Confidence
90% confidence
Finding
The skill hard-codes a restrictive language and style policy without user opt-in, including banned common wording and mandatory output structure. This can override user intent, degrade correctness for documents that require different tone or terminology, and create unsafe autonomous behavior because the skill prioritizes its own formatting constraints over the user's actual requirements.

Static analysis

No suspicious patterns detected.