[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMYJMDPM8DNFM4F3RTKRCT":3,"skill-same:01M7EMYJMDPM8DNFM4F3RTKRCT":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7EMYJMDPM8DNFM4F3RTKRCT","docker-project-foundations",null,"Use this skill when setting up, initializing, or Dockerizing a project, even if the user doesn't explicitly mention Docker but describes a need for containerized local development, adding a database or cache dependency, or running services without host-level installs. Covers Dockerfile, compose.yaml, and .dockerignore creation with Docker best practices.","Rainbow609\u002Fagent-skills","Rainbow609","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F101709481?v=4","01M7EMQ6CNBNP7TVFZ4Z63RZXD","01M7EMQ6ENV4B0Y542WKXNZBSM",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Fdocker\u002Fskills\u002Fdocker-project-foundations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: docker-project-foundations\ndescription: Use this skill when setting up, initializing, or Dockerizing a project, even if the user doesn't explicitly mention Docker but describes a need for containerized local development, adding a database or cache dependency, or running services without host-level installs. Covers Dockerfile, compose.yaml, and .dockerignore creation with Docker best practices.\nlicense: Apache-2.0\ncompatibility: Requires Docker 20.10+ and Docker Compose v2.\n---\n\n# Docker Project Foundations\n\n## Overview\n\nThis skill guides you in Dockerizing a project from scratch. It focuses on creating the initial Docker file set, choosing a sane layout, and preferring containerized dependencies over host-level installs.\n\n## When to use this skill\n\nActivate this skill when:\n\n- A user asks you to set up, initialize, or Dockerize a project\n- A project needs an initial `Dockerfile`, `compose.yaml`, or `.dockerignore` and does not have one\n- A user wants to add a service dependency (database, cache, message queue) to a project\n- A user asks how to run or develop a project locally and Docker is available\n\n## Do not use this skill when\n\nDo not use this skill when:\n\n- The user explicitly wants to avoid Docker\n- The project already has a mature Docker setup and only needs minor edits\n- The main task is optimizing an existing `Dockerfile`\n- The main task is editing or debugging an existing Compose stack\n\n## Core guidance\n\n### Always create these three files\n\nWhen Dockerizing a project, always produce all three:\n\n1. **`.dockerignore`** — Create this first so the initial build context is small and safe. See `assets\u002Fdockerignore-example` for a reference.\n2. **`Dockerfile`** — Create a working starter image definition that the project can build and run with. See `assets\u002FDockerfile.simple`.\n3. **`compose.yaml`** — Create a local development stack that includes the application service and any required dependencies. See `assets\u002Fcompose-dev.yaml`.\n\n### npm registry credentials\n\n- Exclude `.npmrc` at every depth with `**\u002F.npmrc` in `.dockerignore`; otherwise a broad source copy can persist credentials in image layers.\n- The Node.js starter mounts `npmrc` as a BuildKit secret for both `npm ci` steps. Public-package builds need no secret. For private registries, pass the config explicitly:\n  ```bash\n  DOCKER_BUILDKIT=1 docker build --secret id=npmrc,src=\"$HOME\u002F.npmrc\" .\n  ```\n  Use the actual config path if the project keeps it elsewhere. Never copy the credential file or pass its values through `ARG` or `ENV`. Dependency scripts run during installation can access the mounted secret; use trusted dependencies and a least-privilege registry token.\n- For private-registry builds through Compose, add this optional override as `compose.npm.yaml` alongside the starter's `compose.yaml`:\n  ```yaml\n  services:\n    app:\n      build:\n        secrets:\n          - npmrc\n  secrets:\n    npmrc:\n      file: ${NPMRC_PATH:?Set NPMRC_PATH to your npm config file}\n  ```\n  Build with `NPMRC_PATH=\"$HOME\u002F.npmrc\" docker compose -f compose.yaml -f compose.npm.yaml build`. This grants build-time access only, not a runtime secret. Public-package builds should omit the override so no credential file is required.\n\n### Prefer Dockerized dependencies over host installs\n\nWhen a project needs a database (Postgres, MySQL, MongoDB), cache (Redis, Memcached), queue (RabbitMQ, Kafka), or any other infrastructure service:\n\n- **Always** define it as a service in `compose.yaml` instead of telling the user to install it on the host.\n- **Never** suggest `brew install postgres`, `apt install redis`, or similar host-level installs for development dependencies.\n- Use official Docker images from Docker Hub for these services.\n- Configure services with environment variables, not config files baked into images.\n\n### Bootstrap checklist\n\n- Name the file `compose.yaml` rather than legacy Compose filenames.\n- Put all three files at the project root unless there is a clear multi-service layout that justifies a `docker\u002F` subdirectory.\n- Ensure the initial setup can build and start locally with one command path.\n- Bind published application ports to loopback by default. Widen the host address only when another device must reach the development service.\n- Keep unauthenticated datastores on the Compose network instead of publishing their ports. If local host tools require database access, publish only to loopback.\n- If a development-only credential fallback enables one-command startup, label it clearly and document a `.env` override.\n- Use Compose services for local databases, caches, and queues instead of host installs.\n- Keep the first scaffold simple; defer detailed image optimization and advanced Compose tuning to the owning skills.\n\n### Development vs production\n\n- Development: Use bind mounts for live reload, publish application ports on loopback by default, and enable verbose logging. Keep unauthenticated datastores on the Compose network; publish a datastore port only on loopback when local host tools require it.\n- Production: Use multi-stage builds, copy only built artifacts, do not mount source code, minimize image layers, set appropriate resource limits.\n- Keep a single `Dockerfile` that supports both via build stages and build arguments when possible.\n\n### File placement\n\n- Place `Dockerfile` at the project root (or in a `docker\u002F` subdirectory if the project has multiple services).\n- Place `compose.yaml` at the project root.\n- Place `.dockerignore` at the project root, next to the `Dockerfile`.\n\n## Related skills\n\n- For Dockerfile optimization, cache strategy, non-root execution, and image hardening, use `docker-build-strategies`.\n- For service dependencies, health checks, overrides, volumes, networks, and Compose debugging, use `docker-compose-patterns`.\n- For destructive Docker CLI commands (`docker system prune`, `docker rm -f`, image\u002Fnetwork\u002Fbuilder pruning) and a cross-product index of destructive-command guardrails, use `docker-destructive-guardrails`.\n\n## References\n\n- `references\u002Fproject-structure.md` — Detailed guidance on Docker project file organization, naming conventions, and multi-service layouts.\n\n## Assets\n\n- `assets\u002Fdockerignore-example` — A comprehensive `.dockerignore` for a typical project.\n- `assets\u002Fcompose-dev.yaml` — A development-oriented Compose file with Dockerized dependencies.\n- `assets\u002FDockerfile.simple` — A basic multi-stage Dockerfile following best practices.\n\n## Scripts\n\n- **`scripts\u002Fverify-setup.sh`** — Checks that required files exist in the current directory and validates its `compose.yaml`. Run it from the project root, with the script path resolved under this skill's directory:\n  ```bash\n  bash \"\u003Cskill-dir>\u002Fscripts\u002Fverify-setup.sh\" [--help]\n  ```\n  Replace `\u003Cskill-dir>` with the absolute path of the folder that contains this `SKILL.md`; the `scripts\u002F` path is relative to that folder, not to the project. Do not change into the skill directory first: the script checks the current directory. If the skill directory cannot be resolved, check that `.dockerignore`, `Dockerfile`, and `compose.yaml` exist in the project root, then run `docker compose config --quiet`. Exit status is `0` when verification succeeds or help is requested, `1` when required files are missing or the Compose configuration is invalid, and `2` for invalid arguments.\n\n## Checks\n\n- `checks\u002Fverification.md` — Detailed verification checklist for manual review.\n","# Docker Project Foundations\n\n## Overview\n\nThis skill guides you in Dockerizing a project from scratch. It focuses on creating the initial Docker file set, choosing a sane layout, and preferring containerized dependencies over host-level installs.\n\n## When to use this skill\n\nActivate this skill when:\n\n- A user asks you to set up, initialize, or Dockerize a project\n- A project needs an initial `Dockerfile`, `compose.yaml`, or `.dockerignore` and does not have one\n- A user wants to add a service dependency (database, cache, message queue) to a project\n- A user asks how to run or develop a project locally and Docker is available\n\n## Do not use this skill when\n\nDo not use this skill when:\n\n- The user explicitly wants to avoid Docker\n- The project already has a mature Docker setup and only needs minor edits\n- The main task is optimizing an existing `Dockerfile`\n- The main task is editing or debugging an existing Compose stack\n\n## Core guidance\n\n### Always create these three files\n\nWhen Dockerizing a project, always produce all three:\n\n1. **`.dockerignore`** — Create this first so the initial build context is small and safe. See `assets\u002Fdockerignore-example` for a reference.\n2. **`Dockerfile`** — Create a working starter image definition that the project can build and run with. See `assets\u002FDockerfile.simple`.\n3. **`compose.yaml`** — Create a local development stack that includes the application service and any required dependencies. See `assets\u002Fcompose-dev.yaml`.\n\n### npm registry credentials\n\n- Exclude `.npmrc` at every depth with `**\u002F.npmrc` in `.dockerignore`; otherwise a broad source copy can persist credentials in image layers.\n- The Node.js starter mounts `npmrc` as a BuildKit secret for both `npm ci` steps. Public-package builds need no secret. For private registries, pass the config explicitly:\n  ```bash\n  DOCKER_BUILDKIT=1 docker build --secret id=npmrc,src=\"$HOME\u002F.npmrc\" .\n  ```\n  Use the actual config path if the project keeps it elsewhere. Never copy the credential file or pass its values through `ARG` or `ENV`. Dependency scripts run during installation can access the mounted secret; use trusted dependencies and a least-privilege registry token.\n- For private-registry builds through Compose, add this optional override as `compose.npm.yaml` alongside the starter's `compose.yaml`:\n  ```yaml\n  services:\n    app:\n      build:\n        secrets:\n          - npmrc\n  secrets:\n    npmrc:\n      file: ${NPMRC_PATH:?Set NPMRC_PATH to your npm config file}\n  ```\n  Build with `NPMRC_PATH=\"$HOME\u002F.npmrc\" docker compose -f compose.yaml -f compose.npm.yaml build`. This grants build-time access only, not a runtime secret. Public-package builds should omit the override so no credential file is required.\n\n### Prefer Dockerized dependencies over host installs\n\nWhen a project needs a database (Postgres, MySQL, MongoDB), cache (Redis, Memcached), queue (RabbitMQ, Kafka), or any other infrastructure service:\n\n- **Always** define it as a service in `compose.yaml` instead of telling the user to install it on the host.\n- **Never** suggest `brew install postgres`, `apt install redis`, or similar host-level installs for development dependencies.\n- Use official Docker images from Docker Hub for these services.\n- Configure services with environment variables, not config files baked into images.\n\n### Bootstrap checklist\n\n- Name the file `compose.yaml` rather than legacy Compose filenames.\n- Put all three files at the project root unless there is a clear multi-service layout that justifies a `docker\u002F` subdirectory.\n- Ensure the initial setup can build and start locally with one command path.\n- Bind published application ports to loopback by default. Widen the host address only when another device must reach the development service.\n- Keep unauthenticated datastores on the Compose network instead of publishing their ports. If local host tools require database access, publish only to loopback.\n- If a development-only credential fallback enables one-command startup, label it clearly and document a `.env` override.\n- Use Compose services for local databases, caches, and queues instead of host installs.\n- Keep the first scaffold simple; defer detailed image optimization and advanced Compose tuning to the owning skills.\n\n### Development vs production\n\n- Development: Use bind mounts for live reload, publish application ports on loopback by default, and enable verbose logging. Keep unauthenticated datastores on the Compose network; publish a datastore port only on loopback when local host tools require it.\n- Production: Use multi-stage builds, copy only built artifacts, do not mount source code, minimize image layers, set appropriate resource limits.\n- Keep a single `Dockerfile` that supports both via build stages and build arguments when possible.\n\n### File placement\n\n- Place `Dockerfile` at the project root (or in a `docker\u002F` subdirectory if the project has multiple services).\n- Place `compose.yaml` at the project root.\n- Place `.dockerignore` at the project root, next to the `Dockerfile`.\n\n## Related skills\n\n- For Dockerfile optimization, cache strategy, non-root execution, and image hardening, use `docker-build-strategies`.\n- For service dependencies, health checks, overrides, volumes, networks, and Compose debugging, use `docker-compose-patterns`.\n- For destructive Docker CLI commands (`docker system prune`, `docker rm -f`, image\u002Fnetwork\u002Fbuilder pruning) and a cross-product index of destructive-command guardrails, use `docker-destructive-guardrails`.\n\n## References\n\n- `references\u002Fproject-structure.md` — Detailed guidance on Docker project file organization, naming conventions, and multi-service layouts.\n\n## Assets\n\n- `assets\u002Fdockerignore-example` — A comprehensive `.dockerignore` for a typical project.\n- `assets\u002Fcompose-dev.yaml` — A development-oriented Compose file with Dockerized dependencies.\n- `assets\u002FDockerfile.simple` — A basic multi-stage Dockerfile following best practices.\n\n## Scripts\n\n- **`scripts\u002Fverify-setup.sh`** — Checks that required files exist in the current directory and validates its `compose.yaml`. Run it from the project root, with the script path resolved under this skill's directory:\n  ```bash\n  bash \"\u003Cskill-dir>\u002Fscripts\u002Fverify-setup.sh\" [--help]\n  ```\n  Replace `\u003Cskill-dir>` with the absolute path of the folder that contains this `SKILL.md`; the `scripts\u002F` path is relative to that folder, not to the project. Do not change into the skill directory first: the script checks the current directory. If the skill directory cannot be resolved, check that `.dockerignore`, `Dockerfile`, and `compose.yaml` exist in the project root, then run `docker compose config --quiet`. Exit status is `0` when verification succeeds or help is requested, `1` when required files are missing or the Compose configuration is invalid, and `2` for invalid arguments.\n\n## Checks\n\n- `checks\u002Fverification.md` — Detailed verification checklist for manual review.\n",{"name":5,"license":14,"description":7,"compatibility":23},"Requires Docker 20.10+ and Docker Compose v2.","main","18e26686a1432c54293deba762caad02ba886925","upstream\u002Fdocker\u002Fskills\u002Fdocker-project-foundations","https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002FRainbow609","2026-11-15 11:39:03",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Rainbow609\u002Fagent-skills --skill docker-project-foundations",{"tool":36,"command":37},"bunx","bunx skills add Rainbow609\u002Fagent-skills --skill docker-project-foundations",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Rainbow609\u002Fagent-skills --skill docker-project-foundations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Fdocker\u002Fskills\u002Fdocker-project-foundations\u002FSKILL.md",true,[44,50,56,60,64,68,72,78],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",269,"https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Fdocker\u002Fskills\u002Fdocker-project-foundations\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Fcompose-dev.yaml","ASSET","资产文件",1580,"https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Fdocker\u002Fskills\u002Fdocker-project-foundations\u002Fassets\u002Fcompose-dev.yaml",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"assets\u002FDockerfile.simple",959,"https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Fdocker\u002Fskills\u002Fdocker-project-foundations\u002Fassets\u002FDockerfile.simple",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"assets\u002Fdockerignore-example",654,"https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Fdocker\u002Fskills\u002Fdocker-project-foundations\u002Fassets\u002Fdockerignore-example",{"path":65,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":66,"sourceHtmlUrl":67},"checks\u002Fverification.md",4189,"https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Fdocker\u002Fskills\u002Fdocker-project-foundations\u002Fchecks\u002Fverification.md",{"path":69,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fproject-structure.md",3335,"https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Fdocker\u002Fskills\u002Fdocker-project-foundations\u002Freferences\u002Fproject-structure.md",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"scripts\u002Fverify-setup.sh","SCRIPT","脚本",1122,"https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Fdocker\u002Fskills\u002Fdocker-project-foundations\u002Fscripts\u002Fverify-setup.sh",{"path":79,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":80,"sourceHtmlUrl":81},"skill.yaml",853,"https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Fdocker\u002Fskills\u002Fdocker-project-foundations\u002Fskill.yaml",[83,92,100,107,114,121],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M7EN4N53ENQWQE5NDRT64NDC","archify","Create validated architecture, workflow, sequence, data-flow, lifecycle\u002Fstate, entity-relationship, class\u002Finterface, tree, timeline, and execution waterfall diagrams as explorable standalone HTML with inline SVG, dark\u002Flight themes, optional motion, and image\u002FSVG\u002FWebM export. Accept plain-language requirements or Mermaid; inspect repository evidence for code-backed diagrams. Use when visualizing infrastructure, cloud\u002Fsecurity networks, API calls, data pipelines, ETL\u002FELT, state machines, database schemas, class contracts, module hierarchies, incident\u002Frelease histories, or request and agent-run timings. Also use for everyday subjects with steps, parts, relationships, or states: leave and travel plans, applications and approvals, renting conversations, money or document flows, and order progress. Not for numeric charts or dashboards.","MIT","https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Ftt-a1i\u002Farchify\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Ftt-a1i\u002Farchify\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":18},"01M7EN4GGKJXFVK85685S30141","distilly","Set up the owner profile so a personal agent knows who it works for (first-run setup, \"get to know me\"), or distill colleague, relationship, or celebrity source material into reusable Person Profiles for agents.","https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Ftitanwings\u002Fdistilly\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Ftitanwings\u002Fdistilly\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":18},"01M7EMZQREVCNAJA9DY7NQ7M7Q","docker-sandboxes-network-credentials","Use this skill when configuring what a Docker Sandboxes (`sbx`) sandbox can reach on the network or which credentials it authenticates with, even if the user just says they want to \"let the agent call an internal API\", \"block all network access\", \"give the agent a GitHub token\", or \"use a private registry image for a sandbox\". Covers `sbx policy init\u002Fallow\u002Fdeny\u002Fls\u002Finspect\u002Flog\u002Fcheck\u002Frm network` (global and per-sandbox egress rules, deny-over-allow precedence) and `sbx secret set\u002Fset-custom\u002Fls\u002Frm\u002Fimport` (service secrets, dynamic secrets via --ref\u002F--command, and registry pull credentials with their host-pulls-only-by-default injection scope).","https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Fdocker\u002Fskills\u002Fdocker-sandboxes-network-credentials\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":18},"01M7EMZE6V7A70RR2AMMDAGP3S","docker-sandboxes-lifecycle","Use this skill when creating, running, reattaching to, listing, stopping, or removing Docker Sandboxes (the standalone `sbx` CLI that runs AI coding agents in isolated microVMs), even if the user just says they want to \"run claude in a sandbox\", \"isolate an agent from my repo\", \"give an agent its own git clone\", or \"clean up old sandboxes\". Covers `sbx run`\u002F`sbx create` (including the built-in agents claude, codex, cursor, devin, docker-agent, gemini, opencode, shell), workspace bind-mount vs `--clone` isolation, additional read-only workspaces, reattaching by `--name`, `sbx ls`\u002F`stop`\u002F`rm`\u002F`prune`, `sbx exec`, `sbx cp`, and `sbx ports`.","https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Fdocker\u002Fskills\u002Fdocker-sandboxes-lifecycle\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":18},"01M7EMZ2BN8Z7P5H557RS8WYP2","docker-sandboxes-kits","Use this skill when authoring, validating, packaging, signing, or composing a Docker Sandboxes kit `spec.yaml` (`sbx kit add\u002Finspect\u002Fpack\u002Fpull\u002Fpush\u002Fsign\u002Fvalidate\u002Fverify`), even if the user just says they want to \"add a tool to a sandbox agent\", \"build a reusable sandbox extension\", \"publish a kit to a registry\", or \"give a mixin its own credentials and network access\". Covers the kit-spec v2 grammar (`kind: sandbox` vs `kind: mixin`, the `sandbox:` block, `permissions.network`, `ports`, `credentials` apiKey\u002Foauth, `environment`, `setup` install\u002Fstartup\u002Ffiles, `volumes`, `args`, `extends`, `mixins`, `requires.agent`), composition via `--kit`\u002F`sbx kit add`, and distribution (pack\u002Fpush\u002Fpull\u002Fsign\u002Fverify\u002Fprovenance).","https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Fdocker\u002Fskills\u002Fdocker-sandboxes-kits\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":18},"01M7EMYQZXA60B14ZQEXMSWNVG","docker-sandboxes-env","Use this skill when authoring, planning, or running a declarative `sbxenv.yaml` file for Docker Sandboxes (`sbx env create\u002Frun\u002Fplan\u002Fexec\u002Frm`), even if the user just says they want to \"check in a sandbox config\", \"make onboarding reproducible for a sandbox\", \"run a setup script before the agent starts\", or \"define arguments for a shared sandbox environment\". Covers the sbxenv.yaml schema (schemaVersion, agent, kits, workspace\u002FadditionalWorkspaces, args, env, secrets, registries, bindings, mcp, ports, sandboxOptions), host `lifecycle:` commands (initialize\u002FpostCreate\u002FpreRemove) and their approval-plan model, multi-file merge (`-f`-style deep merge and the user-level `.sbxenv.yaml` base layer), and file-write-protection (`sandboxOptions.writableEnvFiles`).","https:\u002F\u002Fgithub.com\u002FRainbow609\u002Fagent-skills\u002Fblob\u002Fmain\u002Fupstream\u002Fdocker\u002Fskills\u002Fdocker-sandboxes-env\u002FSKILL.md",[],[]]