Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation helper for OpenAPI/Swagger work, with no executable code, persistence, credential handling, or hidden high-impact behavior found.
Installers should know this skill may be selected more broadly than ideal for general API-documentation conversations. Review the trigger wording if precise routing matters, but no malicious or high-impact behavior was found in the inspected artifacts.
The trigger sentences are generic and weakly scoped, making it easier for the skill to activate on loosely related requests rather than explicit OpenAPI documentation tasks. In an agent environment, overbroad activation can cause unintended routing, irrelevant actions, or accidental exposure of user context to a skill that was not intentionally selected.
The trigger phrases are broad, generic, and partially malformed, making it easy for unrelated user requests to accidentally invoke this skill. Unintended invocation can cause the agent to apply the wrong workflow, over-collect context, or generate documentation-related outputs in situations where the user did not actually request this capability.
The description activates on a broad set of terms such as 'software-and-data' and general documentation/help requests, which can cause the skill to trigger outside narrowly intended OpenAPI documentation scenarios. Over-broad routing is dangerous because it can misapply this skill in unrelated contexts, leading to irrelevant guidance, instruction conflicts, or accidental overshadowing of more appropriate skills.
The example trigger phrases use generic formulations like 'Help me' and 'I need a practical workflow' that are weakly constrained and may match many ordinary requests. This increases the chance of unintended invocation, reducing routing precision and potentially diverting users into an inapplicable skill.
The skill description and usage condition are broad enough to match many ordinary conversations about software, APIs, or documentation, which can cause the skill to activate outside its intended scope. Overbroad activation is dangerous because it can unexpectedly steer agent behavior, override more appropriate skills, or cause unneeded processing on unrelated user requests.
The keyword triggers are highly generic terms like 'openapi', 'swagger', 'api documentation', and 'rest api' without contextual gating. This increases the chance of accidental invocation during routine technical discussion, which may lead to incorrect workflow selection, irrelevant instructions, or prompt-routing instability.
The skill enables implicit invocation while advertising a very broad trigger surface around common API documentation tasks. That can cause the agent to invoke this skill in situations the user did not explicitly request, increasing the chance of unintended data exposure, overreach, or workflow hijacking if the skill later gains broader capabilities or handles sensitive API specifications.
The trigger sentence is so generic that normal user phrasing could unintentionally activate this skill outside its intended scope. That creates routing ambiguity and can cause the wrong skill to handle requests, leading to irrelevant guidance, prompt-scope confusion, or easier exploitation by adversarial phrasing that forces invocation.
This activation text lacks clear boundaries for when the skill should or should not run, so unrelated documentation or backend-help requests may match. In a multi-skill system, ambiguous activation increases accidental invocation and can be abused to steer requests into a tool or workflow the user did not actually intend.
L46-L50 的示例触发句含有截断和不自然表述，未能清楚展示什么样的用户输入应当触发，且没有任何不应触发的示例。示例质量不足会进一步加剧触发条件的歧义。
