Security audit

Openapi Docs Generator

Security checks for vulnerabilities and agentic risk

Overview

This skill is a documentation workflow helper for OpenAPI/Swagger tasks and does not include code, credential handling, persistence, or destructive behavior.

Install this only if you want automatic help with OpenAPI or Swagger documentation. Be aware that its triggers are broad and implicit invocation is enabled, so users may prefer to invoke it explicitly with $openapi-docs-generator for OpenAPI/Swagger tasks.

A.I.G

Vulnerability Patterns

Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
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 (14)

Vague Triggers

High

Category: Not specified by scanner
Confidence: 98% confidence
Finding: The trigger phrase at this line is so broad and awkwardly templated that it can match routine user language unrelated to an explicit request to invoke the skill. In an agent system, overly broad activation increases the chance of unintended skill invocation, which can route user data or workflow control into the wrong tool and cause confused-deputy behavior or policy bypass in multi-skill environments.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The README defines trigger sentences, but they are malformed and do not clearly delimit when the skill should activate. Phrases beginning with "Help me" and "I need" overlap with common everyday speech, which increases the risk of unintended invocation and provides no negative examples or scope constraints.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The trigger phrases are extremely broad and generic, including common help-seeking language such as 'Help me' and 'I need a practical workflow,' which can cause the skill to activate unintentionally for loosely related requests. In an agent ecosystem, overbroad activation increases the chance of misrouting user requests, unexpected tool use, and privilege or context expansion beyond what the user actually intended.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The skill description is broad enough to match many ordinary software requests involving APIs, documentation, or implementation support, which can cause the skill to activate outside its intended scope. Over-broad activation increases the chance of misrouting user requests, unintended tool behavior, or unnecessary exposure to any downstream instructions the skill may contain.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The trigger keywords include generic phrases like 'software-and-data', 'api documentation', and 'developer experience', which are likely to overlap with many unrelated engineering tasks. This broad collision surface can lead to accidental invocation of the skill, making routing less predictable and potentially applying the wrong workflow or instructions to user requests.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The activation description is broad and loosely bounded, covering generic software-and-data and API-related requests without strong disambiguation. This can cause the skill to trigger on ordinary conversations and route users into an irrelevant workflow, increasing the chance of context hijacking or unintended instruction application.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 91% confidence
Finding: The example trigger phrases begin with highly generic language such as 'Help me' and 'I need a practical workflow,' which overlaps heavily with normal user phrasing. Because the examples are not specific enough, they may train or encourage overbroad activation behavior, causing the skill to intercept unrelated requests.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 89% confidence
Finding: The default prompt uses broad helper language instead of narrowly scoped task criteria, making it more likely to match ordinary software-help requests that are not specifically about generating or validating OpenAPI documentation. In combination with implicit invocation, this broad phrasing increases accidental activation risk and can override more appropriate skills or expected agent behavior.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 94% confidence
Finding: The skill enables implicit invocation without any visible trigger constraints, which increases the chance the agent will call this skill on loosely related requests. That can cause unintended routing, prompt-scope expansion, or misuse of the skill in contexts the user did not clearly request, especially because the description is broad and workflow-oriented.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The activation examples are ambiguous because they describe the requirement text itself rather than clear user intents, making invocation scope poorly bounded. This can cause accidental activation from partial phrase overlap or prompt-injection-style steering where an attacker embeds the example text to force this skill to run when another tool or no tool should be selected.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 82% confidence
Finding: The file lists separate English and Chinese instruction and guide files, but the README does not state how the user's preferred language is selected. This can create a locale-policy concern if the skill defaults to a language without explicit user choice.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 88% confidence
Finding: This is a zh-CN README, but key descriptive and trigger content is presented in English without any note that the user can choose language or that English is required. That can amount to forcing a specific language experience in a locale-specific document without opt-in.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 94% confidence
Finding: The activation examples in this Chinese README are entirely English, which imposes a language-specific usage pattern on users of a locale-specific document. There is no indication that Chinese trigger phrases are also supported or that English is optional.
Content: No source excerpt is available for this finding.

Vague Triggers

Low

Category: Not specified by scanner
Confidence: 92% confidence
Finding: The example trigger sentences are malformed and truncated, so they do not clearly communicate when the skill should or should not activate. Ambiguous examples weaken operator understanding and can contribute to misconfiguration, accidental invocation, or inconsistent routing behavior.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.