Opportunity Intelligence Engine

• Outcome: Pass
• Latest audit: May 29, 2026, 8:36 PM
• Version:
  1.0.0

Overview

This is an instruction-only business planning skill with broad activation wording, but it does not install code, access data, use credentials, or take actions on the user's behalf.

Install this only if you want the agent to steer idea, prioritization, and growth questions toward ROI and monetization advice. Treat outputs as brainstorming rather than financial guidance, and avoid sharing private business details unless you are comfortable using them in planning prompts.

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

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The trigger conditions for the Opportunity Intelligence Engine are broad enough to match many ordinary conversations about ideas, money, focus, or prioritization. This can cause unintended activation of the skill, overriding a more appropriate skill or workflow and leading to misrouting of user requests, especially because the skill is oriented toward rapid monetization and action.

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The Leverage Multiplier Engine uses vague trigger terms like wanting to grow, scale, or get more out of something, which are common across many benign requests. That makes accidental invocation likely, potentially causing the system to produce monetization or distribution strategies when the user intended simpler analysis or unrelated assistance.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The duplicated Opportunity Intelligence trigger repeats the same overly broad activation logic, increasing the chance of unintended matches and inconsistent routing behavior. Duplication also raises maintenance risk, because future changes may be applied to one copy but not the other, compounding misfires and making the system harder to reason about securely.

VirusTotal

65/65 vendors flagged this skill as clean.