ClawHub
Back to skill

Security audit

Openapi Docs Generator

Security checks for vulnerabilities and agentic risk

Overview

This skill is a documentation helper for OpenAPI/Swagger work and does not contain code, persistence, credential handling, or hidden high-impact behavior.

Install this if you want an OpenAPI/Swagger documentation workflow helper. Be aware that its broad trigger terms may activate it for some general API documentation conversations, so prefer explicit prompts when you want or do not want this skill used.

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
  • 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 (10)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger phrases are generic and template-like enough that they could cause the skill to be invoked in situations where a user did not explicitly intend to request this specific capability. In an agent ecosystem, unintended invocation can route user data or workflow control to the wrong skill, producing incorrect outputs, privacy exposure, or policy bypass through misclassification of user intent.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The trigger phrases are broad enough to activate on common requests about software, APIs, or documentation without clear scoping or user confirmation. In an agent environment, this can cause unintended skill invocation, leading the system to apply this workflow in contexts the user did not explicitly request, which increases the risk of prompt/behavior hijacking or inappropriate task handling.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill description is scoped to broadly relevant terms like 'openapi', 'swagger', 'api documentation', and 'rest api', which can cause the router to invoke this skill for many generic API-help requests outside its specific intended workflow. This is not code-execution dangerous, but it can misroute users into an overly specialized or irrelevant skill, reducing reliability and potentially crowding out better-matched skills.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The example trigger phrases use generic conversational wording like 'Help me' and 'I need a practical workflow' combined with a broad requirement statement, which increases the chance of accidental activation from ordinary user requests. In a skill-routing system, overly generic examples can bias selection and create prompt-squatting behavior, where this skill captures traffic meant for other API or software assistance skills.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill description and usage criteria are broad enough that the agent may invoke this skill for many general software or API-related requests, even when the user did not ask for OpenAPI documentation help specifically. Overbroad triggering can cause incorrect routing, unnecessary exposure of user context to the wrong skill, and degraded safety if downstream instructions are applied outside their intended scope.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The keyword list includes generic terms like software-and-data, openapi, swagger, api documentation, and rest api without contextual constraints, making accidental invocation likely. Because skills can shape the agent's behavior, a loosely scoped trigger increases the chance of misapplication, irrelevant instructions, or unintended processing of user requests that only mention APIs tangentially.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The default prompt uses a very broad natural-language activation phrase tied to common topics like OpenAPI, Swagger, API documentation, and REST APIs. Because implicit invocation is enabled, normal user requests in these domains could unintentionally trigger this skill, causing prompt routing confusion or untrusted skill activation without clear user intent.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The trigger sentence starts with a very broad everyday phrase ('Help me') and then appends the requirement text, which creates weak activation boundaries. In agent-routing systems, overly generic triggers can cause the skill to activate for unrelated requests, leading to misrouting, unintended disclosure of context, or execution of this skill when a more appropriate or safer skill should handle the task.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The phrase 'I need a practical workflow for ...' is vague and can match many benign or unrelated productivity requests without clearly requiring OpenAPI/Swagger intent. This ambiguity increases the chance of accidental invocation, which can degrade trust in routing and potentially expose user inputs or system behavior to the wrong skill path.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
71% confidence
Finding

This is a zh-CN README, but key user-facing sections such as the demand description, workflow description, keywords, and trigger phrases are presented in English. That creates an implicit language constraint or inconsistency without telling the user whether English is required or offering a language preference choice.

Content

No source excerpt is available for this finding.