Security audit

Work Productivity Skillscan Security Workflow Helper

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only workflow helper with no executable code, but its activation wording is overly broad and users should invoke it intentionally.

Install only if you want a general SkillScan-style workflow helper, and prefer explicit invocation because the published trigger terms are broad enough to match unrelated productivity or security requests.

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

Vague Triggers

High

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The trigger phrases are excessively broad and include generic terms such as 'security', 'every', 'must', 'before', and 'bug fix', which can cause the skill to activate in many unrelated contexts. In an agent ecosystem, this creates routing ambiguity and increases the chance that sensitive or security-relevant requests are intercepted by the wrong skill, leading to incorrect guidance or unsafe workflow execution.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The description says to use the skill when a user asks for broad categories such as 'work-productivity', 'security', or 'checklist, analysis, or implementation support,' without defining clear boundaries. This ambiguity increases the chance of overmatching, causing the skill to activate in unrelated situations and making behavior less predictable and easier to misuse in prompt-routing systems.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 98% confidence
Finding: The trigger list is excessively broad and includes common words like 'security', 'every', 'must', 'pass', and 'before', which are likely to appear in many unrelated conversations. This can cause accidental or inappropriate skill activation, expanding the skill's influence beyond intended contexts and potentially interfering with safer routing or user intent handling.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The trigger keywords include extremely broad everyday terms such as 'security', 'every', 'must', 'pass', and 'before', which can cause the skill to activate in many unrelated conversations. Over-broad activation increases the chance that this skill injects workflow guidance into contexts where it was not requested, potentially overriding more appropriate skills or contaminating security-sensitive tasks with irrelevant instructions.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 98% confidence
Finding: The trigger sentence is extremely broad and includes generic terms that can appear in many normal user requests, which creates a real risk of unintended skill activation. In an agent ecosystem, overbroad activation can route unrelated tasks into this skill, causing incorrect handling, bypass of user intent boundaries, and expansion of the skill's operational scope beyond what the user actually requested.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 90% confidence
Finding: The invocation conditions are ambiguous because the listed keywords and trigger sentences do not clearly define when this skill should or should not run. That ambiguity can cause over-triggering in multi-skill systems, especially because terms like 'security', 'gate', 'every', and 'before' are common and could capture unrelated requests, leading to unintended processing of user input.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The trigger sentence is broad and resembles ordinary user language, which increases the chance that the skill activates unintentionally during unrelated conversations. In an agent environment, accidental activation can redirect workflow execution, inject irrelevant instructions, or cause the wrong skill to handle sensitive security-oriented tasks.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 78% confidence
Finding: This file is labeled as a Chinese README, but key usage content and trigger phrases are written in English, effectively imposing a language expectation without explicit user opt-in or justification. That can create a language/locale policy issue because users are not offered a clear choice of interaction language.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 88% confidence
Finding: 文件名和正文均表明该技能为 zh-CN 中文版本，但文档中未声明是否允许根据用户偏好切换语言，且示例触发句仍混用英文。对语言输出的默认约束若无用户选择或明确说明，可能构成语言/locale 策略问题。
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 92% confidence
Finding: The description says to use the skill when users mention broad categories like work-productivity, skillscan, security, or need general workflow/checklist support, but it does not clearly define boundaries for activation. This ambiguity can lead to accidental invocation in unrelated requests, creating prompt-routing confusion and increasing the attack surface for skill misuse.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The default prompt embeds a long, generic trigger phrase covering common workplace terms like 'work-productivity', 'security', 'workflow', 'checklist', and 'analysis', which increases the chance of unintended activation during ordinary user requests. Because implicit invocation is enabled, this broad matching can cause the skill to run in contexts the user did not explicitly intend, expanding prompt-surface exposure and potentially injecting unreviewed behavior into unrelated conversations.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 91% confidence
Finding: This trigger phrasing is ambiguous and lacks clear boundaries, making it easy for unrelated requests to match accidentally. Because the skill is positioned for security and workflow assistance, accidental invocation can misapply security-oriented behavior to benign tasks or crowd out a more appropriate skill, reducing reliability and potentially affecting downstream decisions.
Content: No source excerpt is available for this finding.