Security audit

Work Productivity Skill Vetter Workflow Helper

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only workflow helper with poor activation scoping, but it does not request sensitive access, run code, persist changes, or hide behavior.

Install only if you want a lightweight workflow/checklist helper for Skill Vetter-style tasks. Expect possible accidental activation on generic security or GitHub prompts unless the publisher narrows triggers or disables implicit invocation.

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 skill description and use guidance are broad enough to match many ordinary requests, especially because it claims applicability to generic needs like workflows, artifacts, checklists, analysis, and implementation support. In an agent routing system, this can cause over-activation and unintended invocation, which may steer unrelated security-sensitive or productivity tasks through the wrong skill and increase the chance of unsafe or misleading outputs.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 98% confidence
Finding: The trigger keywords include very generic terms such as "security," "first," "before," and "github," which are likely to appear in many unrelated conversations. This makes accidental activation highly probable and weakens routing integrity, especially in environments where skill selection is automated from keyword matches.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The trigger keyword list includes very broad, everyday terms such as "security", "first", "before", and "github", which can cause the skill to activate in many unrelated conversations. Over-broad activation increases the chance of unintended invocation, context hijacking, and user confusion, especially for a security-themed helper where accidental routing may influence sensitive workflows.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 98% confidence
Finding: The trigger sentence starts with ordinary phrases like 'Help me' and 'I need a practical workflow', which are common in unrelated user prompts. This can cause accidental activation of the skill in contexts far outside its intended scope, leading to inappropriate routing of security-sensitive or workflow-modifying behavior based on weak intent matching.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The trigger phrases are broad, generic, and partially malformed, which increases the chance that unrelated user requests containing common words like 'security', 'first', 'before', or 'github' will invoke this skill unintentionally. In a skill that presents itself as a vetting and workflow helper, accidental invocation can misroute sensitive security-related tasks, confuse agent behavior, and cause users to rely on the wrong workflow or analysis path.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The trigger phrases include broad terms like "security", "first", "before", and "github", which are common in many unrelated user requests. This can cause the skill to activate outside its intended scope, leading to incorrect routing, unintended handling of security-related tasks, and increased exposure to prompt-collision or workflow confusion in agent environments.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 88% confidence
Finding: The example trigger sentences are malformed, truncated, and do not provide clear activation boundaries, making it harder for users and automated systems to understand when the skill should fire. Ambiguous examples can amplify misrouting caused by the already broad trigger set and lead to inconsistent or unintended use of the skill.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 84% confidence
Finding: 该文件整体为 zh-CN 中文版本，文档内容未说明这是可选语言版本，也未向用户提供语言选择或切换说明。按规则，若技能在自然语言层面强制特定语言而没有用户选择机制，可能构成语言/地区策略问题。
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 92% confidence
Finding: The description says the skill should be used whenever a user asks for broad categories like work-productivity, security, or practical support artifacts, without clearly bounding when it should not activate. This can make the skill eligible for too many requests and increases accidental selection over more appropriate or safer specialized skills.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 92% confidence
Finding: The default_prompt is overly broad and acts as a generic help-style invocation without clear task boundaries or safety-scoped triggers. Because implicit invocation is enabled, this can cause the skill to be selected in contexts it was not specifically intended for, increasing the chance of inappropriate handling of security-sensitive requests or prompt-routing confusion.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The keyword list includes highly generic terms such as 'security', 'first', 'github', and 'bug fix', which are likely to appear in many benign requests. Overbroad triggers increase the chance that the skill is invoked unexpectedly, potentially inserting the wrong workflow, exposing users to irrelevant security guidance, or interfering with safer task selection.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 80% confidence
Finding: The file is presented as a Chinese README but substantial user-facing content, including the title, core requirement description, and workflow description, is written in English. This can effectively impose a language choice on users without opt-in or explanation, which is a natural-language policy concern.
Content: No source excerpt is available for this finding.