Back to skill

Security audit

Email Reply Assistant Skill

Security checks for vulnerabilities and agentic risk

Overview

This is a simple email-reply/template guidance skill with no executable code, persistence, credential use, or hidden data access.

Review the scope before installing: this skill is low risk, but its activation wording is broad, so use it when you specifically want email or communication-drafting help and avoid pasting secrets or unnecessary personal information.

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
  • 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)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The activation guidance is broad enough to match many generic communication requests, which can cause the skill to trigger outside its intended narrow use case. Overbroad routing increases the chance that users provide unnecessary email content or sensitive context to a generic assistant workflow, even though the skill itself includes otherwise safe guardrails.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The example prompt is phrased so generically that it overlaps with ordinary requests for planning help, making accidental activation more likely. In an agent ecosystem, vague triggers can misroute tasks to the wrong skill and weaken safety-by-specialization, especially when users did not intend to invoke an email-focused workflow.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.