Work Productivity Ontology Typed Workflow Helper

• Outcome: Pass
• Latest audit: Jul 29, 2026 · 4:45 AM UTC
• Version: 0.20260729.110214

Overview

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

Install only if you want a general ontology/workflow productivity helper. Be aware it may activate for broad workflow or knowledge-graph-related requests, so explicit invocation or tighter trigger wording would make its behavior more predictable.

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

Vague Triggers

Medium

• Confidence: 95% confidence
• Finding: The trigger phrases are broad enough to match many ordinary user requests that are not clearly scoped to this skill, which can cause unintended invocation or routing. In an agent ecosystem, ambiguous activation increases the chance the skill is selected in the wrong context, leading to irrelevant actions, workflow confusion, or unsafe application of ontology/knowledge-graph guidance where it was not requested.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The trigger phrases are broad enough to match common, non-specific user requests such as asking for a practical workflow or general help. This can cause unintended skill activation, leading the agent to apply this skill outside its intended scope and potentially override more appropriate safeguards or workflows.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The skill description and usage guidance are broad enough to match many ordinary requests unrelated to a narrowly defined ontology workflow helper. In agentic systems, overly broad triggers can cause accidental invocation, context hijacking, or routing sensitive user tasks into the wrong skill, which may lead to inappropriate actions or unsafe assumptions.

Vague Triggers

High

• Confidence: 97% confidence
• Finding: The keyword list includes highly generic terms like 'typed', 'knowledge', 'graph', 'structured', 'creating', and 'bug fix', which are common across many unrelated tasks. This materially increases false-positive activation risk, allowing the skill to intercept broad user requests and potentially override more appropriate, safer, or specialized workflows.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The example trigger phrases use generic lead-ins such as 'Help me' and 'I need a practical workflow', making it unclear when the skill should or should not be invoked. In practice, these examples train matching systems and users toward vague activation patterns, which can broaden routing beyond intended boundaries and increase unintended tool use.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The trigger keywords are broad and include generic terms like "knowledge", "graph", "structured", and "creating", which can overlap with many unrelated user requests. In an agent system that auto-selects skills from natural language, this increases the chance of accidental activation, causing the agent to apply the wrong workflow or expose irrelevant instructions in contexts where they do not fit.

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The applicability description says to use the skill for broad topic areas and practical support needs, but it does not clearly define boundaries or exclusions. That ambiguity can lead routing logic or human operators to invoke the skill for loosely related tasks, increasing misapplication risk and reducing predictability of agent behavior.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The default prompt is overly broad and maps to generic productivity, workflow, checklist, analysis, and implementation requests. Combined with the skill’s ontology/workflow framing, this can cause unintended activation on ordinary user queries, expanding the skill’s influence beyond explicit user intent and increasing the chance of prompt-scope confusion or misuse.

Vague Triggers

Medium

• Confidence: 95% confidence
• Finding: Enabling implicit invocation without clear trigger constraints allows the platform to auto-select this skill for loosely related requests. Because the skill description and prompt are broad, implicit invocation materially increases the likelihood of accidental routing, unexpected behavior, and unauthorized expansion of the skill into contexts the user did not clearly request.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger sentence begins with a very common phrase ('Help me') followed by requirement text, making accidental invocation plausible in normal user conversations. In agent systems that auto-route by trigger matching, this can cause the wrong skill to activate, leading to confused task execution, disclosure of irrelevant context, or bypass of a more appropriate/specialized workflow.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The trigger uses a generic request form ('I need a practical workflow for ...') that is common across many benign tasks and lacks strong domain-specific anchors. This increases false activations and misrouting risk, especially because the skill is broadly framed around productivity, ontology, typed knowledge, and implementation support, which already spans many ordinary requests.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.