Openapi Docs Generator

• Outcome: Pass
• Latest audit: Jun 20, 2026 at 7:38 PM UTC
• Version:
  0.1.0

Overview

This is a low-risk OpenAPI documentation helper with overly broad activation wording but no executable code, credential access, persistence, or destructive behavior.

Install only if you want a documentation-focused helper for OpenAPI or Swagger work. Be aware it may activate on broader API-related requests because its triggers are loose; review outputs before using them as authoritative API contracts.

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

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The trigger phrases are broad, awkwardly templated, and likely to match loosely related requests, which can cause unintended invocation of the skill outside the user's actual intent. In an agent ecosystem, accidental routing to the wrong skill can expose unrelated user input to unnecessary processing and produce misleading or unsafe outputs, even though this file does not itself contain code execution.

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The skill description and activation guidance are broad enough to match generic software or data requests that only loosely relate to OpenAPI generation. Over-broad activation can cause the wrong skill to engage, leading to scope confusion, unsafe assumptions, or inappropriate handling of user input in contexts where more specialized safeguards should apply.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The listed trigger keywords include generic terms such as 'software-and-data' and 'developer experience', which can match many unrelated requests. This increases the chance of unintended activation, causing the assistant to apply this skill outside its intended domain and potentially produce misleading or lower-safety guidance.

Vague Triggers

Medium

• Confidence: 85% confidence
• Finding: The skill description and usage scope are broad enough to overlap with many routine technical conversations about APIs, Swagger, or developer experience. This can cause the skill to activate when the user did not actually request OpenAPI-documentation help, leading to inappropriate context injection, irrelevant actions, or interference with more suitable skills.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The keyword list is generic and lacks boundary conditions, so common phrases like 'openapi', 'swagger', 'rest api', or 'developer experience' may trigger the skill outside its intended purpose. In an agent environment, ambiguous triggering can route user requests to the wrong skill, increasing the chance of irrelevant guidance, policy bypass via misrouting, or unintended processing of user data in the wrong context.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The default prompt is extremely broad and maps to generic software/API documentation requests without meaningful boundaries, which can cause the skill to activate in contexts the user did not explicitly intend. In combination with implicit invocation, this increases the risk of prompt/skill hijacking, unintended data exposure to the skill context, or overreach into adjacent tasks.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: Enabling implicit invocation without a tightly scoped trigger definition allows the platform to invoke this skill automatically for a wide range of loosely related requests. Because this skill concerns common developer topics like APIs and documentation, the broad scope makes unintended activation more likely and can route unrelated user content into the skill unnecessarily.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The trigger sentences are overly broad and malformed, including generic phrasing like 'Help me' and 'I need a practical workflow' tied to a long requirement fragment. This can cause the skill to activate for unrelated user requests, leading to unintended context injection or misrouting of conversations into this skill when the user did not actually ask for OpenAPI documentation help.

VirusTotal

63/63 vendors flagged this skill as clean.