Work Productivity Ontology Typed Workflow Helper

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

Overview

This is a documentation-only workflow helper with broad auto-invocation wording, but no hidden code, credential access, persistence, or destructive behavior.

Installers should be aware that this skill may activate too broadly in auto-routing environments. It is best used when explicitly working on ontology-style typed workflows or related skill/workflow design, not as a general bug-fix or productivity helper.

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: 98% confidence

Finding

The skill description and usage guidance are broad enough to activate on very common terms like workflow, analysis, implementation support, knowledge, or graph, which can cause the agent to select this skill for requests outside its intended scope. That increases the chance of misrouting, inappropriate task handling, and unsafe reliance on a generic skill where a more specific or safer skill should have been used.

Content

No source excerpt is available for this finding.

Vague Triggers

High

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

Finding

The keyword trigger list includes highly generic terms such as knowledge, graph, structured, memory, creating, and bug fix without contextual constraints or negative examples. In systems that auto-select skills by keyword, this can cause frequent false matches, letting the skill intercept unrelated requests and potentially degrade safety, reliability, and least-privilege skill routing.

Content

No source excerpt is available for this finding.

Vague Triggers

High

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

Finding

The manifest allows implicit invocation while describing the skill in very broad, generic terms such as workflow, checklist, analysis, and implementation support. This creates a routing risk where the skill may be auto-selected for requests outside its narrowly intended scope, causing unintended execution of ontology or workflow-related instructions on unrelated tasks and increasing exposure to prompt-injection or unsafe tool behavior inherited from the skill.

Content

No source excerpt is available for this finding.

Vague Triggers

High

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

Finding

The trigger sentence is highly generic and can match ordinary user requests unrelated to this specific skill, increasing the chance of accidental invocation. In an agent ecosystem, overly broad activation phrases can route sensitive or irrelevant tasks to the wrong skill, causing confusion, incorrect outputs, or unsafe workflow substitution.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

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

Finding

The trigger sentence is written as a very broad natural-language request and includes generic phrases like 'Help me' and 'I need a practical workflow,' which can cause the skill to activate when the user did not explicitly intend to invoke it. In agent ecosystems, overly broad activation patterns can misroute tasks, override more appropriate skills, or cause this skill to engage on unrelated requests, reducing safety and reliability.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

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

Finding

This trigger pattern is ambiguous and matches common user phrasing without defining what makes a request specific to this skill. As a result, the skill may be selected for unrelated productivity or troubleshooting prompts, increasing the chance of unintended execution and poor task routing in multi-skill agent environments.

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 phrased like ordinary user requests, which can cause the skill to activate in contexts far beyond its intended scope. In an agent ecosystem, this increases the risk of accidental invocation, prompt collision with other skills, and unintended handling of user tasks under the wrong workflow.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

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

Finding

The skill description defines applicability using very broad categories and outcome types, including general requests for workflows, artifacts, checklists, analysis, or implementation support. In a multi-skill agent, this ambiguity can over-select the skill for unrelated tasks, increasing the chance of incorrect delegation and unsafe or low-quality task handling.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

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

Finding

The trigger keywords and example invocations are broad enough to match many generic requests such as productivity, knowledge, graph, bug fix, or creating. This can cause the skill to activate outside its intended scope, leading to prompt-routing confusion, inappropriate tool guidance, or accidental overshadowing of more specific skills.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

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

Finding

The trigger block lacks clear scope boundaries and mixes broad productivity language with domain-specific terms, making invocation criteria ambiguous. This can cause the skill to activate in contexts it was not designed for, leading to misrouting, poor task handling, and potentially unsafe reliance on an irrelevant workflow in higher-stakes environments.

Content

No source excerpt is available for this finding.

Vague Triggers

Low

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

Finding

The invocation guidance provides keywords and examples but does not define sufficient scope limits, precedence rules, or exclusion criteria. While this is not directly code-execution dangerous, it weakens skill routing safety by making accidental invocation more likely, especially in environments that rely on loose natural-language matching.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

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

Finding

Several user-facing descriptive and trigger lines are written in English inside a zh-CN README, including the main behavior description and invocation examples. This can amount to forcing a specific language presentation without explicit user opt-in or a documented language-choice mechanism.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.