Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-only OpenAPI helper skill with some overly broad trigger wording but no hidden execution, persistence, or data access behavior.
Installers should be aware that the skill may activate for broad OpenAPI, Swagger, REST API, or developer-experience prompts. Prefer explicit invocation when you want OpenAPI documentation help, and review generated API docs before publishing them.
The trigger phrases are broad, repetitive, and partly malformed, which can cause the skill to activate for loosely related requests rather than explicit user intent. In an agent environment, overbroad activation can route unrelated prompts into this skill, leading to inappropriate handling, unintended data exposure within the workflow, or reduced reliability of downstream actions.
The trigger phrases are extremely generic and include broad terms like 'help me' and 'I need a practical workflow,' which can cause the skill to activate in contexts where the user did not explicitly intend to use it. In an agentic system, ambiguous invocation increases the risk of inappropriate routing, unintended processing of user data, or bypass of more suitable safety-checked workflows.
The skill description uses very broad activation criteria such as general API-documentation terms and 'implementation support,' which can cause the skill to trigger in situations outside its intended scope. Over-broad routing can lead to incorrect delegation, reduced reliability, and accidental application of the skill to unrelated requests, which is a security-relevant policy/scope issue even if it does not directly execute harmful actions.
The keyword list includes broad terms like 'openapi,' 'swagger,' and 'developer experience,' which may overlap with many unrelated developer tasks. This increases the chance of false activation and misrouting, potentially causing the assistant to provide mismatched guidance or expose users to workflows not intended for their request.
The skill description includes broad domain terms such as software-and-data, openapi, swagger, api documentation, and rest api without strong narrowing conditions. This can cause the skill to be invoked in loosely related conversations, leading to misrouting or over-triggering, though the content itself is not directly harmful.
The trigger section lists generic keywords and example phrases but does not define scope boundaries or negative conditions. An attacker or even normal users could accidentally trigger this skill in unrelated API or developer-experience contexts, reducing reliability and potentially surfacing irrelevant instructions.
The default prompt contains a very broad natural-language trigger phrase ('Use $openapi-docs-generator to help me ...') combined with implicit invocation, which increases the chance the skill is activated in loosely related conversations. That can cause unintended routing of user requests to this skill, expanding its influence beyond clear OpenAPI-documentation tasks and increasing prompt-injection or misuse exposure.
The trigger descriptions are ambiguous and do not define clear boundaries for when the skill should or should not activate. In an agent environment, ambiguous routing conditions can cause over-selection of the skill, exposing unrelated user inputs to documentation-generation instructions and increasing the risk of incorrect actions or prompt injection chaining.
The trigger sentence is excessively broad and can match generic user phrasing rather than a clearly scoped request for OpenAPI documentation help. This increases the chance of unintended skill activation, which can route unrelated conversations into this skill and create prompt-scope confusion or instruction interference.
The file lists English and Chinese instruction and guide files, but does not state how the user's preferred language is selected or whether language choice is optional. This can create a locale-policy concern because the skill's language behavior is implied rather than explicitly user-driven.
This Chinese-language README contains core operational content and trigger phrases primarily in English, but it does not state whether users may choose their preferred language or whether English is required. That can create an implicit language constraint without user opt-in.
The example trigger phrases are malformed and truncated, so they do not establish clear activation boundaries for when the skill should be used. Ambiguous examples can reinforce inconsistent routing behavior and make it harder to distinguish intended use from accidental invocation.
No suspicious patterns detected.
