Security audit
Security checks for vulnerabilities and agentic risk
This is a read-only skill reviewer whose behavior matches its stated purpose, with some broad trigger wording but no hidden mutation, credential access, network use, persistence, or target-code execution found.
Install only if you want an agent to inspect skill packages or SKILL.md content for review. When using it manually, run its bundled scripts from this skill package, not scripts from the package being reviewed, and expect some Chinese-first output from the command-line helpers.
声明描述的核心能力是评估 Skill 的质量并自动评分，但给出的代码片段只是在本地检查 Python 运行环境是否满足最低版本要求。虽然环境检查可能是某个更大系统的辅助组件，但就该代码片段本身而言，其实际行为与声明的主要用途明显不一致。代码没有读取或分析 Skill 包、SKILL.md，也没有执行任何审查、评分、诊断逻辑，因此应判定为描述与行为不匹配。
The activation rule is overly broad and tells the agent to proactively use the skill for loosely defined requests about evaluating skills. Over-broad triggering can cause the skill to activate in unintended contexts, increasing the chance of unsafe file access, mis-scoped analysis, or accidental processing of adversarial content without clear user intent.
The skill claims the audited package is treated as untrusted and that review is read-only, yet it instructs running a Python script from the target skill directory. That creates a code-execution path on attacker-controlled content, enabling arbitrary code execution, data exfiltration, or environment tampering under the guise of analysis.
Treating 'simply providing a SKILL.md' as sufficient to trigger the skill is ambiguous and unsafe because the presence of a file alone does not prove the user wants a security or quality review. This can lead to unsolicited processing of content, accidental override of other more appropriate skills, and increased exposure to prompt-injection content embedded in documents.
Treating 'simply providing a SKILL.md' as sufficient to trigger the skill is ambiguous and unsafe because the presence of a file alone does not prove the user wants a security or quality review. This can lead to unsolicited processing of content, accidental override of other more appropriate skills, and increased exposure to prompt-injection content embedded in documents.
Without declared permissions the skill's intent is opaque and cannot be validated.
The natural-language instructions embed bilingual behavior in the core description, but do not state whether output language should follow the user's preference or provide an opt-in choice. This can violate language or locale policy expectations when a skill imposes or defaults to a language format without user selection.
The docstring and user-facing print messages are entirely in Chinese, which imposes a specific language on users without any opt-in or fallback. Under the policy, hard-coded locale/language restrictions should be flagged unless the file clearly justifies the constraint or offers a choice.
The module docstring presents the script description, usage, output, and behavior entirely in Chinese, and the runtime messages printed to users are also Chinese-only. For a general-purpose skill utility, this is a natural-language locale constraint without any opt-in or documented justification.
The printed status, failure, usage, and error messages shown during execution are all hardcoded in Chinese. This continues the fixed-language behavior without user opt-in or a stated regional/compliance reason.
