Provisions isolated userspace development toolchains per project using uv, conda-forge, and publisher archives.
npx skills add https://github.com/BTreeMap/SKILLs --skill setup-env-btreemap
Please help me install this Agent Skill. Skill: setup-env Source: https://github.com/BTreeMap/SKILLs/tree/main/setup-env Command: npx skills add https://github.com/BTreeMap/SKILLs --skill setup-env-btreemap
[email protected], kotlin:android@35, or go:cgo; one command plans, installs, and verifies them with probes. - Hermetic isolation: Activation scripts redirect HOME, TMPDIR, XDG dirs, and every toolchain cache under the environment root, so nothing reads or writes caller state. - Cross-architecture support: Foreign-architecture binaries (e.g., x86_64 aapt2 on linux/arm64) run via qemu user-mode emulation or Rosetta 2, decided centrally. - Use Case: On a bare CI-like Linux box with only uv installed, run btm-setup-env provision [email protected] rust to get a working, verified Python and Rust environment, then source the printed activate.sh and build. ## Quick Start Ask the agent to provision the toolchains your project needs, for example: set up a development environment with python 3.12 and go for this project using the setup-env skill.High-intent search queries and answers about installing and using this skill.
Run `btm-setup-env provision` with tags like `[email protected] go rust`; everything installs into one disposable root in userspace using uv, micromamba, and publisher archives. Source the printed activate.sh to use the tools.
Use the tag `kotlin:android@35` or `java:android@35`, which installs the JDK, Android SDK cmdline-tools, platform, and build-tools. The x86_64-only aapt2 binary is wrapped in qemu user-mode emulation and registered via android.aapt2FromMavenOverride.
Linux and macOS on x86_64/arm64 are first class; Windows x86_64 is best effort, with haskell, bash, c, and cpp unavailable there. On macOS/arm64, osx-64 binaries run transparently through Rosetta 2.
Re-run the same provision command; every executor checks its own postcondition and skips completed work, so re-running is the documented repair. A failed probe still exits 0 with `ok` false and a `next` field naming the repair.
No. The activation script redirects HOME, TMPDIR, XDG directories, and every toolchain cache variable under the environment root. Nothing reads the caller's dotfiles or global toolchains, and the project checkout only receives generated ignored files like local.properties.
Do not use it for CI images, system packages, or deployment; those belong to the project's own tooling. It serves local builds and tests, and the root is ephemeral under the system temp dir, so re-provision after a reboot.
CortaLabsScan user projects for Atlas metadata and repository ownership via GitHub.
ek33450505Scan configured git repositories and summarize commits since yesterday in a markdown table.
databricks-solutionsRun PWAF connector test suites across authentication methods in isolated environments.
salverius-techCreate reproducible DevContainer environments with Docker, uv, and multi-stage builds.