Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-only AstrBot plugin-development skill with purpose-aligned examples and no hidden execution, exfiltration, or destructive behavior found.
This skill is reasonable to install for AstrBot plugin development. When using it to generate real plugins, review any features involving API keys, persistent storage, LLM hooks, proactive messages, platform-specific APIs, or agent loops, and make sure those behaviors are user-requested and documented in the plugin README/config.
The example modifies the system prompt with the instruction '请保持简洁。', which forces Chinese-language behavior in an LLM interaction. There is no indication that this is optional, user-selected, or justified as a region-specific requirement, so it appears to impose a language preference unilaterally.
This markdown file documents storing event.unified_msg_origin and later using it to send proactive messages, but it does not warn users that subscription state/session identifiers may be persisted or that the skill can message them later without a new prompt. Because markdown files should disclose behaviors affecting privacy or user experience, this omission qualifies as a missing user warning.
The checklist requires specific Chinese phrases for the issue title and declaration statements, which imposes a language/locale requirement in natural-language instructions. The file does not offer an alternative language option or explain that this requirement is limited to a region-specific workflow, so it fits the language-policy violation category.
This markdown file includes user-facing natural-language content in Chinese within otherwise English documentation, such as the hint text example. The file does not state that the document is intended for Chinese-speaking users only or offer any language/locale choice, which can conflict with language/locale policy requirements.
The example response string 请求失败，请稍后再试。 presents a fixed Chinese-language user message with no indication that language is configurable or chosen by the user. This can violate a language/locale policy when the skill guidance is otherwise general-purpose and not documented as region-specific.
The example metadata uses a Chinese-only description value (desc: 一个示例插件). In a policy-sensitive context, this can be read as prescribing a specific language for plugin metadata without offering a choice or explaining that the example is locale-specific.
