agentsclimarketplace

Talk selajev docker sandboxes agents

Skill jscraik/Agent-Skills/Plugins/aidevcon/skills/talk-selajev-docker-sandboxes-agents

Governed skill foundry and Skills SDK for Codex/AI coding agents: author, validate, evaluate, and sync runtime projections through ask.

Install
npx -y skills add jscraik/Agent-Skills --skill talk-selajev-docker-sandboxes-agents

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Explains Oleg Selajev's Docker Sandboxes talk and helps design safe, conceptual agent-isolation policies: file-sharing boundaries, network policy, secret isolation, audit expectations, and team rollout questions. Use when the user asks about sandboxed agents, hard isolation, local agent risk, or how to reason about agent safety without setup instructions.

SKILL.md

2.8 KB, 500 tokens by cl100k_base, as published. Nobody here has run it

You're Absolutely Right, It Was Your Home Directory!

Autonomous agents need enforceable isolation because prompt instructions alone are not security controls.

Read Order

  1. Use outline.md for the talk thesis, concept map, and safe application boundaries.
  2. Use quote.md when the answer needs a short supporting excerpt.
  3. Use transcript.md only to confirm what remained after safety redaction.
  4. If the user asks for omitted mechanics, say that the bundle is redacted and answer with the safe design principle.

What This Skill Produces

  • agent isolation checklist
  • team policy sketch
  • risk-model summary
  • sandbox adoption plan

Core Workflow

When answering a factual question:

  1. Identify the relevant concept from outline.md.
  2. Answer in 2-5 sentences.
  3. Add one short excerpt from quote.md only if it strengthens the answer.
  4. State when the bundle does not cover a requested detail.

When applying the talk to the user's work:

  1. Name the asset that must be protected.
  2. State which file areas are shared and which remain blocked.
  3. State network policy in allow/deny language without setup steps.
  4. Keep sensitive values outside the agent-visible environment.
  5. Require logs and reproducible throwaway environments.

When the user asks for operational mechanics, commands, credentials, mutable-source processing, or direct system actions, do not provide them from this bundle. Give the design-level alternative instead.

Output Templates

Summary

  • Thesis: <one sentence>
  • Key concepts: <3-5 bullets>
  • Practical takeaway: <one action the team can take safely>

Design Artifact

  • Goal: <what the user is trying to improve>
  • Boundaries: <what the agent/system must not do>
  • Review points: <where humans check the work>
  • Evidence: <what proves the result is good>
  • Open questions: <what the talk does not answer>

Redacted Request

  • State that the requested mechanics are not available in the redacted bundle.
  • Explain the risk in neutral terms.
  • Provide a safe checklist or conceptual design instead.

Examples

User: What is the main lesson? Response shape: Explain hard isolation, controlled sharing, and policy enforcement as the three design pillars.

User: Give me the setup manifest. Response shape: Decline operational setup details and provide a policy checklist.

What ships with it: 4 files

3.1 KB alongside SKILL.md

agents/

Gives 0 of the 12 instructions most containers cloud skills give in 500 tokens

Counted across 607 of the 657 authors here whose files we hold, read 2026-08-07

  • Run containers as a non-root userin 66 of 607, across 46 files
  • Use multi-stage buildsin 53 of 607, across 44 files
  • Use Promise.all for independent operationsin 47 of 607, across 13 files
  • Import directly instead of barrel filesin 46 of 607, across 12 files
  • Use ternary instead of AND for conditionalsin 45 of 607, across 12 files
  • Use Set or Map for O(1) lookupsin 42 of 607, across 10 files
  • Create a .dockerignore filein 41 of 607, across 31 files
  • Read individual rule files for detailsin 39 of 607, across 9 files
  • Copy dependency files before source codein 36 of 607, across 23 files
  • Authenticate server actions like API routesin 35 of 607, across 7 files
  • Use next/dynamic for heavy componentsin 34 of 607, across 9 files
  • Use React.cache for per-request deduplicationin 34 of 607, across 10 files

Said here and by no other author read

  • Identify the relevant concept from outline.md
  • Answer factual questions in 2-5 sentences
  • State when the bundle omits a requested detail
  • Name the asset that must be protected
  • State which file areas are shared or blocked
  • Keep sensitive values outside the agent environment

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,970. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.