Openapi Docs Generator

• Outcome: Pass
• Latest audit: Jul 29, 2026 · 9:06 AM UTC
• Version: 0.20260729.110214

Overview

This is a low-risk documentation helper for OpenAPI and Swagger work, with some sloppy trigger wording but no hidden execution or data access behavior.

Install this if you want help with OpenAPI or Swagger documentation. Be aware it may activate on broad API-related prompts because its trigger wording is loose, so users should explicitly invoke or dismiss it when the task is not API documentation work.

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

Vague Triggers

Medium

• Confidence: 88% confidence
• Finding: The trigger sentences are broad, repetitive, and partially malformed, which increases the chance that the skill activates for loosely related prompts rather than explicit user intent. In an agent setting, overbroad activation can cause unintended invocation of this skill, leading to prompt-routing errors, irrelevant guidance, or accidental exposure of internal workflows in contexts where they were not requested.

Vague Triggers

Medium

• Confidence: 88% confidence
• Finding: The trigger phrases are broad and partially templated, which can cause the skill to activate for loosely related requests rather than explicit OpenAPI-documentation tasks. In an agent environment, over-broad activation increases the chance of unintended invocation, irrelevant guidance, or interference with a more appropriate skill, though it does not directly enable code execution or data exfiltration.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The skill description and activation guidance are broad enough that the skill may be invoked for loosely related software or API questions, not just OpenAPI documentation tasks. Over-broad routing can cause the agent to apply the wrong workflow, collect irrelevant context, or produce misleading implementation guidance, which is a security-relevant integrity issue in agent orchestration even without explicit malicious content.

Vague Triggers

Medium

• Confidence: 95% confidence
• Finding: The example trigger phrases are malformed, truncated, and overly generic, which increases the chance of accidental or inconsistent invocation by downstream routing logic or human operators. Poor trigger examples weaken boundary-setting for the skill and can lead to misclassification, causing the agent to follow this skill in contexts where its assumptions and outputs are inappropriate.

Vague Triggers

Medium

• Confidence: 87% confidence
• Finding: The trigger keywords are very broad and include common terms like 'openapi', 'swagger', 'api documentation', and 'rest api' without clear gating conditions. This can cause the skill to activate in contexts where the user did not ask for documentation-generation help, leading to incorrect routing, unintended instruction injection into unrelated tasks, or overshadowing of more appropriate skills.

Vague Triggers

Medium

• Confidence: 83% confidence
• Finding: The skill description states broad usage conditions and mixes topical keywords with vague requests for 'workflow, artifact, checklist, analysis, or implementation support' around the requirement. Because the invocation boundary is unclear, an orchestrator may select this skill for loosely related backend/API conversations, increasing the risk of prompt misrouting and unintended behavior in multi-skill environments.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The skill enables implicit invocation while using a very broad description and default prompt centered on common software topics like OpenAPI, Swagger, API documentation, and REST APIs. This can cause the agent to invoke the skill in contexts where the user's intent is ambiguous, creating prompt-routing risk, unnecessary exposure of skill behavior, and opportunities for adversarial or irrelevant activation.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The trigger sentence begins with a very broad everyday phrase ('Help me ...'), which can cause the skill to activate on generic user requests that are not specifically about OpenAPI or Swagger documentation. Overbroad activation increases the chance of unintended routing, where unrelated prompts are handled by this skill and may produce irrelevant or misleading documentation-oriented outputs.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: These trigger sentences are ambiguous and do not impose clear scope constraints, so the skill may match loosely related requests whenever a user asks for a 'practical workflow' or uses the skill name without sufficient context. In an agentic system, ambiguous routing can misfire tool selection, leading to inappropriate execution paths or user confusion.

VirusTotal

60/60 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.