Security audit
Security checks for vulnerabilities and agentic risk
This is a disclosed Kazakh script-conversion skill with expected local file and user-dictionary features, and I found no hidden network, credential, persistence, or destructive behavior.
Install only if you want a Chinese-documented Kazakh Cyrillic/Arabic conversion CLI. Treat --input, --output, and --dict paths as local filesystem access, and avoid pointing them at sensitive or unrelated files because output and dictionary operations can overwrite files.
The skill advertises file input/output and dictionary modification features but does not clearly warn that these operations read from and write to local filesystem paths. In an agent environment, this lack of disclosure increases the risk of users or orchestrators invoking the skill on sensitive files or altering persistent local data without informed consent.
The automatic trigger list includes broad phrases such as '转成阿拉伯文' and '转成西里尔文', which can match ordinary user requests outside a narrowly scoped Kazakh-conversion context. This can cause unintended skill invocation and unexpected processing of user content, especially if the skill can read files or modify dictionaries as documented elsewhere in the skill.
The manifest description is written only in Chinese, which imposes a specific language for understanding the skill's purpose without indicating any user language choice or opt-in. Under the policy, language-specific behavior or presentation can be a violation when it forces a locale or language without offering alternatives.
This code saves the user dictionary directly to the path provided by the caller, overwriting the file contents with no confirmation prompt and no warning comment/docstring explaining that the operation performs a file write. Because this is a code file, file-writing behavior should have at least some visible disclosure unless it is clearly warned elsewhere in the skill description, which is not present here.
When --output is supplied, the program writes conversion results to the specified file path without printing any notice, prompting for confirmation, or documenting the file-write side effect in nearby comments/docstrings. This is a safety-relevant file write operation in code and lacks visible disclosure to the user within the file.
No suspicious patterns detected.
