Security audit
Security checks for vulnerabilities and agentic risk
This skill is mostly a local encoding and format-conversion guide, but it also asks for API credentials and includes remote-request guidance that is not clearly scoped to its purpose.
Review this skill before installing. Its local encoding and conversion examples are mostly ordinary, but do not provide API keys or credentials unless you know which service is being used and why. Avoid sending sensitive tokens, JWTs, file contents, or query parameters to remote endpoints, and check output paths before running commands that write or edit files.
The skill is described as a local encoding/format conversion tool, yet its documentation introduces external API use and API key setup. This mismatch can mislead an agent or user into granting unnecessary secrets or enabling network-capable behavior that is outside the stated purpose, increasing the chance of secret exposure and unsafe execution paths.
The examples and troubleshooting include network/API operations such as authenticated/API-style failure modes and a curl request, which contradict the skill's stated local data-conversion purpose. In an agent setting, such contradictory guidance can normalize unnecessary outbound requests and encourage users to send potentially sensitive input to external endpoints.
The example performs an outbound HTTP request to an external domain, which is a real external transmission path. In the context of a skill marketed as local encoding/format conversion, this is more dangerous because users may not expect data to leave the environment, making accidental disclosure of tokens, queries, or other sensitive input more likely.
curl -G --data-urlencode "q=hello world & more" https://api.example.com/search
# 正确编码空格和特殊字符，发送HTTP GET请求
The skill documentation includes commands that write to files, such as redirecting converted output to output.txt, but the surrounding description does not explicitly warn users that local files may be created or overwritten. Because SQP-2 applies to markdown files when behaviors could affect user data or system integrity, this omission is worth flagging.
The markdown includes a network request example without an explicit warning that query contents will be transmitted off-host. Even though the endpoint is an example domain, the pattern can cause users or agents to treat external transmission as routine and accidentally send sensitive data in real usage.
No suspicious patterns detected.