Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-only OpenAPI helper skill with broad auto-invocation wording, but no hidden code, persistence, credential access, or destructive behavior.
Before installing, be aware that the skill may activate on broad API-related requests because implicit invocation is enabled and triggers are loose. It appears safe as a documentation helper, but maintainers should tighten activation wording to explicit OpenAPI/Swagger documentation tasks.
The trigger sentences are broad, repetitive, and weakly scoped, which can cause the skill to activate on loosely related requests rather than clear user intent. In an agent environment, unintended activation can lead to irrelevant instructions being injected into the workflow, reducing user control and increasing the chance of inappropriate tool use or confusing outputs.
This file is explicitly a Chinese-language README and presents the skill guidance in that locale without any visible opt-in, language selection, or explanation that the skill is region-specific. That can violate language or locale policy where users should be given a choice rather than having a language imposed by default.
The trigger phrases are broad, repetitive, and loosely scoped, which can cause the skill to activate on incidental mentions of OpenAPI, Swagger, or API documentation rather than an explicit user request to use this skill. In an agent ecosystem, unintended invocation can route user data or task flow into the wrong skill, leading to confusion, overreach, or unsafe downstream actions.
The skill description and usage scope are broad enough to match many normal software requests without clearly constraining when the skill should or should not activate. Overbroad routing can cause the agent to invoke this skill in unintended contexts, leading to irrelevant guidance, missed safer/specialized handling, or increased exposure to prompt-surface from unnecessary skill activation.
The trigger list includes generic keywords and lacks negative examples, which increases the chance of accidental or overly aggressive skill selection. In a multi-skill agent, ambiguous triggers can misroute unrelated requests into this skill, causing incorrect assistance and potentially bypassing more appropriate controls or domain-specific review paths.
The skill description uses broad topic terms such as software-and-data, openapi, swagger, api documentation, and rest api without meaningful narrowing conditions. This can cause the skill to activate for loosely related requests, increasing the chance of misrouting user input, overriding a better-matched skill, or exposing the user to irrelevant automated actions.
The keyword list contains several common, high-frequency technical terms that appear in many normal developer conversations. Without scope constraints, the skill may be invoked unintentionally, leading to prompt-routing errors, reduced reliability, and possible interference with more appropriate skills handling adjacent software tasks.
The skill is configured for implicit invocation while its default prompt is broad and trigger conditions are not narrowly constrained. This can cause the agent to invoke the skill in situations only loosely related to OpenAPI work, increasing the attack surface for prompt injection, unintended data exposure to the skill context, or user-confusing autonomous behavior.
The trigger sentence is phrased so broadly and awkwardly that it can match ordinary help-seeking language instead of a clearly scoped OpenAPI-documentation request. This can cause the skill to activate unexpectedly, injecting irrelevant workflow steps or overriding a more appropriate skill, which becomes a security and reliability concern in agent routing.
This trigger lacks clear activation boundaries and does not specify the concrete conditions under which the skill should run. In an agentic system, ambiguous routing rules increase the chance of misfires, where unrelated user prompts are captured by this skill and produce incorrect or overbroad outputs, potentially interfering with safer or more relevant handling.
The file lists English and Chinese variants, but the user-facing documentation does not state how the skill chooses a language or whether the user can opt in to a preferred locale. That can create an implicit language/locale behavior without documented user choice, which falls under natural-language policy concerns.
The example triggers rely on generic helper phrases and only demonstrate positive matches, with no non-trigger examples to define boundaries. This encourages overbroad invocation behavior and makes it harder for routing systems or maintainers to distinguish when the skill should not run.
No suspicious patterns detected.
