Back to skill

Security audit

doc-legacy-extract

Security checks for vulnerabilities and agentic risk

Overview

This skill is a low-risk document-processing prompt with no executable code, persistence, credential handling, or hidden data movement.

Installers should understand that the skill may activate on broad words like doc or extract, but its contents do not perform actions by themselves or request sensitive authority. Use it for user-provided legacy .doc files and verify extracted regulatory text against the source document when accuracy matters.

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 (1)

Vague Triggers

Medium
Confidence
89% confidence
Finding
The trigger keywords 'doc', 'legacy', and 'extract' are generic enough to match many unrelated user requests, which can cause the skill to activate outside its intended narrow purpose of extracting legacy Word .doc text. Over-broad activation increases the chance that the agent applies this skill in inappropriate contexts, leading to incorrect tool selection, unexpected behavior, or downstream exposure if the skill is later expanded with file-handling actions.

Static analysis

No suspicious patterns detected.