Security audit
Security checks for vulnerabilities and agentic risk
This skill mostly matches its interior-design purpose, but it asks for broad command/file authority and enterprise token use with unclear activation rules and unsafe credential examples.
Review this before installing if you will use real Kujiale enterprise credentials. Keep tokens out of repo-tracked config files, require explicit confirmation before running referenced scripts or approving/submitting team changes, and use restricted output directories for generated renders and reports.
The skill first instructs users to place a long-lived access_token directly into .kjlconfig.json, then later advises using environment variables or a secret manager instead. This contradiction can lead users to persist sensitive credentials in local files that may be committed, copied, or exposed through workspace access, logs, backups, or shared project archives.
The trigger condition section is malformed and vague, so an agent may not know when the skill should or should not activate. Ambiguous activation criteria increase the chance of inappropriate execution of exec/write-capable workflows in unrelated contexts, which can cause unintended file changes, external calls, or handling of sensitive inputs without clear user intent.
The skill documents export, save, and configuration-writing behavior while exposing read, write, and exec tools, but it does not place a clear warning or consent checkpoint next to those operations. In an agent setting, this can normalize state-changing actions and lead to accidental overwrites, unsafe file creation, or persistence of sensitive data without the user fully understanding the consequences.
No suspicious patterns detected.
