do e2e tests, run e2e, test on Daytona, run Electron on Daytona, validate feature, real desktop flow, CDP/noVNC, PR proof. Launch and drive OpenWork Electron in Daytona with validated frame evidence.
56
66%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./.opencode/skills/daytona-electron-test/SKILL.mdSecurity
2 findings: 1 high severity, 1 medium severity. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill includes instructions and example commands that require embedding API keys, passwords, or other secrets verbatim (e.g., pasting keys into a password input, setting KEY=sk-..., and inline env vars/curl payloads), which would force an LLM/agent to handle secret values directly and risks exfiltration.
The skill prompts the agent to compromise the security or integrity of the user’s machine by modifying system-level services or configurations, such as obtaining elevated privileges, altering startup scripts, or changing system-wide settings.
The skill explicitly instructs disabling Electron's sandbox (ELECTRON_DISABLE_SANDBOX / --no-sandbox) — a direct security-bypass — and also contains commands that install packages, kill/restart processes, and modify sandbox files/volumes, which together push the agent to alter the machine state.
7b76a2b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.