Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation workflow skill for OpenAPI and Swagger work, with no executable code, persistence, credential handling, or hidden privileged behavior found.
Before installing, be aware that this skill may activate more often than intended for broad API or developer-experience requests. It appears safe from a security perspective, but users should invoke it explicitly for OpenAPI or Swagger documentation tasks if they want predictable behavior.
The trigger sentence uses a broad natural-language phrase beginning with 'Help me', which can cause the skill to activate in situations far beyond narrowly scoped OpenAPI documentation requests. Overbroad activation increases the chance of unintended routing, prompt interception, or the skill influencing conversations outside its intended domain.
The trigger sentences are generic enough to match ordinary user requests and could cause the skill to be invoked when the user did not explicitly intend it. Unintended invocation can route conversations into this skill's workflow, increasing the chance of inappropriate behavior, prompt-scope confusion, or accidental handling of unrelated API/security-sensitive content.
The trigger phrases are broad and generic, so the skill may activate for loosely related requests and take over conversations outside its intended scope. In an agent setting, overbroad activation increases the chance of unintended behavior, irrelevant guidance, or misuse of the skill on inputs it was not designed to handle.
The skill description and usage criteria are broad enough to activate on many ordinary API-related requests, not just narrowly scoped OpenAPI documentation tasks. Over-broad routing can cause inappropriate skill invocation, increasing the chance of irrelevant guidance, prompt-scope confusion, or unintended handling of requests outside the skill’s validated boundaries.
The keyword triggers include generic terms like 'software-and-data' and 'developer experience' that are far too vague for safe routing. Such ambiguous triggers can over-match unrelated requests and cause this skill to intercept prompts it is not designed to handle, reducing reliability and potentially exposing users to unsuitable workflow advice.
The trigger keywords are broad and include generic terms like 'software-and-data', 'openapi', 'swagger', and 'rest api' without stronger scoping conditions. This can cause the skill to activate for loosely related requests, leading to inappropriate routing, irrelevant guidance, or accidental use in contexts where the skill is not the best fit.
The example trigger phrases are highly templated and generic, repeating a broad demand statement rather than showing specific user requests. This weakens activation precision and may cause the skill to match vague requests that only partially resemble the examples, increasing the chance of misfires.
The skill enables implicit invocation while using a very broad default prompt tied to common topics like OpenAPI, Swagger, API documentation, and REST APIs. This can cause the agent to invoke the skill in situations the user did not explicitly request, creating prompt-scope overreach and increasing the chance that adversarial or irrelevant content influences behavior.
The usage section provides positive trigger examples but no negative examples or exclusion conditions, so the agent lacks guidance on when not to invoke the skill. In practice, this can lead to over-triggering, collisions with other skills, and user intent being misrouted into an OpenAPI workflow when another capability would be more appropriate.
The trigger sentence is ambiguous about when the skill should activate because it describes a generic need for 'a practical workflow' without clearly limiting scope to API documentation work. This ambiguity can cause accidental activation on unrelated workflow requests, expanding the skill's reach and reducing predictability of agent behavior.
Although this is a Chinese README, key operational text and all listed trigger phrases are written in English, which can effectively impose a language expectation on users without explicit opt-in. The file does not state whether users may interact in Chinese, English, or both.
The example trigger sentences are malformed and generic, so they do not establish a clear or safe invocation pattern for the skill. Poor trigger examples make routing behavior less predictable and encourage accidental activation from loosely related prompts, though the impact is somewhat lower than the broad description and keywords themselves.
No suspicious patterns detected.
