Work Productivity Ontology Typed Workflow Helper

• Outcome: Pass
• Latest audit: Aug 17, 2026 · 4:13 AM UTC
• Version: 0.20260817.40422

Overview

This is a documentation-only workflow helper with overbroad activation wording but no hidden execution, credential access, persistence, or data exfiltration behavior.

Installers should understand that this skill may be selected for fairly broad workflow or ontology-adjacent requests. Review whether its broad implicit invocation fits your environment, especially if you rely on precise skill routing, but no dangerous runtime behavior was found in the inspected artifacts.

SkillSpector

By NVIDIA

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 (10)

Vague Triggers

Medium

• Confidence: 87% confidence
• Finding: The trigger sentence is broad and phrased like ordinary user language, which can cause the skill to activate in contexts where the user did not explicitly intend to invoke it. In agent ecosystems, unintended activation can route prompts into the wrong workflow, leading to inappropriate actions, confusing outputs, or interference with higher-priority skills.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The invocation guidance is ambiguous and spans generic concepts such as workflow, ontology, bug fixing, and hardening without defining boundaries. This increases the chance of accidental skill selection or prompt hijacking by unrelated requests that happen to contain overlapping terms, reducing reliability and potentially exposing users to unintended behavior.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The trigger phrases are broad enough to match routine user requests about workflows, bug fixes, or productivity, which can cause the skill to activate outside its intended scope. In an agent ecosystem, overbroad activation increases the chance of unintended tool use, context hijacking, or the skill influencing tasks where its assumptions and safeguards do not fit.

Vague Triggers

High

• Confidence: 96% confidence
• Finding: The skill description is broad enough to match many generic productivity, workflow, checklist, analysis, and implementation-support requests that are not specific to a narrowly defined capability. This can cause over-invocation or unintended routing, making the agent apply this skill in inappropriate contexts and potentially override safer or more specialized skills.

Vague Triggers

High

• Confidence: 98% confidence
• Finding: The trigger keywords include highly generic terms such as 'knowledge,' 'graph,' 'structured,' 'creating,' and 'bug fix,' which are common across many unrelated user requests. Combined with broad example trigger sentences, this creates a significant risk of accidental activation, misrouting user requests, and letting this skill preempt more appropriate instructions or controls.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The trigger keywords are broad, generic terms such as 'knowledge', 'graph', 'structured', and 'creating', which can match many ordinary user requests unrelated to this skill's intended job-to-be-done. This can cause accidental invocation, leading the agent to apply the wrong workflow, produce irrelevant guidance, or override a more appropriate specialized skill in security- or reliability-sensitive contexts.

Vague Triggers

Medium

• Confidence: 88% confidence
• Finding: The description says to use the skill whenever users ask for broad categories like work-productivity, ontology, typed, knowledge, or graph, or whenever they need a practical workflow, artifact, checklist, analysis, or implementation support. This activation condition is so expansive that it risks capturing a wide range of unrelated conversations, increasing the chance of unintended routing and reducing the reliability and safety of skill selection.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The skill enables implicit invocation but provides no narrowly defined trigger conditions, so the platform may activate it for loosely related requests. Because the skill description and prompt are broad workflow/productivity terms, this can cause over-selection, unexpected handling of user tasks, and unsafe delegation into a skill whose scope is not tightly bounded.

Vague Triggers

Medium

• Confidence: 88% confidence
• Finding: The default prompt uses expansive and vague wording such as work-productivity, ontology-style workflows, and practical help, without concrete boundaries. This increases the chance that unrelated or sensitive user requests are matched to the skill, leading to misrouting, overreach, and potentially unsafe behavior if the skill influences downstream actions or advice.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger sentences are broad, generic, and partially templated in a way that can match ordinary user requests unrelated to this specific skill. This can cause accidental invocation or misrouting of user intents, which is a security and safety concern because the wrong skill may handle requests outside its intended scope and produce misleading or unsafe workflow guidance.

VirusTotal

59/59 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.