T09 · Insecure Skill Coding Practices
- Location
SKILL.md:37- Finding
Persistent plaintext storage of LLM API credentials in browser localStorage
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly coherent for a browser-based ASMR generator, but it asks users to store an LLM API key in browser localStorage, which deserves review before installation.
Review this skill before installing if you plan to use the LLM feature. Use a restricted, low-quota, revocable API key, avoid entering a primary provider key, and clear browser storage when done. If running the local server, bind it to localhost only, for example with --bind 127.0.0.1, and do not serve directories containing secrets.
SKILL.md:37Persistent plaintext storage of LLM API credentials in browser localStorage
SKILL.md:46Documented development server command exposes the served directory on network interfaces
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The skill name, description, and usage content are presented bilingually in Chinese and English, but the natural-language control feature does not state that users may choose their preferred language or locale. Because the policy requires avoiding forced language or locale behavior without opt-in or justification, this is a mild natural-language policy concern.
The natural-language content in the changelog is presented bilingually in Chinese and English across multiple entries, but the file does not state whether language selection is optional or user-configurable. Under the language/locale policy rule, forcing or assuming a language without opt-in can be a policy concern, even in descriptive metadata.