Security audit

Openapi Docs Generator

Security checks across malware telemetry and agentic risk

Overview

This is a markdown-only OpenAPI documentation helper; its auto-trigger language is overly broad, but it does not request privileged access or perform hidden actions.

Before installing, be aware that the skill may activate for general API or documentation prompts because its triggers are broad. It appears safe from a privilege and persistence standpoint, but users who want tighter routing should invoke it explicitly or narrow the trigger language.

SkillSpector

By NVIDIA

Vulnerability Patterns

Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (9)

Vague Triggers

Medium

Confidence: 91% confidence
Finding: The trigger phrases are broad, awkwardly templated, and likely to match loosely related user requests, which can cause unintended invocation of the skill. In an agent environment, overbroad activation increases the chance that the skill engages outside its intended scope and influences responses or workflows the user did not explicitly request.

Vague Triggers

Medium

Confidence: 87% confidence
Finding: The trigger phrases are broad enough to match ordinary user requests about APIs, OpenAPI, Swagger, or documentation, which can cause the skill to activate when the user did not explicitly intend to invoke it. In an agent system, over-broad routing increases the chance of unintended prompt injection surface, incorrect tool selection, and disclosure of context to a skill that was not deliberately chosen.

Vague Triggers

Medium

Confidence: 94% confidence
Finding: The skill description activates on a very broad set of terms such as 'software-and-data' and general requests for workflows, analysis, or implementation support. This can cause the skill to be selected for unrelated requests, increasing the chance of inappropriate context injection, misleading outputs, or unintended handling of tasks outside its narrow OpenAPI scope.

Vague Triggers

Medium

Confidence: 92% confidence
Finding: The example triggers use generic phrasing like 'Help me' and 'I need a practical workflow' with only loosely attached domain text, which can match ordinary user language too broadly. Overbroad triggers increase accidental invocation and can route unrelated conversations into this skill, reducing reliability and potentially exposing users to irrelevant or incorrect guidance.

Vague Triggers

Medium

Confidence: 92% confidence
Finding: The trigger keywords are broad and include common terms like 'openapi', 'swagger', 'api documentation', and 'rest api', which can appear in many normal technical conversations. This can cause the skill to activate outside its intended scope, leading to inappropriate routing, reduced response quality, or unreviewed behavior being injected into unrelated requests.

Vague Triggers

Medium

Confidence: 89% confidence
Finding: The example trigger phrases use highly generic request patterns such as 'Help me' and 'I need a practical workflow', which overlap with ordinary user prompts. Because the examples do not clearly constrain the scope to OpenAPI-documentation tasks, they reinforce over-broad activation behavior and increase the chance of misrouting unrelated requests into this skill.

Vague Triggers

Medium

Confidence: 91% confidence
Finding: The skill enables implicit invocation but does not define narrow trigger constraints or clear guardrails for when it should be auto-selected. This can cause the agent to invoke the skill in broader contexts than intended, potentially exposing user data or influencing responses without explicit user intent.

Vague Triggers

Medium

Confidence: 93% confidence
Finding: The trigger sentence is so broad and awkwardly phrased that it could match ordinary user requests about backend help or practical workflows, causing the skill to activate outside its intended OpenAPI-documentation scope. Over-broad activation increases the chance of inappropriate routing, irrelevant instructions, or accidental application of this skill to unrelated tasks.

Vague Triggers

Medium

Confidence: 91% confidence
Finding: This activation phrase is ambiguous because 'I need a practical workflow for...' is common language that does not clearly limit use to API documentation tasks. In a skill-routing system, such ambiguity can lead to false activations and misapplication of the skill in contexts where it should not run.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.