Work Productivity Weather Current Workflow Helper

• Outcome: Pass
• Latest audit: Sep 16, 2026 · 10:39 AM UTC
• Version: 0.20260729.110214

Overview

This is a documentation-only workflow helper with overly broad activation wording but no evidence of malware, data access, persistence, or destructive behavior.

Install only if you want a broad helper for Weather-style workflow planning. Be aware it may trigger on generic weather, API, key, or productivity language because implicit invocation is enabled and the activation terms are loose; review or narrow those triggers if precise routing matters.

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
• 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
• Supply Chain: Unpinned 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, generic, and include ordinary help-seeking language that could cause the skill to activate when a user did not explicitly intend to invoke it. In an agent ecosystem, this can lead to unintended workflow execution, context hijacking, or misrouting user requests to the wrong skill, especially because the skill is framed around common topics like productivity, weather, API, and bug fixing.

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 so broad that it can match ordinary requests involving productivity, weather, APIs, checklists, analysis, or implementation help, causing the skill to activate outside its intended niche. Over-broad activation increases the chance of prompt/skill hijacking, unintended routing, and application of irrelevant instructions to unrelated user 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 includes generic terms like "weather," "current," "api," "key," "required," and "users," which are common in everyday requests and likely to collide with unrelated conversations. This can spuriously invoke the skill, expanding its influence over prompts where it does not belong and making downstream behavior less predictable and less secure.

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 "weather", "current", "api", "key", "users", and "required", which can cause the skill to activate in many unrelated conversations. Over-triggering is dangerous because it can route user requests into an irrelevant workflow, causing incorrect assistance, prompt hijacking surface expansion, and unintended disclosure or manipulation opportunities in multi-skill environments.

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 broad enough to match ordinary user phrasing unrelated to this specific skill, which can cause accidental invocation or misrouting. In an agent environment, overbroad routing expands the skill's authority surface and may cause the wrong workflow, assumptions, or outputs to be applied to unrelated tasks.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

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

Finding

The invocation guidance lacks clear boundaries, exclusions, and disambiguation rules despite combining multiple generic concepts like work-productivity, weather, current, forecasts, and practical workflow help. This makes accidental or competing activation more likely, which can degrade agent routing reliability and potentially expose downstream tools or workflows to prompts that were never meant for this skill.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

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

Finding

The trigger example is extremely broad and resembles ordinary user language, which can cause the skill to activate in situations far outside its intended scope. In an agent ecosystem, overbroad activation can misroute user requests, override more appropriate skills, and increase the chance that unrelated prompts are processed under weather/workflow logic unexpectedly.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

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

Finding

This is a Chinese README, but core descriptive content is presented in English without stating that English is optional or user-selectable. In a localized skill document, this can create an implicit language constraint that does not clearly offer the user a language choice.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

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

Finding

The example trigger phrases are written in broad natural language and effectively teach the router to fire on generic requests for help or practical workflows. That lowers the precision of skill selection and can cause unintended activation on benign, unrelated prompts, which is a security and reliability risk in agentic systems.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

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

Finding

The usage condition in the description is overly broad, stating the skill should be used whenever users ask about broad topics like work-productivity, weather, current, forecasts, or api, or whenever they need practical workflow support. This creates ambiguous routing boundaries and increases the chance the skill is selected for unrelated tasks, which can degrade safety controls and produce misleading or off-target outputs.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

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

Finding

The default prompt trigger phrase is highly generic and overlaps with common user language around work, productivity, weather, forecasts, APIs, and implementation help. Combined with allow_implicit_invocation=true, this creates a realistic risk of unintended skill activation, causing the agent to route conversations into this skill when the user did not explicitly request it.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

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

Finding

This trigger is insufficiently scoped because it references a generic request for a 'practical workflow' without clearly bounding the domain, inputs, or expected task type. That ambiguity can cause the skill to activate for unrelated productivity requests, increasing the chance of incorrect tool selection, unintended data handling, or user confusion.

Content

No source excerpt is available for this finding.