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 payload, though its broad activation wording could cause unintended use.

Before installing, be aware that this helper may activate for broad security or workflow wording. Prefer explicit invocation for SkillScan-style workflow tasks, and review generated security guidance rather than treating it as an authoritative gate.

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: 97% confidence
Finding: The trigger phrases are broad enough to match ordinary user language such as 'security', 'every', 'must', or 'before', which can cause the skill to activate unexpectedly in unrelated conversations. In an agent environment, overbroad activation expands the skill's authority surface and can route sensitive or unintended tasks through this workflow, increasing the chance of misuse, prompt hijacking exposure, or confusing security decisions.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The skill description is extremely broad and includes generic terms like "security," "workflow," and "analysis," which can cause accidental invocation for unrelated user requests. Over-broad activation increases the chance that this skill intercepts prompts outside its intended scope, leading to prompt-routing errors, unwanted instruction precedence, or inappropriate handling of sensitive tasks.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 99% confidence
Finding: The keyword list contains very common words such as "security," "gate," "every," "must," "pass," and "before," which are likely to appear in many ordinary prompts. In a skill-selection system, this can cause pervasive false activations, allowing the skill to capture unrelated conversations and potentially override more appropriate or safer workflows.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 98% confidence
Finding: 触发关键词包含 security、gate、every、must、pass、before、activate 等高度常见或语义宽泛的词，会让技能在大量无关对话中被误触发。对代理系统而言，这会扩大技能适用范围并增加不相关上下文注入、错误执行安全流程或覆盖更合适技能的风险。
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 98% confidence
Finding: Enabling implicit invocation without strict activation constraints allows the platform to auto-select this skill based on vague relevance signals rather than explicit user intent. Combined with the broad productivity and security-themed metadata, this can lead to unintended invocation in many normal conversations, causing context hijacking, unnecessary privilege exposure, or unsafe workflow influence.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The trigger keywords and example phrases are overly broad and include common terms like "security," "gate," "every," and "must," which can cause the skill to activate for many unrelated user requests. In an agent environment, this creates routing confusion and may unintentionally invoke this workflow in sensitive contexts, increasing the chance of incorrect automation, analysis on the wrong artifact, or policy bypass through skill misselection.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The trigger phrases are broad enough to match common security and productivity terms such as 'security', 'gate', 'every', 'must', and 'bug fix', which can cause the skill to activate in unrelated contexts. In an agent ecosystem, overbroad activation can misroute sensitive requests to this skill, causing incorrect guidance, workflow interference, or unintended handling of security-relevant tasks.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 80% confidence
Finding: This Chinese README contains substantial English-only content in headings, descriptions, and trigger examples, but does not state that English is optional or required by design. That can amount to an implicit language policy constraint without user opt-in.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 92% confidence
Finding: The example trigger sentences are malformed and fail to define clear activation boundaries, which makes it harder for routing logic or maintainers to distinguish valid invocations from incidental text matches. Ambiguous examples reinforce over-broad triggering behavior and increase the probability of accidental skill activation in unrelated contexts.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 89% confidence
Finding: 技能描述中的激活条件使用了宽泛主题词和“或需要…支持时使用”这类开放式表述，缺少明确的排除条件与边界。这会使路由器或调用者将大量边缘请求错误归入该技能，造成误用、结果偏离用户意图，甚至在安全相关场景中产生错误的分析权重。
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 91% confidence
Finding: 示例触发句几乎复述了宽泛需求文案，未提供受限、可判别的调用模式，反而鼓励基于模糊相似度进行激活。在多技能环境中，这会提高错误匹配率，使该技能劫持本应由更专门技能处理的请求。
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The default prompt contains broad, common-language trigger terms such as 'help me' and generic workflow language, which can cause the skill to activate in unrelated conversations. This creates prompt-scope confusion and increases the chance the agent injects this skill's behavior or context when the user did not explicitly request it.
Content: No source excerpt is available for this finding.