Security audit
Security checks for vulnerabilities and agentic risk
This skill openly creates local project note files so long-running work can be resumed later, with no hidden code, network access, or background persistence found.
Install only if you want the agent to keep durable local project notes. Review the project folder path and avoid writing secrets or sensitive business details into the generated markdown files unless that local storage is acceptable.
The description says to use the skill when the user wants to 'start a long-term project,' 'continue a previous project,' or for broad domains like engineering, research, writing, planning, and operations work. These conditions are wide-ranging and lack explicit boundaries or negative examples, increasing the chance of unintended invocation for ordinary project-related requests.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
## Start a long project
When the user asks to create a long-running project or preserve context across sessions:
1. Normalize a short hyphen-case project name.
2. Create `projects/<name>/`.
The skill directs the agent to create and continuously modify files in the workspace without explicitly requiring confirmation or warning the user before durable changes are made. In practice, this can lead to unexpected filesystem writes, accidental overwrites, or persistent storage of sensitive content the user did not intend to keep.
The markdown template headings and prompts are entirely in Chinese, which imposes a specific language on skill users without offering an opt-in or alternative locale. This matches the policy category for language/locale constraints because the file provides no indication that the skill is region-specific or that another language is supported.
This markdown file explains that the skill turns work into durable project state on disk, which implies file creation and ongoing file writes. Under the markdown criteria for SQP-2, the description should include a clear user warning about modifying local files or project data, but no such warning appears.
The workflow instructs the agent to choose between a Chinese template and an English template, but it does not say to ask the user which language they want or otherwise obtain opt-in. Because language/locale constraints should be user-driven unless clearly justified, this is a natural-language policy issue.
The file path and content indicate an English-only project template, and the instructions require specific English-named files such as STATUS.md, TODO.md, and HANDOFF.md. This imposes a language convention without any user opt-in or documented justification, which matches the language/locale policy concern for natural-language content.
The template headings and field labels are entirely in Chinese, which implicitly enforces a specific language for entries. There is no surrounding note offering a language choice or explaining that the template is intended only for a Chinese-speaking or region-specific context.
The natural-language content of this handoff template is entirely in Chinese, including the core operating instructions for resuming work. Because the file does not offer a language choice or explain a justified locale constraint, it can violate the policy against forcing a specific language without user opt-in.
This log template uses Chinese section headings exclusively, which imposes a specific language on users. There is no indication that the language choice is optional or justified by a region-specific requirement.
The template is entirely written in Chinese, including headings and instructions, with no indication that another language is supported or that the Chinese-only format is required for a specific regional or compliance reason. This can violate a language/locale policy when users are not given an explicit choice or opt-in.
This markdown file uses Chinese section headings such as '关键文件' and '关键链接' without any indication that the skill is region-specific or that language selection is optional. That can conflict with a language/locale policy requiring user choice or documented justification for a fixed language.