T09 · Insecure Skill Coding Practices
- Location
example.py:19- Finding
Predictable Temporary File Allows Symlink-Based File Overwrite
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent Python static-analysis skill with a few minor implementation and publishing hygiene issues, but no evidence of hidden, deceptive, destructive, or exfiltrating behavior.
Before installing, note that the skill is primarily Chinese-language and analyzes local Python files you point it at. Avoid running the included example in shared multi-user systems until its fixed /tmp/sample.py path is changed, and maintainers should pin and isolate the ClawHub CLI used for publishing.
example.py:19Predictable Temporary File Allows Symlink-Based File Overwrite
PUBLISH.md:5Unpinned Global Installation of Third-Party Publishing CLI
The skill description is written as a direct capability statement in Chinese and presents the tool as the default interaction mode without indicating that other languages are supported. Under the language/locale policy, forcing a specific language without user opt-in is a natural-language policy concern.
This markdown file contains user-facing instructions, examples, and operational guidance exclusively in Chinese. The policy requires flagging language or locale constraints when a skill forces a specific language without user opt-in, and no alternative language option or justification is provided here.
The top-level description presents the tool as a Python code analysis and optimization tool in Chinese only. This imposes a language choice in user-facing natural language without indicating that users can select another language or locale.
The module docstring is written as a Chinese-only user-facing description ('示例:使用 Code Analyzer 分析代码'), and subsequent printed labels are also Chinese. This indicates a language preference is imposed by the skill content without opt-in or justification, which matches the language/locale policy violation criteria.
Dynamic import() can load arbitrary modules at runtime, bypassing static analysis and potentially importing malicious code.
print(analyzer.generate_report(result))
print("\n" + "="*50)
print("按严重性分类的问题数量:")
print(f" P0 (必须修复): {len(result.get_by_severity(__import__('analyzer').Severity.P0))}")
print(f" P1 (重要): {len(result.get_by_severity(__import__('analyzer').Severity.P1))}")
print(f" P2 (建议): {len(result.get_by_severity(__import__('analyzer').Severity.P2))}")
Dynamic import() can load arbitrary modules at runtime, bypassing static analysis and potentially importing malicious code.
print("\n" + "="*50)
print("按严重性分类的问题数量:")
print(f" P0 (必须修复): {len(result.get_by_severity(__import__('analyzer').Severity.P0))}")
print(f" P1 (重要): {len(result.get_by_severity(__import__('analyzer').Severity.P1))}")
print(f" P2 (建议): {len(result.get_by_severity(__import__('analyzer').Severity.P2))}")
Dynamic import() can load arbitrary modules at runtime, bypassing static analysis and potentially importing malicious code.
print("按严重性分类的问题数量:")
print(f" P0 (必须修复): {len(result.get_by_severity(__import__('analyzer').Severity.P0))}")
print(f" P1 (重要): {len(result.get_by_severity(__import__('analyzer').Severity.P1))}")
print(f" P2 (建议): {len(result.get_by_severity(__import__('analyzer').Severity.P2))}")
This shell script uses Chinese for comments, status messages, prompts, and success/failure text throughout, including the user confirmation prompt. That creates a language/locale policy issue because the skill forces a specific language without user opt-in or any indication that it is intentionally limited to Chinese-speaking users.
The natural-language description and usage labels are presented only in Chinese, which effectively imposes a specific language on users without any opt-in or justification. The policy allows locale constraints when clearly documented and justified, but no such explanation appears here.
The file states all update records and linked standards references in Chinese, which indicates a fixed language choice in natural-language content. Under the policy, forcing a specific language without user opt-in can be a locale-policy violation, and no justification or alternative language option is provided here.
This markdown file contains natural-language instructions only in Chinese, which can constitute a language-policy issue when no user opt-in or alternative locale is offered. The rule for policy violations applies to all file types, and there is no indication that this locale restriction is documented as required or optional.
The description is written entirely in Chinese, which signals a language-specific skill presentation without any indication that users can choose another language or that the tool is intentionally region-specific. Under the policy, language constraints should either be optional for users or clearly justified.
The natural-language comment states '无外部依赖,仅使用 Python 标准库' in Chinese, introducing a language-specific instruction/comment without any indication that users can choose their preferred language. The policy for this audit flags language or locale constraints when they are imposed without user opt-in.