Work Productivity Skill Vetter Workflow Helper

• Outcome: Pass
• Latest audit: Sep 16, 2026 · 10:05 AM UTC
• Version: 0.1.0

Overview

This is a documentation-only workflow helper with overly broad activation wording, but it does not request sensitive access, run code, persist itself, or hide unrelated behavior.

Before installing, be aware that this skill may be selected too broadly because it allows implicit invocation and lists common trigger words. It is best suited for explicit skill-vetting or skill-hardening requests, not general GitHub, security, or bug-fix help.

A.I.G

Vulnerability Patterns

• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally
• Unauthorized Access and Privilege Escalation: Obtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access

Findings (11)

Vague Triggers

High

• Category: Not specified by scanner
• Confidence: 95% confidence

Finding

The trigger keywords and example invocations are broad terms like 'security', 'first', 'github', and 'bug fix', which are common in ordinary conversations and can cause accidental activation of the skill outside its intended scope. In an agent ecosystem, this increases the chance of inappropriate routing, unexpected workflow injection, or the skill being invoked during unrelated tasks where its instructions may alter behavior or outputs.

Content

No source excerpt is available for this finding.

Vague Triggers

High

• Category: Not specified by scanner
• Confidence: 98% confidence

Finding

The manifest description includes broad terms like 'security' and 'first' that are likely to match many unrelated prompts, causing the skill to activate outside its intended scope. Overbroad activation can route sensitive or general-purpose requests into a skill with assumptions and workflows the user did not intend, increasing the chance of unsafe guidance, prompt hijacking via unintended invocation, or degraded agent reliability.

Content

No source excerpt is available for this finding.

Vague Triggers

High

• Category: Not specified by scanner
• Confidence: 99% confidence

Finding

The trigger keyword list contains ambiguous everyday terms such as 'security', 'first', 'before', and 'github' without qualifiers, making accidental activation highly likely. In an agent ecosystem, this can cause the wrong skill to intercept broad classes of requests, which is dangerous because it weakens user intent matching and may expose users to irrelevant or unsafe operational advice.

Content

No source excerpt is available for this finding.

Vague Triggers

High

• Category: Not specified by scanner
• Confidence: 97% confidence

Finding

The trigger list includes very common terms such as "security", "first", "before", and "github", which are likely to appear in many unrelated conversations. This can cause unintended activation of the skill, potentially injecting irrelevant workflow guidance into security-sensitive or general productivity contexts and overriding more appropriate routing.

Content

No source excerpt is available for this finding.

Vague Triggers

High

• Category: Not specified by scanner
• Confidence: 96% confidence

Finding

The trigger sentences and keywords are broad enough to match common requests like 'security', 'github', 'first', or generic workflow/help phrasing, which can cause the skill to activate outside its intended scope. In an agent ecosystem, overbroad activation can route unrelated user tasks into this skill, leading to incorrect handling, prompt-context contamination, and reduced trust in skill selection.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

• Category: Not specified by scanner
• Confidence: 94% confidence

Finding

The trigger phrases are broad, generic, and include common terms like 'security', 'github', 'first', and 'bug fix', which can cause the skill to activate outside its intended scope. In an agent environment, ambiguous activation boundaries can lead to unintended routing, incorrect assistance, or a security-review workflow being applied when the user did not request it, increasing the chance of unsafe or confusing behavior.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

• Category: Not specified by scanner
• Confidence: 88% confidence

Finding

This file is presented as a Chinese-language README, but the operational usage text and example trigger phrases are only in English. That creates an implicit language constraint without user opt-in or an explicit bilingual choice, which is a natural-language policy concern.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

• Category: Not specified by scanner
• Confidence: 93% confidence

Finding

The example trigger sentences are vague and repetitive, and they do not establish clear activation boundaries for when this skill should or should not run. Because examples often shape downstream routing behavior and author expectations, weak examples reinforce over-triggering and make accidental invocation more likely in contexts involving generic bug fixing or security help.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

• Category: Not specified by scanner
• Confidence: 89% confidence

Finding

The activation description mixes broad categories like work-productivity, security, practical workflow, checklist, analysis, and implementation support without clear boundaries. This ambiguity increases the chance the skill will be selected for tasks outside its intended scope, leading to misrouting and potentially unsafe or low-quality assistance in adjacent contexts.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

• Category: Not specified by scanner
• Confidence: 95% confidence

Finding

The default prompt is triggered by very broad, everyday terms such as 'work-productivity', 'security', 'first', and generic requests for help or analysis, which can cause the skill to activate in many contexts unrelated to the user's intent. Because implicit invocation is enabled, this increases the chance of prompt hijacking of normal conversations, unintended disclosure of skill behavior, or unwanted steering of user workflows.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

• Category: Not specified by scanner
• Confidence: 82% confidence

Finding

Providing English and Chinese variants without stating how language selection occurs can cause the wrong instruction set or user-facing content to be used. While not inherently dangerous on its own, ambiguity in language routing can degrade reliability, confuse users, and in edge cases cause safety-critical instructions to be missed or misunderstood.

Content

No source excerpt is available for this finding.