Security audit
Security checks for vulnerabilities and agentic risk
This is a straightforward Bing web-search helper that sends search terms to Bing and returns JSON results, with no persistence or credential handling.
Install only if you are comfortable with your search terms being sent to Bing. The skill appears benign, but the author-local command path may need correction after installation and users should avoid putting secrets, private documents, or sensitive personal details into search queries.
The skill invokes a Python script that performs web search, which implies outbound network access, but the manifest does not declare any corresponding tool scope or permissions. This weakens least-privilege controls and reduces transparency for reviewers and runtime policy systems, making unintended or unauthorized network use harder to detect and constrain.
The trigger conditions are broad enough to match many generic requests such as finding information or searching the web, which can cause the skill to activate more often than users expect. Overbroad activation increases the chance of unnecessary network calls, data exposure through search queries, and accidental delegation of general tasks to a tool with external side effects.
The natural-language description and usage guidance are entirely in Chinese, while the skill claims to support both Chinese and English search. There is no statement that the language is user-selectable or that the Chinese-only presentation is an intentional, justified locale constraint.
The manifest description is written entirely in Chinese, which imposes a specific language presentation without offering the user any language or locale choice. This can violate language/locale policy when the skill is intended for general use rather than a clearly documented region-specific audience.
The script sends the user’s raw search query to Bing, an արտաքին third-party service, without any in-code disclosure, consent flow, or warning about data sharing. Because search terms can contain sensitive information, this creates a real privacy risk through unintended transmission of user data to an external provider.
The request hard-codes the Accept-Language header to en-US/en, which imposes a language/locale preference regardless of user settings. There is no indication that the user can opt in to this locale choice or that the restriction is required for a documented regional purpose.
