Security audit
Security checks for vulnerabilities and agentic risk
This skill is a backend interview coach that stores limited local practice progress and uses optional CV input, with no evidence of hidden network, destructive, or privileged behavior.
Install this if you want a backend interview practice assistant that keeps local progress files. Be aware it may activate on broad phrases like "system design" unless your request is clearly outside backend topics, and only provide CV files you intend it to read and summarize into its local profile data.
The trigger phrase "design interview" is broad enough to activate on requests outside backend scope, causing the skill to take over conversations it was not intended to handle. In an agent environment, overly broad activation can lead to incorrect tool use, irrelevant persistence, or mishandling of user data under the wrong skill context.
The phrase "Rate my solution" is generic and could match many unrelated tasks, leading the skill to activate on non-backend content. This increases the risk of context confusion, accidental file handling, and storing interview-related state for requests that do not belong to this skill.
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.
On first message, ensure data directory exists:
mkdir -p ~/.openclaw/backend-interview-simulator
Initialize (create if missing) using these shapes:
The standalone trigger "system design" lacks a backend qualifier, so the skill may activate for frontend, product, hardware, or general architecture discussions. Misrouting requests to this skill can cause inappropriate questioning, faulty guidance, or unnecessary local persistence under an incorrect user workflow.
Lines L078-L080 state that storage should be limited to ~/.openclaw/backend-interview-simulator/ only. However, L230 instructs the skill to back up a corrupted file without specifying that the backup must remain in that same directory, which weakly contradicts the earlier documented storage boundary.
No suspicious patterns detected.