Devcontainer Setup Agent
- Repo stars 0
- Author repo skills-registry
- Domain
- AI
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Manual integration
- External API key
- Not required
- Operating systems
- macOS · Linux · Docker
- Runtime requirements
- Node.js · Python · Docker
- Detected file/system behavior
-
- Read-only
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Devcontainer Setup Agent
## Prerequisites
Node.js, Docker
## Installation
Use the upstream install or setup path that matches your environment:
- npm install -g @devcontainers/cli
- git clone https://github.com/microsoft/vscode-remote-try-rust
- yarn
- yarn compile
Requirements and caveats from upstream:
- You can install the CLI with a standalone script that downloads a bundled Node.js runtime, so no pre-installed Node.js is required. It works on Linux and macOS (x64 and arm64):
- To install the npm package you will need Python and C/C++ installed to build one of the dependencies (see, e.g., [here](https://github.com/microsoft/vscode/wiki/How-to-Contribute) for instructions).
- [165 ms] Start: Run: docker build -f /home/node/vscode-remote-try-rust/.devcontainer/Dockerfile -t vsc-vscode-remote-try-rust-89420ad7399ba74f55921e49cc3ecfd2 --build-arg VARIANT=bullseye /home/node/vscode-remote-try-...
Basic usage or getting-started notes:
- A development container allows you to use a container as a full-featured development environment. It can be used to run an application, to separate tools, libraries, or runtimes needed for working with a codebase, and...
- [x] devcontainer run-user-commands - Runs lifecycle commands like postCreateCommand
- bash
- Source: https://github.com/devcontainers/cli
- Extracted from upstream docs: https://raw.githubusercontent.com/devcontainers/cli/HEAD/README.md
## Documentation
- https://github.com/devcontainers/cli
## Source
- [Agent Skill Exchange](https://agentskillexchange.com/skills/devcontainer-setup-agent/)
---
> Source: [agentskillexchange/skills](https://github.com/agentskillexchange/skills) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
Sections and files
Listed in source order.
sections -> Prerequisites → Installation → Documentation → Source
terms -> Basic usage or getting-started notes: - A development container allows you to use a container as a full-featured development environment. · --- > Source: [agentskillexchange/skills](https://github.com/agentskillexchange/skills) — distributed by [TomeVault](https://tomevault.io).
files/cmd -> Node.js · devcontainers/cli · github.com/microsoft/vscode-remote-try-rust · C/C · github.com/microsoft/vscode/wiki/How-to-Contribute · home/node/vscode-remote-try-rust/.devcontainer/Dockerfile · home/node/vscode-remote-try-... · github.com/devcontainers/cli
body sha256 -> d32fd213290e
Prerequisites
Node.js, Docker
Installation
Use the upstream install or setup path that matches your environment: npm install -g @devcontainers/cli git clone https://github.com/microsoft/vscode-remote-try-rust yarn yarn compile
Documentation
https://github.com/devcontainers/cli
Source
Agent Skill Exchange Source: agentskillexchange/skills — distributed by TomeVault.