Openapi Docs Generator

• Outcome: Pass
• Latest audit: Jul 13, 2026 · 1:08 PM UTC
• Version: 0.1.1

Overview

This is a documentation-only OpenAPI/Swagger helper skill with no executable code, credential handling, persistence, or hidden data flow.

Install only if you want an agent helper for OpenAPI/Swagger REST API documentation. Be aware it may activate on some broad API or developer-experience prompts, so review whether it is the right skill when your request is only general backend work rather than API documentation.

SkillSpector

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: 90% confidence
• Finding: The trigger sentences are broad, repetitive, and partially malformed, which increases the chance that the skill is invoked for loosely related requests rather than explicit user intent. In an agent environment, unintended invocation can cause the model to follow the wrong workflow, produce irrelevant outputs, or expose users to unnecessary prompt/context handling they did not ask for.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The trigger phrases are so generic that the skill may activate on loosely related requests, causing it to handle prompts outside its intended scope. In an agent environment, over-broad activation increases the chance of prompt hijacking, unintended tool usage, or inappropriate application of the skill to sensitive API/documentation tasks.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The skill description says to use the skill for broad categories like software-and-data, openapi, swagger, api documentation, and rest api, which are common topics across many unrelated requests. This can cause over-triggering, routing users into this skill when they did not ask for documentation generation or validation, increasing the chance of irrelevant actions or unsafe context mixing.

Vague Triggers

Medium

• Confidence: 96% confidence
• Finding: The listed trigger keywords are generic technical terms that appear in many normal engineering conversations, not only in requests that need this specific skill. Because activation is scoped by broad keywords rather than a clear user intent, the skill may be invoked unexpectedly and produce off-target guidance or interfere with more appropriate tooling.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The example trigger phrases use very common wording such as 'Help me' and 'I need a practical workflow', which overlaps heavily with ordinary user requests. These examples encourage permissive matching behavior, making accidental invocation more likely and reducing confidence that the skill is being applied only when the user explicitly wants OpenAPI/Swagger documentation help.

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The default prompt is overly broad and reads like a generic everyday request fragment rather than a narrowly scoped invocation trigger. Combined with `allow_implicit_invocation: true`, this can cause the skill to activate in situations where the user did not clearly intend to use it, increasing the chance of prompt-routing mistakes, unintended tool use, or exposure of user context to the skill.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger sentence is so broad and generic that normal user phrasing could activate the skill unintentionally, causing it to handle requests outside a clearly bounded scope. In an agent environment, overbroad activation increases prompt-routing risk and can expose users to irrelevant or lower-quality automated behavior without clear consent.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The activation phrase 'Use $openapi-docs-generator to handle ...' is ambiguous about when the skill should be invoked and does not clearly constrain scope beyond a long requirement fragment. Ambiguous routing language can lead to accidental or inappropriate invocation, especially when users mention similar concepts casually or in mixed-context requests.

Static analysis

No suspicious patterns detected.