Use when the user asks about Oleg Šelajev's talk "You're absolutely right, it was your home directory!" (ext live / Testkube conference, 2026) — including questions about Docker Sandboxes, running AI agents in microVM isolation, the trifecta of agent risks (sensitive data + external comms + untrusted content), why containers aren't enough for agent isolation, SBX kits, secret injection / sentinel values, prompt injection horror stories, YOLO mode agents, or applying his sandboxing workflow to the user's own agent setup.
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./talk-selajev-docker-sandboxes-agents/SKILL.mdThe skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The runtime workflow ingests outsider-authored free text via the user/agent-submitted skill/demo payload included in the transcript (“prompt injection” email/GitHub handles seed), which demonstrates an attacker can supply arbitrary text to the agent through the skill input path.
AINativeDev/aidevcon-2026-ldn
df83a42
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.