Security audit

Work Productivity Auto Updater Workflow Helper

Security checks for vulnerabilities and agentic risk

Overview

This documentation-based workflow helper has broad activation wording but contains no automatic updater, sensitive-access instructions, or hidden execution behavior.

Expect workflow guidance and requested deliverables. Prefer explicit invocation or narrower activation keywords if the helper appears on unrelated requests; its popularity claims do not establish security or update reliability.

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

Activation keywords include everyday words without auto-updater context constraints.

Medium

Category: Trigger Abuse
Confidence: 97% confidence
Finding: Generic activation keywords such as "once", "daily", "installed", and "update" lack an explicit requirement for auto-updater context, potentially causing the skill to activate on unrelated requests if these keywords are used for routing. The metadata similarly permits activation on broad terms, increasing the possibility of unintended workflow selection. However, this README contains no executable update instructions, privileged operations, or data-exfiltration behavior, so the demonstrated risk is limited to routing interference rather than unauthorized software changes.
Content: No source excerpt is available for this finding.

Activation keywords include common words without auto-updater context constraints.

Medium

Category: Trigger Abuse
Confidence: 99% confidence
Finding: Generic activation keywords such as 'once', 'daily', 'auto', and 'update' are not constrained to auto-updater tasks, potentially activating this skill for unrelated requests when routing uses these keywords. This creates a skill-selection integrity risk, but the visible workflow is ordinary planning and validation guidance with no dangerous execution instructions, so the demonstrated impact is limited to task interference and reduced response relevance.
Content: No source excerpt is available for this finding.

Activation keywords include everyday words without requiring an auto-updater-specific context.

Medium

Category: Trigger Abuse
Confidence: 99% confidence
Finding: The activation criteria include common words such as 'once', 'daily', and 'installed' without requiring an auto-updater-related request, creating an overly broad routing condition that could activate this skill for unrelated tasks. This could divert the assistant into an irrelevant workflow, but the supplied content contains no instructions for unauthorized execution, data disclosure, or security bypass, so the demonstrated impact is low.
Content: No source excerpt is available for this finding.

Activation keywords include everyday terms without scope constraints.

Medium

Category: Trigger Abuse
Confidence: 93% confidence
Finding: The activation keywords include generic terms such as 'auto', 'once', 'daily', and 'installed' without requiring an updater-related context, potentially routing unrelated requests into this skill. The metadata reinforces this broad matching, but the supplied file only describes a planning workflow and contains no automatic installation, privileged execution, or data-transfer instructions, limiting the demonstrated impact to inappropriate activation and task misdirection.
Content: No source excerpt is available for this finding.

Activation keywords include everyday words without an explicit auto-updater context requirement.

Low

Category: Trigger Abuse
Confidence: 97% confidence
Finding: The usage keywords include broad terms such as 'once', 'daily', 'installed', and 'update', which commonly occur in requests unrelated to auto-updater workflows. Although the example trigger sentences mention the intended domain, the keyword list does not require that context or specify exclusions, creating a risk of unintended activation.
Content: No source excerpt is available for this finding.

Implicit invocation is enabled, but the description does not establish a clear activation scope.

Low

Category: Trigger Abuse
Confidence: 91% confidence
Finding: Implicit invocation is enabled, while the interface description and default prompt are vague and truncated. The supplied skill metadata further broadens activation to generic terms such as 'auto' and 'automatically', increasing the chance of unintended activation on unrelated requests; however, this file contains no executable actions, privilege changes, or exfiltration instructions that would establish a higher-impact vulnerability.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.